Subject: Discussion related to cado-nfs
List archive
- From: Zimmermann Paul <Paul.Zimmermann@inria.fr>
- To: Emmanuel Thomé <emmanuel.thome@gmail.com>
- Cc: Cado-nfs-discuss@lists.gforge.inria.fr
- Subject: Re: [Cado-nfs-discuss] change of semantics of -admin and -incr
- Date: Tue, 16 Sep 2014 23:21:33 +0200
- List-archive: <http://lists.gforge.inria.fr/pipermail/cado-nfs-discuss/>
- List-id: A discussion list for Cado-NFS <cado-nfs-discuss.lists.gforge.inria.fr>
> Sorry for the very late follow-up on this.
>
> By forcing a_d to be a multiple of e.g. 210, we are forcing some good
> root properties at inifinity.
>
> Are you saying that the induced benefit is minimal, to the point that
> we should not do that ?
no, I was not clear enough. If you want one polyselect job to process
odd multiples of 210, while another one processes even multiple of 210,
it would be possible with the proposed new behaviour, with:
job 1: -admin 210 -incr 420 will process 210, 630, 1050, ...
job 2: -admin 420 -incr 420 will process 420, 840, 1260, ...
This is not possible with the current code, since job 1 would round up
admin to a multiple of incr=420, thus 420, and would thus process the same
values as job 2.
Paul
- [Cado-nfs-discuss] change of semantics of -admin and -incr, Zimmermann Paul, 09/09/2014
- Re: [Cado-nfs-discuss] change of semantics of -admin and -incr, Emmanuel Thomé, 09/16/2014
- Re: [Cado-nfs-discuss] change of semantics of -admin and -incr, Zimmermann Paul, 09/16/2014
- Re: [Cado-nfs-discuss] change of semantics of -admin and -incr, Emmanuel Thomé, 09/16/2014
- Re: [Cado-nfs-discuss] change of semantics of -admin and -incr, Zimmermann Paul, 09/16/2014
- Re: [Cado-nfs-discuss] change of semantics of -admin and -incr, Emmanuel Thomé, 09/16/2014
Archive powered by MHonArc 2.6.19+.