All three all running WCG CPU only. Two of the boxes can run GPU tasks, but one of them continuously gets computation errors on Einstein when running WCG, so I paused Einstein on it for a while. One box is still crunching away at some Einstein units, I think, but it's definitely done with what WCG it has. 9 more hours, I'll probably just sit tight because I'm working and can't do anything that will take more than a few minutes.
#!/bin/bash
while true ; do
boinccmd --get_tasks | grep -B12 -A4 EXECUTING | grep ' name:\|checkpoint' | grep -B1 'time: [89][0-9][0-9]' | grep 'name:.*eah' | sed -e 's/^ *name: //' | xargs -n1 -I{} boinccmd --task http://einstein.phys.uwm.edu/ {} suspend
sleep 30
doneI thought every race had a defined starting time. Can you explain in more detail?
Every race has a time when SETI.Germany collects starting stats from a site. Once they've done that, they'll post starting stats here and you can flush. Sometimes a site isn't accessible for awhile, like one last year. If they don't post stats immediately, hold your flush until they post stats.
I don't understand. Did the Einstein work fail to resume? Or did my script prevent it from progressing? (It should do that; you should stop the script before dumping results.)
Oh, that's definitely too long. Typically I was seeing a minute or two before resumption of GPU usage, mainly on machines with slower CPUs.
