Subject: Discussion related to cado-nfs
List archive
- From: Emmanuel Thomé <emmanuel.thome@gmail.com>
- To: paul leyland <paul.leyland@gmail.com>
- Cc: "cado-nfs-discuss@lists.gforge.inria.fr" <Cado-nfs-discuss@lists.gforge.inria.fr>
- Subject: Re: [Cado-nfs-discuss] Possible enhancement?
- Date: Fri, 29 Nov 2013 09:59:30 +0100
- 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 empty mail, I've hit the wrong key too soon.
Won't
$cadofactor.py original_params.c1xy local.params
Just Work (tm) instead ? I think that any freestanding thing in the
command line is interpreted as a file name if it doesn't look like an
option.
Best,
E.
On Fri, Nov 29, 2013 at 9:43 AM, Paul Leyland <paul.leyland@gmail.com> wrote:
> On Thu, 2013-11-28 at 20:10 +0100, Zimmermann Paul wrote:
>> Paul,
>>
>> > From: Paul Leyland <paul.leyland@gmail.com>
>> > Date: Thu, 28 Nov 2013 17:50:18 +0000
>> >
>> > Now I'm getting more practice with V2.0 I find myself going through the
>> > following procedure to set up a params file.
>> >
>> > 1) copy the prototype params.c1xy to a work directory
>> > 2) Delete a few lines from that copy
>> > 3) Copy some standard local boiler plate to set such things as the
>> > network whitelist, number of cores per machine and so on.
>> > 4) Use diff to check that the new params file looks plausible.
>> >
>> > Wouldn't It Be Nice If (tm) there was a #include mechanism for parameter
>> > files? Each of the prototypes could then #include "local.params" to set
>> > the local environment and overwrite / delete (i.e. overwrite with NULL)
>> > inappropriate global variables.
>> >
>> > Is it feasible to implement this WIBNI? Is there a better way of doing
>> > the same thing at present than my laborious procedure?
>> >
>> > Paul
>>
>> sure there is a better way:
>>
>> $ cadofactor.py original_params.c1xy param1=... param2=...
>>
>> Any parameter given on the command line takes precedence on those defined
>> in
>> the original_params.c1xy file.
>
> Ah, I'd noted that but your reminder helped me see that a #include
> function can be implemented as
>
> $cadofactor.py original_params.c1xy `cat local.params`
>
> Thanks.
>
> Paul
>
>
>
> _______________________________________________
> Cado-nfs-discuss mailing list
> Cado-nfs-discuss@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/cado-nfs-discuss
- [Cado-nfs-discuss] Possible enhancement?, Paul Leyland, 11/28/2013
- Re: [Cado-nfs-discuss] Possible enhancement?, Zimmermann Paul, 11/28/2013
- Re: [Cado-nfs-discuss] Possible enhancement?, Paul Leyland, 11/29/2013
- Re: [Cado-nfs-discuss] Possible enhancement?, Emmanuel Thomé, 11/29/2013
- Re: [Cado-nfs-discuss] Possible enhancement?, Emmanuel Thomé, 11/29/2013
- Re: [Cado-nfs-discuss] Possible enhancement?, Paul Leyland, 11/29/2013
- Re: [Cado-nfs-discuss] Possible enhancement?, Zimmermann Paul, 11/28/2013
Archive powered by MHonArc 2.6.19+.