![]() |
![]() |
#1 |
Oct 2004
Austria
2·17·73 Posts |
![]()
Is there a way to resume an msieve poly search job (e.g. when I had to restart the PC fore some reason)?
I mean other than manually doing the following: * skimming the msieve.dat.p file to get an estimate where to continue (let this be A5_0) * guessing how much time it has used until the PC had to be restarted (let this time be t1) * remembering the time limit msieve automatically sets for this size of jobs (or look it up in the msieve.log), let this be t2 * rename the msieve.dat.p file * start an msieve -np job with starts at A5_0 for t2-t1 minutes * after the run has finished skim the new and the old (renamed) .dat.p files for the best poly to create an msieve.fb file ? (in other words: it would be nice to have an msieve -np -resume flag which does all these steps automatically. Maybe msieve should write a timestamp to each poly it finds to the .dat.p file - and a timestamp each hour just in case no poly was found since the last hour - to get a good estimate for t1) |
![]() |
![]() |
![]() |
#2 |
Sep 2009
22×5×72 Posts |
![]()
Unless I misunderstood what you want to do: a way to record the last A5 value on which msieve computed, so that you can use it later with msieve -np X,Y, is to record the msieve screen output to a log file (msieve -l, msieve -v &> logfile, etc.)
![]() |
![]() |
![]() |
![]() |
Thread Tools | |
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Best msieve poly scores | VBCurtis | Msieve | 209 | 2023-08-18 20:53 |
Poly search candidates | schickel | Msieve | 32 | 2013-11-05 19:11 |
Poly Search vs Sieving times | EdH | Factoring | 10 | 2013-10-14 20:00 |
gpu poly search error | bdodson | Msieve | 10 | 2010-11-09 19:46 |
Poly search for c157 from 4788:2422 | henryzz | Aliquot Sequences | 59 | 2009-07-04 06:27 |