Problem with the badge-status-page.

Author	Message
Aurel Send message Joined: 25 Feb 13 Posts: 211 Credit: 8,816,142 RAC: 5	Message 887 - Posted: 25 Jul 2013, 20:12:13 UTC Hi @all, if seen some little problems in the badge-status-page, so I´ll just inform you. I´ve seen it in the 13. Subfield of the bounded app, now I compute WU´s from "SF124-1_Idx9", but only to "SF124-3_Idx6" are to see in the status. (That means: "SF124-1_Idx9" haven´t started yet, if you trust the status page. Greetings from Germany, Aurel eLISA-Supporter theoretical physics ID: 887 · Rating: 0 · rate: / Reply Quote

Eric Driver Project administrator Project developer Project tester Project scientist Send message Joined: 8 Jul 11 Posts: 945 Credit: 104,214,880 RAC: 68,254	Message 888 - Posted: 26 Jul 2013, 2:58:45 UTC - in response to Message 887. Hi @all, if seen some little problems in the badge-status-page, so I´ll just inform you. I´ve seen it in the 13. Subfield of the bounded app, now I compute WU´s from "SF124-1_Idx9", but only to "SF124-3_Idx6" are to see in the status. (That means: "SF124-1_Idx9" haven´t started yet, if you trust the status page. Greetings from Germany, Aurel eLISA-Supporter theoretical physics Sorry, I just need to turn it on inside the script. I usually wait until some WUs have been returned, so that the ETA is more accurate. The ETA is computed as (#WUs left)/(max(1,#finished in last 24 hrs)), so when no WUs have been returned, this is a very bad estimate. ID: 888 · Rating: 0 · rate: / Reply Quote