[QUOTE=paulunderwood;526476]Here is the script that handles multiple header lines in a file:

[CODE]open INFILE, "<@ARGV[0]" or die "Need input file\n";
open OUTFILE, ">@ARGV[1]" or die "Need output file\n";

while ( <INFILE> ) {
if( $_ =~ /\[/ ) {
@header = split( ' ', $_ );

@expression = split( '\$', @header[1] );

@start = split( '\[', @header[2] );
@start = split( '\]', @start[1] );

$current = @start[0];
} else {
$current += $_;
}
print OUTFILE $expression[0].$current.substr($expression[1],1)."\n";
}
[/CODE][/QUOTE]


THANKS, works perfect!

[QUOTE=rebirther;526420]@rogue:

a feature request for srsieve2, the x factors found is uninteresting for me, can you replace it with x factors left + factors found rate f/sec? The factors left total I can only see at the end of sieving.[/QUOTE]

I'll think about it. It would likely need another switch to control what to show, i.e. factors found or remaining terms.

[QUOTE=rogue;526486]I'll think about it. It would likely need another switch to control what to show, i.e. factors found or remaining terms.[/QUOTE]


And to spend time the prp output file.

[QUOTE=rebirther;526499]And to spend time the prp output file.[/QUOTE]

I believe I added that in the latest build. Try -fB. I call it BOINC format since it is used for input to BOINC.

[QUOTE=rogue;526501]I believe I added that in the latest build. Try -fB. I call it BOINC format since it is used for input to BOINC.[/QUOTE]


nope, still not working

[QUOTE=rebirther;526512]nope, still not working[/QUOTE]

In what way is it not working? is this the missing carriage return or something else?

[QUOTE=rogue;526514]In what way is it not working? is this the missing carriage return or something else?[/QUOTE]


Fatal error: invalid argument

[QUOTE=rebirther;526547]Fatal error: invalid argument[/QUOTE]

See [URL]https://www.mersenneforum.org/showpost.php?p=524883&postcount=195[/URL]. SVN hasn't been updated yet to add this fix.

Sorry, but I have been busy and haven't had time to make changes.

[QUOTE=pepi37;526221]Hit error one more time, now on twinsieve[/QUOTE]

I haven't been able to reproduce this yet. It might be fixed with some other changes I've made to the framework, but I don't know right now. I need to continue testing.

I did find a bug that can occur when using multiple threads. I suspect that might be behind the error you encountered.