20041014, 22:15  #1 
"Mike"
Aug 2002
13·593 Posts 
M1061...
This is just a thread for all of us to post our progress on this number... I don't know if this is an optimal way to report progress but I'm sure someone will let me know if it isn't... I can't think of an easy way to do a web page with results except by accepting emails and manually updating charts and tables... If this is what we need for M1061 and other numbers like it, as well as the ones B. Silverman mentioned, I'm willing to do that... Otherwise we can have a separate thread for each number, or maybe a thread for each range or type of number...
Anyways, I think we have several things we need to accomplish or answer... 1) How do we determine what value to place on the results from different programs... For example, a stage two curve done on mprime might be worth less than one done on GMPECM... 2) How can we help new people get this running on their boxes? I can post a walkthrough for mprime and I think for GMPECM, but since I have no access to a Windows box, I don't know how to set that up, other than to use the same worktodo.ini file... 3) How often should we report progress and when do we decide to move on to a deeper bit level? 4) Do we just post the curves we have done or do we need to post additional data? Anyways, this is just an idea... Let me know if it is stupid or not... PS  Any technical discussion related to this number is highly encouraged and appreciated! Mike (Xyzzy) 
20041014, 22:16  #2 
"Mike"
Aug 2002
13·593 Posts 

20041014, 22:18  #3 
"Mike"
Aug 2002
13×593 Posts 
I've completed 102 curves with mprime using B1=44000000, B2=4290000000... I'm switching to GMPECM for a while so i can learn that program...

20041014, 22:32  #4 
"Mike"
Aug 2002
17035_{8} Posts 
The way I ran this in mprime was to make a directory with the mprime executable in it:
Code:
mkdir mprime cd mprime wget ftp://mersenne.org/gimps/mprime235.tar.gz tar zxvf mprime235.tar.gz Code:
echo "ECM=1061,44000000,0,100,0,0,0,0" > worktodo.ini Code:
echo e "AskedAboutMemory=1\nUsePrimenet=0\nOutputIterations=1000000000" > prime.ini Code:
echo e "DayMemory=256\nNightMemory=256" > local.ini I then started the program with: Code:
nohup nice 19 ./mprime d >> log.txt You can keep a terminal open to view the progress in real time with: Code:
tail f log.txt If you want to add a line to cron or a startup script to start this automatically when you boot, you can, although the procedure might be different depending on what distro you use... 
20041015, 00:44  #5 
Jun 2004
UK
139 Posts 
I've done 44 curves on M1061. It's taking approx 55 minutes with GMPECM for each stage with B1=44000000 and B2=184367799127. Is this normal for a 1.8GhZ Athlon? Are there any settings I can change which will decrease this?

20041015, 01:08  #6 
"Mike"
Aug 2002
13×593 Posts 
Once GMPECM is installed you can invoke it like this:
Code:
( echo "2^10611"  bc  tr d '\\\n'; echo )  nohup nice 19 ecm c 100 44e6 >> log.txt & If I have time in the next few days I will post what akruppa sent me about how to compile GMPECM from scratch... For now, if you run Debian, and if you are using "testing" or "unstable" you can do this as root: Code:
aptget install gmpecm 
20041015, 01:10  #7  
"Mike"
Aug 2002
13·593 Posts 
Quote:
To get CPU speed, type: Code:
cat /proc/cpuinfo  grep MHz 

20041015, 02:40  #8 
Jun 2004
UK
139 Posts 
Code:
[Fri Oct 15 01:28:43 BST 2004] GMPECM 5.0.3 [powered by GMP 4.1.3] [ECM] Input number is 24707306311927565716857342128774085333197833223161879682238935306082805123046306993647507776054336486228891340858985829027076261887914242781617846672453431386903982455635542158748401823985988322905245077938567513252198179128990807936780194781391547404884040101606295111368825026273254703636026307207764436438929167613951 (320 digits) Using B1=44000000, B2=184367799127, polynomial Dickson(30), sigma=1289006054 Step 1 took 2112262ms Step 2 took 2075776ms Oh and if you run ecm v then it tells you it recognises the number as 2**1061  1 along with lots of building Gs. 
20041015, 02:56  #9  
"Mike"
Aug 2002
13×593 Posts 
Quote:
Here is what it says: Code:
Using special division for factor of 2^10611 Code:
./test.ecm ecm ./test.pp1 ecm ./test.pm1 ecm 

20041015, 04:54  #10 
Jun 2004
UK
139 Posts 
Yep I compiled it and have the scripts and they erm passed. I guess my Athlon is just slow.

20041015, 06:39  #11 
Mar 2003
New Zealand
13·89 Posts 
Here are a few curve times that will give a guide for what to expect from P4 based machines.
Times are in seconds. The Celeron runs at 2.88GHz, P4 times have been scaled slightly to match. P4 (HT) times are for the average of two hyperthreads. Versions: mprime 23.9, gmpecm 5.0.3, libgmp 4.1.4. Code:
mprime gmpecm Stage  S1 S2  S1 S2 S2 S2 S2 S2 S2 S2 B1/B2  44e6 4.3e9  44e6 4.3e9 11e9 15e9 22e9 45e9 90e9 180e9 ++ Celeron  546 260  1629 117 238 281 382 764 P4  545 247  1625 108 219 259 349 709 1120 1726 P4 (HT)  472 193  1268 90 180 217 292 595 standard curves as 19300*ecmprob(44e6,B2',sqrt(10)*10^49,k*dF^2,poly): Code:
B2 4.3e9 11e9 15e9 22e9 45e9 90e9 180e9 polynomial 12 12 12 12 30 30 30 Standard curves 1.08 1.34 1.42 1.53 1.84 2.08 2.34 Daily output (P4) mprime 118 gmpecm 54 63 65 67 68* 65 60 mprime+gmpecm 143 152 153* 148 127 108 89 
Thread Tools  
Similar Threads  
Thread  Thread Starter  Forum  Replies  Last Post 
Predict the number of digits from within the factor for M1061  Raman  Cunningham Tables  12  20130617 21:21 
M1061 factored!!!  lycorn  NFS@Home  28  20120830 04:40 
Anyone have an ETA for M1061?  Stargate38  NFS@Home  99  20120805 09:38 
M1061  t60  Andi47  Factoring  122  20111125 09:18 
P1 on M1061 and HP49.99  ATH  Factoring  21  20091013 13:16 