Skip to Content.
Sympa Menu

cado-nfs - Re: [Cado-nfs-discuss] change of semantics of -admin and -incr

Subject: Discussion related to cado-nfs

List archive

Re: [Cado-nfs-discuss] change of semantics of -admin and -incr


Chronological Thread 
  • From: Emmanuel Thomé <emmanuel.thome@gmail.com>
  • To: Zimmermann Paul <Paul.Zimmermann@inria.fr>
  • Cc: "cado-nfs-discuss@lists.gforge.inria.fr" <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:26:47 +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>

Ok. Agreed. Your -admin -incr 32 was misleading, because on all
accounts, I think that this is not something that someone would
consider doing. But the application you suggest is fine. The user
should just not do stupid things when setting admin.

E.

On Tue, Sep 16, 2014 at 11:21 PM, Zimmermann Paul
<Paul.Zimmermann@inria.fr> wrote:
>> 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
>




Archive powered by MHonArc 2.6.19+.

Top of Page