Home My Page Projects cado-nfs
Summary Activity Forums Tracker Lists Tasks Docs News SCM Files

Project Filelist for cado-nfs

File Release Notes and Changelog

Release Name: 2.3.0

Release Notes
Main changes between cado-nfs-2.2.0 and cado-nfs-2.3.0:
* When tasks.threads is not given, it is set to the number of logical cores
  (including hyperthreading if any) instead of the number of physical cores.
* The estimated time of arrival (ETA) is now printed during the linear
  algebra phase too.
* Speedup in the linear algebra phase (mksol) when m > n
* DLP support: got rid of the Magma dependency
* Fixed compiler warnings with new versions of compilers.
* Several bug fixes.
* The output files have been shortened. Previously, we had filenames of
  the form cxxx.TASKNAME.PROGRAMNAME.foo, where TASKNAME was actually an
  implementation detail. In cado-nfs-2.3.0, TASKNAME goes away.
* In parallel to the change above, the parameter hierarchy no longer
  includes the TASKNAME, which is an implementation detail. Previously,
  the finest grain to which one could specify parameters was
  scripts/cadofactor/cadotask.py (among polyselect, sieve, filter,
  linalg, reconstructlog, descent -- some toplevel relevant parameters
  have no PATH_PREFIX). Now the TASKNAME goes away. This
  means that as before, setting tasks.sieve.threads works for setting a
  parameter which is obeyed by las (and actually makefb too), but changes
  happen when one specifies parameters on a finer grain.  While
  tasks.sieve.sieving.las.threads or
  tasks.sieve.factorbase.makefb.threads used to work, now these become
  simply tasks.sieve.las.threads or tasks.sieve.makefb.threads.
* The --verboseparam option to cado-nfs.py now also prints an
  automatically generated, and by default comprehensive list of
  parameters that cado-nfs recognizes (among other things
  which this option still does as it always has). Note that the lists for
  factoring and DLP differ slightly.
* The database which stores the computation state can now also be backed
  by a mysql server. This is optional, and requires the
  python3-mysql.connector package (on Debian linux -- actual package name
  depends on your OS distribution). To activate this feature, pass the
  database URI as an extra parameter to cado-nfs.py, e.g.
  "database=db:mysql://USER:PASS@host:port/foobar", where port, PASS, and
  USER are optional. The same syntax may be used to have an sqlite3
  database as usual, but stored in a different location (which can be
  handy to work around some filesystem deficiencies). For that, use
  "database=db:sqlite3:///tmp/foo.db", where obviously "/tmp/foo.db" must
  be adapted to your preferred database path (you do need the triple /).