C225_122_79 (14e) factored.
 

[code]
p87 factor: 452517561431020563705780262154795670678440403065919061321475144777983343483047553956607
p138 factor: 943637697543405219582632111467924078907057158984932138692742662198386064163502200246441411998100003569418599154169898244584780293141023907
[/code]

Log: [url]http://pastebin.com/UG7gBGyi[/url] and attached.

Reserving 5659_67_minus1 (14e).

Reserving 6007_67_minus1 (14e).

What's up with C202_134_51?
 

The .dat.gz file for C202_134_51 appears to be truncated on the server. As of now the status page is showing 109,337,484 relations, but the file only has about 10,000,000 lines.

Can anybody fix that?

[QUOTE=jyb;436931]The .dat.gz file for C202_134_51 appears to be truncated on the server. As of now the status page is showing 109,337,484 relations, but the file only has about 10,000,000 lines.

Can anybody fix that?[/QUOTE]

My mistake! On the back end C200_134_76 is labeled as C202_134_51, which means it was included in my clean-up a few days ago and was deleted by my script. Time to run it a third time! :brian-e:

I've queued it. When a number is added again, it must be given a new name. If the old name is reused, BOINC will still pick up the old poly. The relations I deleted would have still been for the wrong poly.

Is somebody giving more work units to C211_123_77, C225_122_79, and P55_5_minus1 (all 14e)? All of these numbers have been factored already!

It would probably be a good idea for somebody with the access to clean up the 14e status page and incorporate all of the reservations/results in this thread, so this sort of thing doesn't happen. Right now a whole lot of CPU time is being used for nothing.

I have gone through 14e and clearing up the jobs that have been finished. It was slightly tedious because I had to do them one at a time and the page is very slow to update after each one.

I have deleted P55_5_minus_1 because it's already factored, and claimed C206_134_84 for post-processing myself.

[QUOTE=fivemack;436973]I have gone through 14e and clearing up the jobs that have been finished. It was slightly tedious because I had to do them one at a time and the page is very slow to update after each one.
[/QUOTE]

Not sure if related but more than 1M tasks were queued to 16e.

Reserving C211_148_132

[QUOTE=pinhodecarlos;437061]Not sure if related but more than 1M tasks were queued to 16e.[/QUOTE]

My time is very limited of late, so I queued all of 6,383-, 7,353+, 7,353-, and 2,1009+.

[QUOTE=frmky;437087]My time is very limited of late, so I queued all of 6,383-, 7,353+, 7,353-, and 2,1009+.[/QUOTE]

At current rate that's only 25 days of work...still to decide if I should request another BoincStats challenge. Which composites are we doing after these ones?

Edit: let's see what happens if I request support to run the 16e to several teams....hehe