After 5 hours 26 min 52 sec runtime: http://150.254.66.104/gaiaathome/result.php?resultid=2291547

I had 2 WUs that were continuing to run past 6 hours (on different machines). I just aborted them. Hope I didn't do that prematurely. (I've only had 1 2_Gaia WUs complete successfully so far)

---

I am waiting for end of wus in progress and I will change 2_Gaia app to shorter time for each wus ....

increase the difficulty of the task

<workunit>
<name>######</name>
<app_name>2_Gaia@home[20201013.11]</app_name>
<version_num>100</version_num>
<rsc_fpops_bound>86400000000000.000000</rsc_fpops_bound>

or decrease application performance

<app_version>
<app_name>2_Gaia@home[20201013.11]</app_name>
<version_num>100</version_num>
<flops>424268477.267049</flops>

by changing the size of the task, you keep the proportion, but it is too optimistic

changing the difficulty of a task is easiest.
performance is recalculated by the client after the test and task completion

At threadopener

Holy Cow , 60K seconds and a lousy 8.33 points for real !?

My validated 2_Gaia WUs haven't been that stingy on credit. Nothing to holler about either :).

---

The revised 2_Gaia have a large drop in credits today compared to earlier (yesterday). I assume this change happened after a fix to stop the timeouts as my machine is now running tasks longer. I am fine with 40-60 cr/hour on this machine, however, the current WUs are at 9.15 credits regardless of time which results in 2 to 3 cr/hour.

...something got messed up somewhere....

I may run into this error soon as I have 3 work units that are using cpu but have been running 10, 12 and 15 hours.
The time remaining has run out on two of them and 3 seconds left on the other but it will take a long time to do those 3 seconds.

Thanks
Conan

---

Finally the task http://150.254.66.104/gaiaathome/result.php?resultid=2338280 mentioned here

ended with the error EXIT_TIME_LIMIT_EXCEEDED after almost 36 hours runtime.

Too many long running tasks that end in error...I have decided to set my machine to no new tasks for the time being until the current kinks are worked out.

Should we manually cancel tasks that are being calculated much longer than 2 hours, let's say those running over 5 hours? They are in infinite loop or something? I've got 2 tasks running over 10 hours and they will probably end with errors.

My previous solution was limited to 2h calculations, it does not work perfectly because sometimes the computation time is very long for one loop.
I checked the time every one loop.
I will change to a protection using kernel signals and I will terminate the process after max 3h ( 2h for normal time without problems). Next will send a signal of correct process ending to boinc and i will save temporary results.
I hope that this solution will save your credits .....

I wonder if there is not something else that might be causing problems..
This WU http://150.254.66.104/gaiaathome/workunit.php?wuid=1164886, the first two tasks were aborted after long run times. However the third task seemed to run for the normal length of time and was valid. So why were two tasks screwy and yet the WU still ended up having good results? Is there still some sort of calculation bug in the system that would lead one set of hardware to go to an infinite loop yet another set of hardware runs just fine?

I had 2 WUs that were continuing to run past 6 hours (on different machines). I just aborted them. Hope I didn't do that prematurely. (I've only had 1 2_Gaia WUs complete successfully so far)

Hey that's good for me passing you...ol buddy!!! :-) :-)))

---

It is problem of numerical integrations...
Nominal star travels long distance from the Sun ( long integrations step, short calculation time for it)
Next 10 clons of star travel silimary distance (short calculation time)
Next clons travel very close to Sun ( short integration step, long calculations time) - and this situations is problematic
I plan stop at the moment calculations and save previous 10 clones.

Long running tasks are not necessarily bad, if they are needed to perform the calculations properly. But they should give more credits, based on the longer run times.

And you really should add checkpoints so the tasks don't have to start over at 0% if they are paused or interrupted (computer reboot, for example).

And you really should add checkpoints so the tasks don't have to start over at 0% if they are paused or interrupted (computer reboot, for example).

+1

And you really should add checkpoints so the tasks don't have to start over at 0% if they are paused or interrupted (computer reboot, for example).

+1

+1