Nothing better from 0-3M.
Third best is 1.1.03e-14.
I'm using stage1_norm=1e28 at these low values.
Takes about 8 hours on GTX 460 per 100K leading coeff.
Continuing whenever I get a chance.

Nothing better to 4.5M leading coefficient.
I should have more time on a GPU in the coming days.
I may reach 10M within a couple weeks.

c194 @ i5236
 

Overnight, a new number two popped out.
Still not in the desired range.
[CODE]R0: -19590035041723157218547011054582449403
R1: 975334194934990309
A0: 24137781628053720561203589791084388125707564416
A1: 3729890152208266331360779006510859657032
A2: -64245986828706004956243043613430
A3: -130509958297049266684611
A4: 2223170352185530
A5: 4695300
skew 164421929.49, size 5.428e-19, alpha -7.477, combined = 1.176e-14 rroots = 5[/CODE]

Passing through 7M (A5:) with nothing better than previously mentioned.

rich, remind me how to run msieve, and i'll try to find something.
Since it's been one year and a half I haven't run a custom poly selection, I hav forgotten almost everything.
But i didn't forgot this thread
[url]http://mersenneforum.org/showthread.php?t=18368&highlight=msieve&page=42[/url]

Thanks. According to my notes I perform 4 steps. There is further optimization using stage2-norm but I haven’t research it yet.

[CODE]1. msieve -g 0 -t 3 -mp1 “stage1-norm=2e28 20000000-21000000” -nps -v
2. sort -g -k 10 msieve.dat.ms | head -<num> > <tempfile>
3. replace msieve.dat.ms with the <tempfile>
4. msieve -g 0 -npr[/CODE]

Place the “n” number in the worktodo.ini file.
Step 1 has the norm picked for this number.
The X,Y is the range for the leading coefficient (20M-21M).
This step takes hours to run.
I can run a 100k interval on a GTX 460 in less than 8 hours.

In step 2, the -k 10 is for a 5 degree polynomial.
(-k 11 is used for a 6 degree.)
The <num> is the numéro du jour or the number of records to keep.
I usually pick anything from 30 to 50.
This step takes a few seconds.

Step 3, the new <tempfile> replaces the old msieve.dat.ms for the last step.

Step 4 takes around 10 minutes depending on the number of records saved from the sort.

VBCurtis has a good intro in this [url="http://www.mersenneforum.org/showpost.php?p=403501&postcount=107"]post[/url].

ok, i'll try to find something, quick and dirty. Going on a trip from monday morning to the 21.. So i'll probably post something monday and will resume the search after my return (if you are still looking for a good poly)

I use a similar process to RichD, but I've written scripts to automatically find the sort key: [code]
# Find out how many fields each line has.
KEY=`head -1 msieve.dat.ms | wc -w`
# The sort key is 5+the polynomial degree. 9 for degree 4, 10 for degree 5 and 11 for degree 6. So sanity check it.
if (($KEY<9)) ; then exit;fi
if (($KEY>11)) ; then exit;fi
# Now sort msieve.dat.ms on the last field on each line and save only the top few entries.
sort -g -k $KEY msieve.dat.ms | head -1000 >msieve.dat.ms.cut
[/code]
Or in perl:
[code]
# check how many fields there are in $PREFIX.msieve.dat.ms
open(IN,"< $PREFIX.msieve.dat.ms") or die "Can't read $PREFIX.msieve.dat.ms $!";
my $rec = <IN>;
my @words = split / /,$rec;
close(IN);
my $sortkey = scalar @words;
if (($sortkey<9) or ($sortkey>11)) {
logwrite("Invalid sort key $sortkey");
logwrite("First record in $PREFIX.msieve.dat.ms rec was $rec");
logclose();
die;
}

# Sort hits on the last field (score, lower is better) and save just the best ones.
$cmd = "sort -g -k $sortkey $PREFIX.msieve.dat.ms | head -200 >$PREFIX.msieve.dat.ms.cut";
$time = localtime time;
print "$time" if($ECHO_CMDLINE);
logwrite("=>$cmd") if($ECHO_CMDLINE);
$res=system($cmd);
[/code]
It's not as bad as it looks, I've added a lot of sanity checks to the code.

But it assumes all the polys msieve generates will be the same degree. So it will go wrong if we get a mixture of degrees in the same file.

Chris

We tell msieve what degree to look for, so we should never have multiple degrees of polys in the same file. I suppose it could happen if someone sent multiple GPU runs to the same file, so we shouldn't do that!

I keep all my GPU runs, but I tightly restrict my size-opt output so those files are quite small. Setting stage2_norm merely reduces the output to the .ms file; it doesn't change the poly search process itself. That means I don't use the 'head' part of the process, as I just -npr the entire (small).ms file.
This allows me to tinker with the root-opt settings on a "greatest hits" collection of, say, the best 200 hits in a week rather than just the 100-150 I get in a day from the 460M GPU.

I spend a lot more time on the -npr step than 10 minutes! But, my batches are 100-200 hits per run, and the CPU is an i7-laptop chip at 1.7ghz. I figure an extra half-hour per day of CPU time on the small chance that my 100th to 150th hits produce a good poly is worth it, compared to the large amount of watt-hours and GPU time it took to generate those hits. Generally, I'l try root-opt on any candidate from the file whose norm is within an order of magnitude of my very-best hit. For this particular number, I get 1-2 hits a day at 3e25, so I try the root-opt step on anything better than 2.5e26.

I hope this helps!

Nothing better through 12M (A5:).

back, just tried a few hours, and got

[code]
Fri Jun 26 16:23:01 2015 R0: -14135786849137023876913291436065506569
Fri Jun 26 16:23:01 2015 R1: 18969287860104342181
Fri Jun 26 16:23:01 2015 A0: 3957161515503501886407430713481202014028653753560
Fri Jun 26 16:23:01 2015 A1: 237172237772281744778864702626993430912766
Fri Jun 26 16:23:01 2015 A2: -3750924488863288259553793715871617
Fri Jun 26 16:23:01 2015 A3: -6194491949591007980204110
Fri Jun 26 16:23:01 2015 A4: 37993686710338596
Fri Jun 26 16:23:01 2015 A5: 24001560
Fri Jun 26 16:23:01 2015 skew 304604311.11, size 3.944e-019, alpha -9.639, combined = 9.389e-015 rroots = 5
[/code]