85 wus validated, 0 wus invalid validation

Well done, guys!!
Is it ready for production, going out from beta status??

I want to wait one day more to be sure, but the numbers look good! We will restart the non-beta projects soon.

There are some details that we want to improve with the checkpoints, but, at least now, you won't get non valid results when the computation is done right.

Best,
Jesús.

---

Jesús Carro
Universidad San Jorge
@InSilicoHeart

Just discovered this project. Downloaded 58 tasks and just got started.
See how it goes.

It's working and making progress, but the CPU is quite cold ... does it do actual computations ?

It's working and making progress, but the CPU is quite cold ... does it do actual computations ?

I checked with BoincTasks and its running 87-91% per core.

35 of the first 58 done ok.
Have a bunch more to work through.
Now 102 stored.

I suspended yesterday evening 3 beta's to shutdown the PC overnight.
I watched the checkpoints were set. Progress was at about 88% after 1hr40m runtime.
This morning I resumed the three tasks at the same time.
One task resumed from the last checkpoint, the other 2 started from zero.

The two tasks that did not resumed from the last checkpoint:
https://denis.usj.es/denisathome/result.php?resultid=2110666
https://denis.usj.es/denisathome/result.php?resultid=2110975

I suspended yesterday evening 3 beta's to shutdown the PC overnight.
I watched the checkpoints were set. Progress was at about 88% after 1hr40m runtime.
This morning I resumed the three tasks at the same time.
One task resumed from the last checkpoint, the other 2 started from zero.

I've had the same problem
Admins knows the situation

I've had the same problem
Admins knows the situation

I've uploaded the beta_0.17 that should solve this issue (I hope). Issues with checkpoints are the most difficult to solve, thank you for all the information. It helps us a lot.

Best,
Jesús.

---

Jesús Carro
Universidad San Jorge
@InSilicoHeart

I've uploaded the beta_0.17 that should solve this issue (I hope). Issues with checkpoints are the most difficult to solve, thank you for all the information. It helps us a lot.

Best,
Jesús.

I just tested v0.17 on another machine. I suspended all 4 tasks after the 2nd checkpoint with "Leave tasks in memory while suspended" not selected.
I resumed the 4 one by one. All four started from scratch. What was wrong with v0.14?

Hi Crystal,
Thank you very much for this information. The problem with the v14 was the same: in some circunstances, the checkpoint is partialy saved in windows (we are trying to understand why). When we detect it, it's necessary to restart the simulation (the checkpoint is no valid). In version 14 the simulation was not restarted and, in many cases it generated non valid results. In this version it restarts the simulation but you will send valid results and you will receive credit.

We will continue trying to find why the checkpoints are not working in some windows machines.

Best,
Jesús.

---

Jesús Carro
Universidad San Jorge
@InSilicoHeart

We will continue trying to find why the checkpoints are not working in some windows machines.

I think is more important to have valid wus (scientific results) than checkpoint (the working units are not so time consuming).
But if they resolve the checkpoint problem, is great!

We will continue trying to find why the checkpoints are not working in some windows machines.

Thanks Jesús for your information.

I just ran 2 of your tasks with the previous version 0.14 to understand what's the difference.
I suspended those two tasks several times and after a resume they restarted from the last checkpoint, at least did not went back to zero.
However in the result log I see several times Problem reading the states from the checkpoint file... Restarting the simulation, but
not all previous iterations are repeated. So maybe those results are not valid scientifically for you.

https://denis.usj.es/denisathome/result.php?resultid=2136910
https://denis.usj.es/denisathome/result.php?resultid=2137064

ver.0.16/017

Irregular behavior of the checkpoints time keeping when boinc is exited and restarted.
Some times when restarting a few of the higher completion % are "normal" and continue to finish , the others restart at 0% with time resets at, in my case at 57 minutes timing ok
others would start at 0% .... 57 minutes ( normal estimate) but would continu adding time ( remaining) at the point of cut-off( exited.).

May I suggest a possibility that it could be regional settings of the computers that is confusing the computation.
I'm in Canada, in the province of Québec ( french). So that means that my keyboard is normally CAFR but win 11 is English canadian language ( multi-lingual country) but MS added for some reason a package for UK local experience language pack. it also means that my date is expressed 22022-08-03. The time is 24hr format.
So could that cause a problem?

my date is expressed 22022-08-03. The time is 24hr format.
So could that cause a problem?

So you're 20000 years in the future. Tell is what the past was like, thanks.

not seeing any issues on my system.
tasks are done in 58 minutes to just a bit over an hour.
I only shut my system down at 0000 CET and turn it back on at 0830 while I am working.
So I do not keep a close eye on anything.
And it looks like I really don't need to, which is nice.

I think we have found the problem... Beta 0.18 uploaded for Windows and Linux (I will do later for MacOS). Could you check?

Thanks!

---

Jesús Carro
Universidad San Jorge
@InSilicoHeart