Subject: Discussion related to cado-nfs
List archive
- From: Paul Zimmermann <Paul.Zimmermann@inria.fr>
- To: eric.jeancolas@free.fr
- Cc: cado-nfs@inria.fr, paul.leyland@gmail.com
- Subject: Re: [cado-nfs] Parameter documentatin.
- Date: Thu, 06 Jul 2023 09:33:38 +0200
- Authentication-results: mail3-relais-sop.national.inria.fr; dkim=none (message not signed) header.i=none; spf=SoftFail smtp.mailfrom=Paul.Zimmermann@inria.fr; spf=None smtp.helo=postmaster@coriandre
Hi Eric,
> Date: Wed, 5 Jul 2023 16:13:31 +0200 (CEST)
> From: eric.jeancolas@free.fr
>
> Hi Paul(s)
>
> Just a question of logic.
> Issuing a grep tasks.I params* on parameters/factor, I get the following
> params.c105:tasks.I = 12
> params.c110:tasks.I = 12
> params.c115:tasks.I = 12
> params.c120:tasks.I = 12
> params.c125:tasks.I = 13
> params.c130:tasks.I = 14
> params.c135:tasks.I = 13
> params.c140:tasks.I = 13
> params.c145:tasks.I = 13
> params.c150:tasks.I = 13
> params.c155:tasks.I = 14
> params.c160:tasks.I = 14
> params.c165:tasks.I = 14
> params.c170:tasks.I = 14
> params.c175:tasks.I = 14
>
> Well, about params.c130, it seems have a continuity check. Shouldn't be set
> to 13 ?
these parameters were set using some optimization tool.
This tool does not guarantee continuity of the parameters.
If you change tasks.I to 13 in params.c130, beware that
you have to adapt the other parameters, otherwise you might
have a suboptimal configuration.
Best regards,
Paul
- Re: [cado-nfs] Parameter documentatin., Paul Zimmermann, 07/04/2023
- Re: [cado-nfs] Parameter documentatin., eric . jeancolas, 07/05/2023
- Re: [cado-nfs] Parameter documentatin., Paul Zimmermann, 07/06/2023
- Re: [cado-nfs] Parameter documentatin., eric . jeancolas, 07/05/2023
Archive powered by MHonArc 2.6.19+.