Let's see: knreed on Friday night left, his wife waiting on him to help pack. Yesterday was a festive day in the USA, so I'm not expecting anyone to start working ''behind the scene'' at 6 AM on a none-urgent issue. Propose to allow some patience for the techs to get their barings sorted.

thx

--//--

You really thought that in normal day operation there would be a script to do this? Amazing.

I'm afraid that you're behind the times. This is what we use, the key that needs to be hit flashing and it giving audiovisual cue: "hit me, hit me, hit me"



(no no, not with that rhythm stick of Ian Dury and the blockheads ;P)

--//--

I seem to have one stuck in pending validation:

BETA_E202698_324_C.26.C22H14N2SSi.00057698.4.set1d06

Killing job because cpu time has been exceeded. Subjob start time = 1381893703, Subjob current time = 1088346282
[05:05:06] Finished Job #15
05:05:29 (5608): called boinc_finish

Any chance of credit?

The No Replies and Too Late's continue to Vanish:
My β No replies are now down to 4, Too Late's down to 6 and Valid's down to 85. PV still at 15.
Of course we won't know until the next stats update if there was any credit granted for these Too Late's, No Replies or PV's.

For all my Too Late's (all HPF2) and No Replies there are other people with either No Reply, Too Late, Aborted or Error messages; sometimes as many as 5.

Is there any point using the "Try Validation" option for the PV's; does Try Validation mark these tasks for Validation during the next Validation cycle?