Unreported Assignment
 

I was looking at the Active Assignment report to see if we were keeping ahead of the wavefront on DC. For a while we were by about 300-400 exponent, but then yesterday about 3000 got reserved in a short span of time.

At first I thought that the DC TF range on GPU272 got extended to the 29M mark, and the [url]http://gpu.mersenne.info/reports/available/[/url] report showed exponent available in the 29M range for about an hour but then they disappeared. So clearly the system is configured to report exponent in the 29M range, but right now it's reporting none. Yet if we look at the [URL="http://mersenne.org/assignments/?exp_lo=29000000&exp_hi=30000000&execm=1&B1=Get+Assignments"]first 1000 Exponent[/URL] assigned in the 29M range, 720 of them belong to gpufactor - dd_work. Have they fallen thru a crack in the system?

Funny, looks like I can't edit my post... (Guess I can't edit top post in a thread) :surprised

Anyway, I did some further investigation and the 28M range is properly reported, all 5289 exponent. So it looks like it's only the 29M range that isn't reported.

Here are the top 5 userid in the 28M range

[CODE]
gpufactor 5289
matt_joe 3241
ANONYMOUS 2263
ckdo 1682
TheJudger 245
[/CODE]

[QUOTE=diamonddave;280679]Funny, looks like I can't edit my post... (Guess I can't edit top post in a thread) :surprised

Anyway, I did some further investigation and the 28M range is properly reported, all 5289 exponent. So it looks like it's only the 29M range that isn't reported.

Here are the top 5 userid in the 28M range

[CODE]
gpufactor 5289
matt_joe 3241
ANONYMOUS 2263
ckdo 1682
TheJudger 245
[/CODE][/QUOTE]

Stupid programmer error (read: my fault). Those in the 29M range were supposted to have been returned to PrimeNet, but weren't. They weren't "lost" by the system, just to GUI. They're displayed now.

I will probably throw them back since we already have enough work below 29M at the moment.

[QUOTE=diamonddave;280679]Funny, looks like I can't edit my post... (Guess I can't edit top post in a thread) :surprised
[/QUOTE]
There's a time limit on this forum, I [i]think[/i] it's an hour since your last edit (or OP as the case may be).

Edit limits
 

I believe it's an hour since the original post.

I'm pretty sure I've edited stuff after an hour, but only because I'd been editing it every twenty minutes. What we really need is Xyzzy to answer for us. (And while we're on it can we shorten or get rid of the 120 seconds between posts rule? I run it to it more than is probably healthy for me.)

(For instance I am writing this sentence while staring at the thing telling me I have to wait 42 seconds.)
(14 s.)
(3 s.)

[QUOTE=Dubslow;280756]I'm pretty sure I've edited stuff after an hour, but only because I'd been editing it every twenty minutes. What we really need is Xyzzy to answer for us. (And while we're on it can we shorten or get rid of the 120 seconds between posts rule? I run it to it more than is probably healthy for me.)

(For instance I am writing this sentence while staring at the thing telling me I have to wait 42 seconds.)
(14 s.)
(3 s.)[/QUOTE]

The first step to healing is admitting you have a problem. :smile::smile::smile:

:kitten:

[QUOTE=KyleAskine;280778]The first step to healing is admitting you have a problem. :smile::smile::smile:[/QUOTE]

Indeed :P
If he could, my roommate would remove Prime95 from my computer :P

The spider is again running wild again... I haven't verified the 56M range, but for the 57M range gpufactor as 1333 exponent of the first 3000 reserved LL tested. None show up in the [url]http://gpu.mersenne.info/reports/available/[/url] report

Sure enough I was able to reserve the 2 following assignment... yet range 56M and 57M still don't appear in the available report.

[CODE]
56140813 LL TF 70 72 2011-12-17 07:59:36
57001093 LL TF 70 72 2011-12-17 07:59:50
[/CODE]

[QUOTE=diamonddave;282557]The spider is again running wild again...[/QUOTE]

Whoops. Stupid programmer error... Fixed.

[QUOTE=diamonddave;282557]Sure enough I was able to reserve the 2 following assignment... yet range 56M and 57M still don't appear in the available report.[/QUOTE]

Candidates which are reserved by the spider but are not "interesting" are still placed in the same SQL table, but with a field called "Back" set for the un-reservation spider to use. This was an addition to facilitate the anonymous transfer for true LL/DC work.

Unfortunately, I had forgotten to add a clause in the LLTF and DCTF reservation SQL query to ignore any candidates which were set to be returned to PrimeNet (note that the un-reservation spider wouldn't release any which had been assigned to Workers even if the Back field was set).

This is how you were able to reserve them -- by giving higher than normal bounds. Also now fixed.

Thanks for pointing that out.