[QUOTE]If possible I suggest that you break it up into smaller files (maybe 500,000 each), each with a different set of k. This will allow you to start working on candidates while others are loading.[/QUOTE]

That's the exact thing I'm trying to avoid. I just turned 75 on Monday and can't see too well and don't move around too much. A straight forward one time load of files without having to bust them up would be ideal.

[QUOTE=MyDogBuster;552801][QUOTE]If possible I suggest that you break it up into smaller files (maybe 500,000 each), each with a different set of k. This will allow you to start working on candidates while others are loading.[/QUOTE]

That's the exact thing I'm trying to avoid. I just turned 75 on Monday and can't see too well and don't move around too much. A straight forward one time load of files without having to bust them up would be ideal.[/QUOTE]

You can load that many, but I recommend that if the server is empty that you wait until loading is done before you point clients to it.

Thanks Mark. Will try to load them all.

For now using srbsieve up to n=3000; after that i will use a script using srsieve2 and cllr. In general i think srsieve2 should be implemented in srbsieve to get a speed boost.

Aren't the syntaxes the same for srsieve and srsieve2? Can't you just rename srsieve2 to srsieve and get what you want?

[QUOTE=VBCurtis;569174]Aren't the syntaxes the same for srsieve and srsieve2? Can't you just rename srsieve2 to srsieve and get what you want?[/QUOTE]


Sadly not. srsieve2 needs -s flag to import sequences from a file while srsieve just needs the name of a file to get the sequences loaded.

[QUOTE=MisterBitcoin;569185]Sadly not. srsieve2 needs -s flag to import sequences from a file while srsieve just needs the name of a file to get the sequences loaded.[/QUOTE]

It isn't quite a "slam dunk". It should support srsieve, srsieve2, and srsieve2cl as possible sieving programs.

You can try the following, but it will require change to your srbsieve.ini file. You need to change the phase lines. The first parameter should be the sieving program to use, "srsieve", "srsieve2", and "srsieve2cl" are the possible values but there isn't any explicit validation. So if you have:

phase=1000,100000,30000

it must now be:

phase=srsieve,1000,100000,30000

This will allow you to choose the program you want to use for each phase and play around with the configurations to determine to determine which works the best.

And no, I have not tested these changes.

[QUOTE=rogue;569192]You can try the following, but it will require change to your srbsieve.ini file. You need to change the phase lines. The first parameter should be the sieving program to use, "srsieve", "srsieve2", and "srsieve2cl" are the possible values but there isn't any explicit validation. So if you have:

phase=1000,100000,30000

it must now be:

phase=srsieve,1000,100000,30000

This will allow you to choose the program you want to use for each phase and play around with the configurations to determine to determine which works the best.

And no, I have not tested these changes.[/QUOTE]


[CODE]Phase 3: Processing k from 1132000000 to 1132052528
command: srsieve -q -m1e10 -P42000 -n145 -N192 -w sieve.in
srsieve2 v1.1, a program to find factors of k*b^n+c numbers for fixed b and variable k and n
srsieve: unknown option -- q
Fatal Error: srsieve: invalid option -m1e10[/CODE]

Those flags also have been changed so i dont think it will work. Tried out your mention, but i got

[CODE]Error: Could not process line phase=srsieve,144,33000,396000[/CODE]

[QUOTE=MisterBitcoin;569195][CODE]Phase 3: Processing k from 1132000000 to 1132052528
command: srsieve -q -m1e10 -P42000 -n145 -N192 -w sieve.in
srsieve2 v1.1, a program to find factors of k*b^n+c numbers for fixed b and variable k and n
srsieve: unknown option -- q
Fatal Error: srsieve: invalid option -m1e10[/CODE]

Those flags also have been changed so i dont think it will work. Tried out your mention, but i got

[CODE]Error: Could not process line phase=srsieve,144,33000,396000[/CODE][/QUOTE]

You renamed srsieve2 to srsieve. Rename back to srsieve2 and update your ini file.

[QUOTE=rogue;569204]You renamed srsieve2 to srsieve. Rename back to srsieve2 and update your ini file.[/QUOTE]


Did that and still get the Error that he couldnt process the line.



[CODE]base=71
mink=1132000000
maxk=1132052528
c=-1
npgfile=1,1_.log
npgfile=2,2_.log
npgfile=3,3_.log
npgfile=4,4_.log
phase=srsieve,144,30000,300000
phase=srsieve,192,32981,42000
phase=srsieve,240,32976,225000[/CODE]


Thats the ini i am using, just for testing reasons.
(and yes i am using the srbsieve you posted)