Discussion related to cado-nfs

[Greg Marks <marks@member.ams.org>]

Thank you for your help.  The documentation in scripts/cadofactor/README
does advise adjusting the value of tasks.sieve.sieving.qmin although
it wasn't quite so explicit about what it should be changed to.
I thought omitting this step would simply lead to extra time spent
removing duplicates, not a program crash.  Incidentally, is that a typo
in scripts/cadofactor/README: is tasks.sieve.sieving.qmin supposed to
be tasks.sieve.qmin?

Sincerely,
Greg Marks

    ------------------------------------------------
   | Greg Marks                                     |
   | Department of Mathematics and Computer Science |
   | St. Louis University                           |
   | St. Louis, MO 63103-2007                       |
   | U.S.A.                                         |
   |                                                |
   | Phone: (314)977-7206        Fax: (314)977-1452 |
   | PGP encryption public key ID: 0x53F269E8       |
   | Web: http://gmarks.org                         |
    ------------------------------------------------

Message from Francois Morain <morain@lix.polytechnique.fr>
of June 13, 2015, 09:22:06 +0200, follows:
> I had the very same problem yesterday. The problem is this: if you
> import relations, you must reset the value of qmin to the last value
> of special-q used (the largest number in all the *sieve*.gz).
> Otherwise, you restart with the same special-q's and then you get
> zillions of duplicate relations which make dup1 doing its job
> and this explains the 0 size file.
> 
> As for the comments about regenerating things already done, I think
> this is under study, because we are plenty of customers having the
> same problem. Importing bases and such would be handy.
> 
> Hope this helps,
> FM

Attachment: signature.asc
Description: Digital signature