PrimeGrid
Please visit donation page to help the project cover running costs for this month

Toggle Menu

Join PrimeGrid

Returning Participants

Community

Leader Boards

Results

Other

drummers-lowrise

Advanced search

Message boards : Cullen/Woodall prime search : Stalled tasks

Author Message
Profile Jim_Clark
Avatar
Send message
Joined: 7 Sep 07
Posts: 42
ID: 11907
Credit: 286,805
RAC: 0
321 LLR Bronze: Earned 10,000 credits (37,581)Cullen LLR Bronze: Earned 10,000 credits (20,534)PSP LLR Bronze: Earned 10,000 credits (78,408)Woodall LLR Bronze: Earned 10,000 credits (66,612)Cullen/Woodall Sieve (suspended) Bronze: Earned 10,000 credits (22,193)PPS Sieve Bronze: Earned 10,000 credits (25,365)
Message 6902 - Posted: 11 Sep 2007 | 14:27:26 UTC

I currently have two tasks running that appear to be stalled:

status at 9:22 AM EDT --
Project Application Name CPU time Progress To compl Report deadline
PrimeGrid LLR (Woodall) 5.07 llrWOO_7825599_2 19:01:00 99.740% 00:02:58 9/16/2007 2:09 PM
PrimeGrid LLR (Cullen) 5.07 llrCULL_7863087_0 06:16:26 0.000% 01:56:40 9/17/2007 10:56 AM

Both tasks are running.
The Woodall task has been stuck at 99.740% for at least 10 hours, with "To completion" slowly
creeping up from 02:00. The data file text is:
2842171*2^2842171-1 is not prime. LLR Res64: 7AC6B4112A2D4732 Time : 82875.661 sec.

The Cullen task has been stuck at 0.000% while "CPU time" increases and "To completion" remains fixed. The data file text is:
193512827:P:0:2:1 2370345 2370345

My computer was in a hangup mode, and I had to force it off and back on to recover. These tasks may have been running at the time. Should these tasks be aborted? Should the project be reset?

____________

mdettweiler
Avatar
Send message
Joined: 25 Apr 07
Posts: 271
ID: 7489
Credit: 6,407,234
RAC: 1,797
321 LLR Bronze: Earned 10,000 credits (10,279)Cullen LLR Bronze: Earned 10,000 credits (11,460)PPS LLR Bronze: Earned 10,000 credits (14,949)PSP LLR Bronze: Earned 10,000 credits (11,016)SoB LLR Bronze: Earned 10,000 credits (16,635)SGS LLR Bronze: Earned 10,000 credits (11,081)TRP LLR Bronze: Earned 10,000 credits (10,140)Woodall LLR Bronze: Earned 10,000 credits (10,331)321 Sieve Bronze: Earned 10,000 credits (20,883)Cullen/Woodall Sieve (suspended) Bronze: Earned 10,000 credits (21,464)PPS Sieve Bronze: Earned 10,000 credits (57,241)Sierpinski (ESP/PSP/SoB) Sieve (suspended) Bronze: Earned 10,000 credits (20,499)TRP Sieve (suspended) Bronze: Earned 10,000 credits (20,039)PSA Turquoise: Earned 5,000,000 credits (6,169,287)
Message 6904 - Posted: 11 Sep 2007 | 14:50:55 UTC - in response to Message 6902.

I currently have two tasks running that appear to be stalled:

status at 9:22 AM EDT --
Project Application Name CPU time Progress To compl Report deadline
PrimeGrid LLR (Woodall) 5.07 llrWOO_7825599_2 19:01:00 99.740% 00:02:58 9/16/2007 2:09 PM
PrimeGrid LLR (Cullen) 5.07 llrCULL_7863087_0 06:16:26 0.000% 01:56:40 9/17/2007 10:56 AM

Both tasks are running.
The Woodall task has been stuck at 99.740% for at least 10 hours, with "To completion" slowly
creeping up from 02:00. The data file text is:
2842171*2^2842171-1 is not prime. LLR Res64: 7AC6B4112A2D4732 Time : 82875.661 sec.

The Cullen task has been stuck at 0.000% while "CPU time" increases and "To completion" remains fixed. The data file text is:
193512827:P:0:2:1 2370345 2370345

My computer was in a hangup mode, and I had to force it off and back on to recover. These tasks may have been running at the time. Should these tasks be aborted? Should the project be reset?

Don't reset the project, that would be unnecessary and potentially problematic. As for the Woodall result...it seems like it might have hung somehow. Considering the data fle for it, then that means that the wrapper must have crashed somehow, yet the actual scientific application continued working. Did the Woodall task display as "Running" or "Waiting to Run" when the progress was slowly increasing? If it was shown as "Waiting to Run" then that would be the wrapper hanging again. :-P Although I don't know enough about the workings of the application to give you an "official" recommendation, I would say that in that case, you'd probably be best off simply suspending all other projects until the system starts running that task, and then once it's marked as "running" it should notice that the LLR application has finished, and be done with the WU. After that, simply unsuspend all the projects you suspended. DISCLAIMER: This is just a guess, not anything for sure. I think it might be worth a try though. Just don't sue me if thigns go wrong. Hey, wait a minute...how can you sue me if I'm Anonymous? ;-)

The Cullen task that you mentioned is behaving perfectly NORMAL. Just let it keep running--Cullen workunits don't update the progress bar, this is a known bug. So they will stay at 0.000% for the duration of the WU, then jump to 100%. However, rest assured, as long as the CPU time is ticking, the workunit is running normally. (Checkpointing, fortunately, is not affected by the progress reporting bug.)
____________

Profile Jim_Clark
Avatar
Send message
Joined: 7 Sep 07
Posts: 42
ID: 11907
Credit: 286,805
RAC: 0
321 LLR Bronze: Earned 10,000 credits (37,581)Cullen LLR Bronze: Earned 10,000 credits (20,534)PSP LLR Bronze: Earned 10,000 credits (78,408)Woodall LLR Bronze: Earned 10,000 credits (66,612)Cullen/Woodall Sieve (suspended) Bronze: Earned 10,000 credits (22,193)PPS Sieve Bronze: Earned 10,000 credits (25,365)
Message 6907 - Posted: 11 Sep 2007 | 15:00:40 UTC - in response to Message 6904.

I currently have two tasks running that appear to be stalled:

status at 9:22 AM EDT --
Project Application Name CPU time Progress To compl Report deadline
PrimeGrid LLR (Woodall) 5.07 llrWOO_7825599_2 19:01:00 99.740% 00:02:58 9/16/2007 2:09 PM
PrimeGrid LLR (Cullen) 5.07 llrCULL_7863087_0 06:16:26 0.000% 01:56:40 9/17/2007 10:56 AM

Both tasks are running.
The Woodall task has been stuck at 99.740% for at least 10 hours, with "To completion" slowly
creeping up from 02:00. The data file text is:
2842171*2^2842171-1 is not prime. LLR Res64: 7AC6B4112A2D4732 Time : 82875.661 sec.

The Cullen task has been stuck at 0.000% while "CPU time" increases and "To completion" remains fixed. The data file text is:
193512827:P:0:2:1 2370345 2370345

My computer was in a hangup mode, and I had to force it off and back on to recover. These tasks may have been running at the time. Should these tasks be aborted? Should the project be reset?

Don't reset the project, that would be unnecessary and potentially problematic. As for the Woodall result...it seems like it might have hung somehow. Considering the data fle for it, then that means that the wrapper must have crashed somehow, yet the actual scientific application continued working. Did the Woodall task display as "Running" or "Waiting to Run" when the progress was slowly increasing? If it was shown as "Waiting to Run" then that would be the wrapper hanging again. :-P Although I don't know enough about the workings of the application to give you an "official" recommendation, I would say that in that case, you'd probably be best off simply suspending all other projects until the system starts running that task, and then once it's marked as "running" it should notice that the LLR application has finished, and be done with the WU. After that, simply unsuspend all the projects you suspended. DISCLAIMER: This is just a guess, not anything for sure. I think it might be worth a try though. Just don't sue me if thigns go wrong. Hey, wait a minute...how can you sue me if I'm Anonymous? ;-)

The Cullen task that you mentioned is behaving perfectly NORMAL. Just let it keep running--Cullen workunits don't update the progress bar, this is a known bug. So they will stay at 0.000% for the duration of the WU, then jump to 100%. However, rest assured, as long as the CPU time is ticking, the workunit is running normally. (Checkpointing, fortunately, is not affected by the progress reporting bug.)


Perhaps I should just abort the Woodall task. But the output file reads like the task reached a conclusion (not prime). How can this be reported?

____________

mdettweiler
Avatar
Send message
Joined: 25 Apr 07
Posts: 271
ID: 7489
Credit: 6,407,234
RAC: 1,797
321 LLR Bronze: Earned 10,000 credits (10,279)Cullen LLR Bronze: Earned 10,000 credits (11,460)PPS LLR Bronze: Earned 10,000 credits (14,949)PSP LLR Bronze: Earned 10,000 credits (11,016)SoB LLR Bronze: Earned 10,000 credits (16,635)SGS LLR Bronze: Earned 10,000 credits (11,081)TRP LLR Bronze: Earned 10,000 credits (10,140)Woodall LLR Bronze: Earned 10,000 credits (10,331)321 Sieve Bronze: Earned 10,000 credits (20,883)Cullen/Woodall Sieve (suspended) Bronze: Earned 10,000 credits (21,464)PPS Sieve Bronze: Earned 10,000 credits (57,241)Sierpinski (ESP/PSP/SoB) Sieve (suspended) Bronze: Earned 10,000 credits (20,499)TRP Sieve (suspended) Bronze: Earned 10,000 credits (20,039)PSA Turquoise: Earned 5,000,000 credits (6,169,287)
Message 6908 - Posted: 11 Sep 2007 | 15:30:21 UTC - in response to Message 6907.

Perhaps I should just abort the Woodall task. But the output file reads like the task reached a conclusion (not prime). How can this be reported?

Hmm...maybe if the admins notice this thread they can enter it into the database manually and possibly give you credit for it. Did you try making it "run" the Woodall task, though, by suspending other tasks until it does so? Maybe then it would recognize that it's done and report the result normally.
____________

Profile Jim_Clark
Avatar
Send message
Joined: 7 Sep 07
Posts: 42
ID: 11907
Credit: 286,805
RAC: 0
321 LLR Bronze: Earned 10,000 credits (37,581)Cullen LLR Bronze: Earned 10,000 credits (20,534)PSP LLR Bronze: Earned 10,000 credits (78,408)Woodall LLR Bronze: Earned 10,000 credits (66,612)Cullen/Woodall Sieve (suspended) Bronze: Earned 10,000 credits (22,193)PPS Sieve Bronze: Earned 10,000 credits (25,365)
Message 6909 - Posted: 11 Sep 2007 | 17:07:26 UTC - in response to Message 6908.

Perhaps I should just abort the Woodall task. But the output file reads like the task reached a conclusion (not prime). How can this be reported?

Hmm...maybe if the admins notice this thread they can enter it into the database manually and possibly give you credit for it. Did you try making it "run" the Woodall task, though, by suspending other tasks until it does so? Maybe then it would recognize that it's done and report the result normally.


While we were discussing this, both tasks completed, "ready to report".
The Woodall data file now reads:
193512827:M:0:2:2 2842171 2842171
instead of:
2842171*2^2842171-1 is not prime...
My guess is that 193512827 may be a factor demonstrating that 2842171*2^2842171-1 is not prime.

____________

Rytis
Volunteer moderator
Project administrator
Avatar
Send message
Joined: 22 Jun 05
Posts: 2639
ID: 1
Credit: 20,845,900
RAC: 5,668
321 LLR Silver: Earned 100,000 credits (104,475)Cullen LLR Silver: Earned 100,000 credits (291,372)ESP LLR Bronze: Earned 10,000 credits (18,156)Generalized Cullen/Woodall LLR Bronze: Earned 10,000 credits (15,259)PPS LLR Silver: Earned 100,000 credits (107,362)PSP LLR Silver: Earned 100,000 credits (116,517)SoB LLR Silver: Earned 100,000 credits (151,232)SR5 LLR Bronze: Earned 10,000 credits (14,071)SGS LLR Silver: Earned 100,000 credits (100,082)TPS LLR (retired) Silver: Earned 100,000 credits (111,607)TRP LLR Jade: Earned 10,000,000 credits (15,569,095)Woodall LLR Silver: Earned 100,000 credits (101,463)321 Sieve Silver: Earned 100,000 credits (201,501)Cullen/Woodall Sieve (suspended) Silver: Earned 100,000 credits (214,653)Generalized Cullen/Woodall Sieve Bronze: Earned 10,000 credits (14,200)PPS Sieve Silver: Earned 100,000 credits (282,191)Sierpinski (ESP/PSP/SoB) Sieve (suspended) Silver: Earned 100,000 credits (200,232)TRP Sieve (suspended) Ruby: Earned 2,000,000 credits (2,453,872)AP 26/27 Silver: Earned 100,000 credits (473,058)GFN Silver: Earned 100,000 credits (163,887)PSA Bronze: Earned 10,000 credits (97,541)
Message 6912 - Posted: 11 Sep 2007 | 17:58:37 UTC - in response to Message 6909.

The Woodall data file now reads:
193512827:M:0:2:2 2842171 2842171
instead of:
2842171*2^2842171-1 is not prime...
My guess is that 193512827 may be a factor demonstrating that 2842171*2^2842171-1 is not prime.

Not really, this is an input file format. I'm not sure what happened, but your workunit is valid, so I guess it's all ok.
____________

mdettweiler
Avatar
Send message
Joined: 25 Apr 07
Posts: 271
ID: 7489
Credit: 6,407,234
RAC: 1,797
321 LLR Bronze: Earned 10,000 credits (10,279)Cullen LLR Bronze: Earned 10,000 credits (11,460)PPS LLR Bronze: Earned 10,000 credits (14,949)PSP LLR Bronze: Earned 10,000 credits (11,016)SoB LLR Bronze: Earned 10,000 credits (16,635)SGS LLR Bronze: Earned 10,000 credits (11,081)TRP LLR Bronze: Earned 10,000 credits (10,140)Woodall LLR Bronze: Earned 10,000 credits (10,331)321 Sieve Bronze: Earned 10,000 credits (20,883)Cullen/Woodall Sieve (suspended) Bronze: Earned 10,000 credits (21,464)PPS Sieve Bronze: Earned 10,000 credits (57,241)Sierpinski (ESP/PSP/SoB) Sieve (suspended) Bronze: Earned 10,000 credits (20,499)TRP Sieve (suspended) Bronze: Earned 10,000 credits (20,039)PSA Turquoise: Earned 5,000,000 credits (6,169,287)
Message 6913 - Posted: 11 Sep 2007 | 18:01:16 UTC - in response to Message 6909.

Perhaps I should just abort the Woodall task. But the output file reads like the task reached a conclusion (not prime). How can this be reported?

Hmm...maybe if the admins notice this thread they can enter it into the database manually and possibly give you credit for it. Did you try making it "run" the Woodall task, though, by suspending other tasks until it does so? Maybe then it would recognize that it's done and report the result normally.


While we were discussing this, both tasks completed, "ready to report".
The Woodall data file now reads:
193512827:M:0:2:2 2842171 2842171
instead of:
2842171*2^2842171-1 is not prime...
My guess is that 193512827 may be a factor demonstrating that 2842171*2^2842171-1 is not prime.

Actually, you're looking at two different data files. One's the input file, the other's the output file. The one that looks like "193512827:M:0:2:2 2842171 2842171" is the input file, and the one that looks like "2842171*2^2842171-1 is not prime..." is the output file. Either way, it appears that things are all fine and dandy now. Probably the Woodall one was finished because BOINC decided to start it, which then opened the door for the wrapper to realize that the work was done and report it completed. The Cullen one, meanwhile, would have been completed normally.

You can now either wait for BOINC to automatically report the results next time it asks for more work (or, in some cases, decide that it's time to report them and do so), or you can simply select PrimeGrid on the Projects tab of the BOINC Manager and hit "Update" which will report the results to the server as complete.
____________

Profile Jim_Clark
Avatar
Send message
Joined: 7 Sep 07
Posts: 42
ID: 11907
Credit: 286,805
RAC: 0
321 LLR Bronze: Earned 10,000 credits (37,581)Cullen LLR Bronze: Earned 10,000 credits (20,534)PSP LLR Bronze: Earned 10,000 credits (78,408)Woodall LLR Bronze: Earned 10,000 credits (66,612)Cullen/Woodall Sieve (suspended) Bronze: Earned 10,000 credits (22,193)PPS Sieve Bronze: Earned 10,000 credits (25,365)
Message 6921 - Posted: 12 Sep 2007 | 1:18:42 UTC - in response to Message 6913.

Perhaps I should just abort the Woodall task. But the output file reads like the task reached a conclusion (not prime). How can this be reported?

Hmm...maybe if the admins notice this thread they can enter it into the database manually and possibly give you credit for it. Did you try making it "run" the Woodall task, though, by suspending other tasks until it does so? Maybe then it would recognize that it's done and report the result normally.


While we were discussing this, both tasks completed, "ready to report".
The Woodall data file now reads:
193512827:M:0:2:2 2842171 2842171
instead of:
2842171*2^2842171-1 is not prime...
My guess is that 193512827 may be a factor demonstrating that 2842171*2^2842171-1 is not prime.

Actually, you're looking at two different data files. One's the input file, the other's the output file. The one that looks like "193512827:M:0:2:2 2842171 2842171" is the input file, and the one that looks like "2842171*2^2842171-1 is not prime..." is the output file. Either way, it appears that things are all fine and dandy now. Probably the Woodall one was finished because BOINC decided to start it, which then opened the door for the wrapper to realize that the work was done and report it completed. The Cullen one, meanwhile, would have been completed normally.

You can now either wait for BOINC to automatically report the results next time it asks for more work (or, in some cases, decide that it's time to report them and do so), or you can simply select PrimeGrid on the Projects tab of the BOINC Manager and hit "Update" which will report the results to the server as complete.


Thanks for your prompt relies and help. Since the number 193512827 is in the input file, then my guess that "193512827 may be a factor demonstrating that 2842171*2^2842171-1 is not prime" must be wrong. But since some methods of testing for primality need a base number for the test, perhaps 193512827 is such a number.

BTW, where can I find a description or documentation of the LLR algorithm?

____________

Rytis
Volunteer moderator
Project administrator
Avatar
Send message
Joined: 22 Jun 05
Posts: 2639
ID: 1
Credit: 20,845,900
RAC: 5,668
321 LLR Silver: Earned 100,000 credits (104,475)Cullen LLR Silver: Earned 100,000 credits (291,372)ESP LLR Bronze: Earned 10,000 credits (18,156)Generalized Cullen/Woodall LLR Bronze: Earned 10,000 credits (15,259)PPS LLR Silver: Earned 100,000 credits (107,362)PSP LLR Silver: Earned 100,000 credits (116,517)SoB LLR Silver: Earned 100,000 credits (151,232)SR5 LLR Bronze: Earned 10,000 credits (14,071)SGS LLR Silver: Earned 100,000 credits (100,082)TPS LLR (retired) Silver: Earned 100,000 credits (111,607)TRP LLR Jade: Earned 10,000,000 credits (15,569,095)Woodall LLR Silver: Earned 100,000 credits (101,463)321 Sieve Silver: Earned 100,000 credits (201,501)Cullen/Woodall Sieve (suspended) Silver: Earned 100,000 credits (214,653)Generalized Cullen/Woodall Sieve Bronze: Earned 10,000 credits (14,200)PPS Sieve Silver: Earned 100,000 credits (282,191)Sierpinski (ESP/PSP/SoB) Sieve (suspended) Silver: Earned 100,000 credits (200,232)TRP Sieve (suspended) Ruby: Earned 2,000,000 credits (2,453,872)AP 26/27 Silver: Earned 100,000 credits (473,058)GFN Silver: Earned 100,000 credits (163,887)PSA Bronze: Earned 10,000 credits (97,541)
Message 6931 - Posted: 12 Sep 2007 | 6:31:56 UTC - in response to Message 6921.

It's the depth we have sieved to; have in mind that it's hardcoded to simplify wrapper development, so it has no meaning here.

http://mersenneforum.org/showthread.php?t=639 has some mathematical stuff about Lucas Lehmer Riesel test.
____________

JohnProject donor
Honorary cruncher
Avatar
Send message
Joined: 21 Feb 06
Posts: 2876
ID: 2449
Credit: 2,681,934
RAC: 0
321 LLR Bronze: Earned 10,000 credits (11,773)Cullen LLR Bronze: Earned 10,000 credits (14,945)ESP LLR Bronze: Earned 10,000 credits (26,855)PPS LLR Bronze: Earned 10,000 credits (84,876)PSP LLR Bronze: Earned 10,000 credits (15,311)SoB LLR Bronze: Earned 10,000 credits (21,440)SR5 LLR Bronze: Earned 10,000 credits (29,270)SGS LLR Bronze: Earned 10,000 credits (26,616)TPS LLR (retired) Bronze: Earned 10,000 credits (36,288)TRP LLR Bronze: Earned 10,000 credits (41,655)Woodall LLR Bronze: Earned 10,000 credits (15,807)321 Sieve Bronze: Earned 10,000 credits (20,014)Cullen/Woodall Sieve (suspended) Bronze: Earned 10,000 credits (23,405)PPS Sieve Bronze: Earned 10,000 credits (36,192)Sierpinski (ESP/PSP/SoB) Sieve (suspended) Bronze: Earned 10,000 credits (20,306)TRP Sieve (suspended) Bronze: Earned 10,000 credits (21,738)GFN Bronze: Earned 10,000 credits (86,217)PSA Ruby: Earned 2,000,000 credits (2,143,756)
Message 6937 - Posted: 12 Sep 2007 | 14:04:15 UTC - in response to Message 6921.
Last modified: 12 Sep 2007 | 14:04:28 UTC

..., perhaps 193512827 is such a number.

Here are the NewPGen formats as they relate to PG and these specific prime forms: k*b^n+1 & k*b^n-1

<sieve limit>:<mode character>:<chain len>:<base>:<mode bitmap as a decimal>

sieve limit:P:0:2:1 Cullen Prime Search
sieve limit:M:0:2:2 Woodall Prime Search
sieve limit:T:0:2:3 Twin Prime Search

Mode character:
'P' +1
'M' -1
'T' -+1 (Twin) (Also 3-tuple and 4-tuples)

chain len:
0 is just a single length chain

base: This is the 'b' value. For all three searches, the base is 2.

BitMap:
0x0001 k*2^n+1
0x0002 k*2^n-1
NOTE: 0x0003 is not listed but I presume it means k*2^n-+1

As Rytis states, the sieve depth is hard-coded for PG WU's. It has no real meaning here. To see sieving progress and depth, please visit the sieving thread:

http://www.primegrid.com/forum_forum.php?id=22

The last two numbers in PG's input file are k & n for the form k*b^n-1 and k*b^n+1. So, presuming a hard-coded sieve depth of 1000000000, this is what the following input files mean:

- Cullen
1000000000:P:0:2:1 123987 123987
Testing 123987*2^123987+1

- Woodall
1000000000:M:0:2:2 123987 123987
Testing 123987*2^123987-1

- TPS
1000000000:T:0:2:3 123987 333333
Testing 123987*2^333333-1. If this is found prime, then LLR will test 123987*2^333333+1

For more information on NewPGen, please visit:

http://primes.utm.edu/programs/NewPGen/
____________

Message boards : Cullen/Woodall prime search : Stalled tasks

[Return to PrimeGrid main page]
DNS Powered by DNSEXIT.COM
Copyright © 2005 - 2019 Rytis Slatkevičius (contact) and PrimeGrid community. Server load 1.34, 1.31, 1.25
Generated 24 Aug 2019 | 7:27:27 UTC