Mersenne: mprime and primenet
I just started running a recent build of mprime on a couple of linux systems, and noted an anomaly vis a vis primenet... When mprime connects to primenet, its not updating date on the rest of the worktodo, only on the exponent actually in progress. case in point... 18665107 67 13.6 7.4 67.4 26-Mar-03 12:48 18-Mar-03 17:20 xeon1b 2790 v19/v20 18665149 66 13.6 17.4 74.4 18-Mar-03 17:20 xeon1b 2790 v19/v20 18665327 66 13.6 27.4 74.4 18-Mar-03 17:20 xeon1b 2790 v19/v20 18665333 66 13.6 38.4 74.4 18-Mar-03 17:20 xeon1b 2790 v19/v20 18665377 66 13.6 48.4 74.4 18-Mar-03 17:20 xeon1b 2790 v19/v20 18670741 66 13.3 48.7 74.7 18-Mar-03 23:20 xeon1b 2790 v19/v20 18763243 66 2.2 68.8 85.8 30-Mar-03 03:38 xeon1b 2790 v19/v20 I fired this client up on the 18th, and it downloaded the 60 days I told it to. its updated the exponent its working on on the 26th, and it checked out a new one on the 30th, but it hasn't updated the other values yet. I've tried using -c manually, it communicates, updates the WIP, but doesn't update the rest of the work*.ini file. -jrp _ Unsubscribe & list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Mersenne: oh great, here we go again!
John R Pierce <[EMAIL PROTECTED]> wrote: >the numerologists are at it again... > >http://www.nature.com/nsu/030317/030317-13.html > I wonder if they tried checking it against the "Lucky Numbers" (http://mathworld.wolfram.com/LuckyNumber.html)?? Also, wasn't there someone who did some analysis on a list of numbers generated by using random numbers and the 1/ln(n) probability function? I wonder if the "numerologists" would have written the same paper using this list as well? -Shaun _ Unsubscribe & list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: Twin prime conjuncture
Whoops, that's _conjecture_, of course. :-) /* Steinar */ -- Homepage: http://www.sesse.net/ _ Unsubscribe & list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Mersenne: Twin prime conjuncture
Just saw this on Slashdot -- appearently it has been proved that there are infinitely many near-twin primes, ie. primes that are very close together without not neccessarily being twins. The article doesn't go into too much detail, but I'm sure one could follow the links and learn more. :-) http://www.siliconvalley.com/mld/siliconvalley/5483833.htm /* Steinar */ -- Homepage: http://www.sesse.net/ _ Unsubscribe & list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: Old files in my mprime dirs
Daran wrote: >> Actually the .001 extension would be expected... especially >> if running MPrime on a dual CPU box... with one instance using >> the -A1 switch... Using the -A switch will put an extension >> with the instance after it... No -A switch... no extension... > >OK. I've never used a Dual CPU Box. Actually... it doesn't matter whether it's a dual CPU box or not... it all depends on the -A switch... You could set up two instances on a single CPU box... and put a Time= line in the prime.ini file(s)... and have one without the -A switch running L-L tests at night... and one with the -A switch running factoring during the day... to reduce memory use... Note: ECM and P-1 use the -A switch for extensions... but the L-L tests and trial-factoring do not... L-L will only add an extension equal to iteration / X (where x is from interimfiles=X in prime.ini)... if interimfiles= is present... >> However... to complete the P-1s... assuming they were initiated >> by a L-L test... adding Pfactor=exponent,66 lines to the >> WORK0001.INI would do it... no ,1 is needed... since it would >> indicate the P-1 is complete... > >Not for Pfactor assignments it doesn't. Here's what undoc.txt >says >[...] >I have verified that this is correct. A '1' in the last place >causes it to choose DC limits. OK... but if the test were in progress... and not completed... MPrime has already chosen the limits... Restarting it with the DC limits... which might be different... would cause MPrime to restart the P-1 tests from scratch... A factor might be found... but if Chris didn't want to go thru the trouble... he might as well delete the files... since when double-checking gets there... the P-1 will be done... since PrimeNet doesn't know it was even started... >One question: If Chris is going to finish them on a different > - single CPU machine, would he have to remove the extension? Not if Chris used the -A1 switch to run the tests... but it would be easier to just remove the extension... and not use the -A switch entirely... if using a single CPU box... and only one instance of MPrime... Eric _ Unsubscribe & list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
