[QUOTE=James Heinrich;282943]I'm pretty sure by "GPU-P1" and "GPU-DC" [i]petrw1[/i] is referring to assignments from [url=http://www.gpu72.com]www.gpu72.com[/url] as opposed to actually doing the work on a GPU.
[/QUOTE]

Gold star for James

[QUOTE=petrw1;282944]Gold star for James[/QUOTE]

Make that two!

I'll put at least one core on P-1 duty... after I'm done with some DC AVX testing...
Maybe more, depending on how much LL/DC I want to do... (though with petrw1 on DC duty the milestone should be just fine, so I think it'll be LL or P-1... I do need one core for the 460...) we'll see. I'll stick with one core for now.

[QUOTE=petrw1;282939]let's hope there will be others to take over my share of P-1 (15 per day).[/QUOTE]

I currently have 3 cores running P-1, completing 3/day. I added these about 10 days ago. I might get more memory soon, in which case I could bump it up to all 4 cores and so approximately 4/day. Not much compared to 15/day, but much better than nothing!

[QUOTE=Mini-Geek;282993]I currently have 3 cores running P-1, completing 3/day. I added these about 10 days ago. I might get more memory soon, in which case I could bump it up to all 4 cores and so approximately 4/day. Not much compared to 15/day, but much better than nothing![/QUOTE]


Mine is not quite 2/day with one core. Could be 2 if I let it use the lower bounds of 72 bits.

We seem to be out of P-1 candidates <50M and factored to 72 bits. Did you do a mass unreservation or is P-1 suddenly so popular?

[QUOTE=garo;283077]We seem to be out of P-1 candidates <50M and factored to 72 bits. Did you do a mass unreservation or is P-1 suddenly so popular?[/QUOTE]

The latter.

Can I request you list the expiration times in the 'View Assignments' report? I had accidentally reserved a good three months of work of TF, and the half of it I had not done expired a couple of days ago while I was servicing those without GPU's. If it weren't for the fact that I can't get mfaktc-0.18 to work, I wouldn't have noticed that they had expired and would have been chugging through them.

[QUOTE=Dubslow;283091]Can I request you list the expiration times in the 'View Assignments' report? I had accidentally reserved a good three months of work of TF, and the half of it I had not done expired a couple of days ago while I was servicing those without GPU's. If it weren't for the fact that I can't get mfaktc-0.18 to work, I wouldn't have noticed that they had expired and would have been chugging through them.[/QUOTE]

Take the "Assigned" date, add one to the month. if ($Month == 13) { $Month = 1; $Year++; } :smile:

I also highlight in red (and add an asterisk) any assignment which is within five days of expiring on the "View Assignments" page.

I'm not sure what else I can do, other than perhaps automatically e-mailing users when they are at risk of having assignments expire.

[QUOTE=chalsall;283092]Take the "Assigned" date, add one to the month. if (Month == 13) { $Month = 1; $Year++; } :smile:

I also highlight in red (and add an asterisk) any assignment which is within five days of expiring on the "View Assignments" page.

I'm not sure what else I can do, other than perhaps automatically e-mailing users when they are at risk of having assignments expire.[/QUOTE]

Just noticed I have a few that are 30 days old today but no red asterisk.
Does this only apply to TF? Mine are P-1. I may also have some DC or LL in the future that will be more than a month old.

[QUOTE=petrw1;283093]Just noticed I have a few that are 30 days old today but no red asterisk. Does this only apply to TF? Mine are P-1. I may also have some DC or LL in the future that will be more than a month old.[/QUOTE]

Sorry; should have been clearer.

TF work expires after a month unless an extension is requested. This is clearly stated on the assignments page.

P-1 work expires after three months.

DC/LL work is formally transferred to the control of PrimeNet, so its expiration policy governs.