Error at Batch Status

Author	Message
Aurel Send message Joined: 25 Feb 13 Posts: 216 Credit: 9,899,302 RAC: 0	Message 1015 - Posted: 17 Apr 2014, 8:57:41 UTC Hi Eric, I saw at the bounded part [SF 21] that 16_Idx3 is allready computed. Thats wrong. I have at my PC one WU from it. 6358 is the data who is not ready. The WU: http://numberfields.asu.edu/NumberFields/workunit.php?wuid=6229492 Please take a look at it. Happy easter. ;) ID: 1015 · Rating: 0 · rate: / Reply Quote

Eric Driver Project administrator Project developer Project tester Project scientist Send message Joined: 8 Jul 11 Posts: 1330 Credit: 438,579,945 RAC: 512,567	Message 1016 - Posted: 17 Apr 2014, 15:02:27 UTC - in response to Message 1015. Hi Eric, I saw at the bounded part [SF 21] that 16_Idx3 is allready computed. Thats wrong. I have at my PC one WU from it. 6358 is the data who is not ready. The WU: http://numberfields.asu.edu/NumberFields/workunit.php?wuid=6229492 Please take a look at it. Happy easter. ;) Hi Aurel, That behavior is actually normal. When there is less than .1% left to go, I consider it essentially complete, and turn off that line in the table. I do this to reduce the load on the server, because every line in the table requires a database query. Those last few WUs are just as important as the others, so please don't abort them just because the table shows the batch as complete. ID: 1016 · Rating: 0 · rate: / Reply Quote

Aurel Send message Joined: 25 Feb 13 Posts: 216 Credit: 9,899,302 RAC: 0	Message 1017 - Posted: 17 Apr 2014, 23:19:13 UTC - in response to Message 1016. I don´t abort them... ;) I´ve compute all WU´s I get, new testing some WU for Wildlife@Home...^^ ID: 1017 · Rating: 0 · rate: / Reply Quote