Dear all,

A new challenge has been announced! It will help us to proceed on the 5th target with its long-running tasks. The event starts on December 24 08:45 UTC, ends on December 31 08:45 UTC. All teams are welcome to participate!

We prepared special badges for the winners. They depict a molecule of leucine, an essential amino acid. Leucine contributes to the regulation of blood-sugar levels, growth and repair of muscle and bone tissue, growth hormone production and wound healing. Leucine also prevents breakdown of muscle proteins after trauma or severe stress. The name of the compound comes from Greek, λευκός (leukos, "white"). A nice reason to put it as a reward for the December competition!

A technical issue. Due to a technical error, some tasks run normally, but are reported as failed. If convenient, please abort the following tasks on your computers: app version 2.01, id<=380000, suffix _0 or _1.

For example: a task corona_Eprot_v1_run_2_nb3di_377447_3_1 should be aborted.

We are very sorry for this issue and hope it will not bring too much bother.

So corona_Eprot_v1_run_2_nb3di_377447_1_2 would validate even though the first 2 iterations of the task failed ?

It would have been better to have put it as a news item to get sent to clients for people to see in their Notices rather than rely on them visiting the web site.

Hello PDW!

So corona_Eprot_v1_run_2_nb3di_377447_1_2 would validate even though the first 2 iterations of the task failed ?

Yes. Not exact but close example: 19291710. First task failed (due to other problem), second task successfully completed with version 2.0 and third task (*_2) completed with version 2.01.

I hope that in 4 hours I will have examples from my computer.

It would have been better to have put it as a news item to get sent to clients for people to see in their Notices rather than rely on them visiting the web site.

We tried to inform active participants through various channels and at the moment we see that most of the potentially unsuccessful tasks have already been interrupted or failed. The number of tasks in progress that cannot be affected by this problem is many times larger and if participants start killing tasks without proper attention, the total losses can be much greater.

Hier gibt es eine Menge an Fehlern:

Task

(sek) Punkte Anwendung
36372992 19322777 20024 26. Dez. 2021, 7:50:58 UTC 26. Dez. 2021, 14:28:14 UTC Fehler beim Berechnen 19.354,41 19.190,08
36372993 19322778 20024 26. Dez. 2021, 7:50:58 UTC 26. Dez. 2021, 13:48:16 UTC Fehler beim Berechnen 17.333,91 17.154,97
36373064 19322813 20024 26. Dez. 2021, 7:50:58 UTC 26. Dez. 2021, 14:06:36 UTC Fehler beim Berechnen 18.252,54 18.077.44
36373068 19322815 20024 26. Dez. 2021, 7:50:58 UTC 26. Dez. 2021, 14:17:37 UTC Fehler beim Berechnen 18.702,38 18.530,92
36373069 19322816 20024 26. Dez. 2021, 7:50:58 UTC 26. Dez. 2021, 14:17:37 UTC Fehler beim Berechnen 18.683,05 18.510,41
36372990 19322776 20024 26. Dez. 2021, 7:50:58 UTC 26. Dez. 2021, 14:17:37 UTC Fehler beim Berechnen 18.643.03 18.474,64
36358132 19315352 20024 25. Dezember 2021, 22:50:57 UTC 26. Dez. 2021, 11:01:21 UTC Fehler beim Berechnen 21.030,29 20.851,45
36357938 19315255 20024 25. Dezember 2021, 22:44:37 UTC 26. Dez. 2021, 10:10:29 UTC Fehler beim Berechnen 18.760,78 18.609,97
36356618 19314595 20024 25. Dez. 2021, 21:46:12 UTC 26. Dez. 2021, 9:12:27 UTC Fehler beim Berechnen 17.471,69 17.333,73
36356626 19314599 20024 25. Dez. 2021, 21:46:12 UTC 26. Dez. 2021, 9:20:16 UTC Fehler beim Berechnen 17.888,70 17.749.31
36356640 19314606 20024 25. Dez. 2021, 21:46:12 UTC 26. Dez. 2021, 9:48:15 UTC Fehler beim Berechnen 19.236,32 19.095,45
36356675 19314623 20024 25. Dez. 2021, 21:46:12 UTC 26. Dez. 2021, 8:44:04 UTC Fehler beim Berechnen 16.415,61 16.289.36
36356580 19314576 20024 25. Dez. 2021, 21:46:12 UTC 26. Dez. 2021, 9:33:57 UTC Fehler beim Berechnen 19.714.33 19.559.73 --- CurieMarieDock auf BOINC + gezippte Eingabe, Kontrollpunkte und Fortschrittsbalken v2.01
windows_x86_64

Hier gibt es eine Menge an Fehlern:

Hello! Yes, first two tasks for workunits with number <= 380000 and application version 2.01. The next tasks for this workunits should compute successfully.

Over one hundred units already errored and other 400 on going with id <38000
Not good

We know the range of id of affected tasks and after completion of workunits (by another tasks) we try to grant credit for failed tasks and its hosts, participants and teams. I think we will do it near to finish of challenge.

We tried to inform active participants through various channels and at the moment we see that most of the potentially unsuccessful tasks have already been interrupted or failed. The number of tasks in progress that cannot be affected by this problem is many times larger and if participants start killing tasks without proper attention, the total losses can be much greater.

You could abort the workunits with issues on the server side.

---

- - - - - - - - - -
Greetings, Jens

BOINC allows to cancel work by workunit id, not by result id. And that's the problem. :)

Hello PDW!

So corona_Eprot_v1_run_2_nb3di_377447_1_2 would validate even though the first 2 iterations of the task failed ?

Yes. Not exact but close example: 19291710. First task failed (due to other problem), second task successfully completed with version 2.0 and third task (*_2) completed with version 2.01.

I hope that in 4 hours I will have examples from my computer.

Computed! :) Workunit 19313249, for example.

OMG For real?
I just quit 32 tasks that were already running for 18 hours.... -__-
At least now I know why my performance in the challenge has gone down.

---

Hi! We see this results in project database and will give credit for them.

Technical notice: after sending out all results from current queue we will return to previous targets - corona_3CLpro_v7 and corona 3CLpro_v8 for perform an additional computing.

Hi! We see this results in project database and will give credit for them.

Which results?
The aborted, that ran already for hours?
Or the wrongly marked as error?
Will this be done before the end of the challenge?

Hi! We see this results in project database and will give credit for them.

Which results?
The aborted, that ran already for hours?
Or the wrongly marked as error?
Will this be done before the end of the challenge?

Hi! The Plan: All affected results (inside a known range of id) which runs more than 1000 secods and falls with errors (or was interrupted) must take the credit equal of credit of successfull tasks for this workunit. When the results currently in the queue will be processed, we wil be able to grant the credit.

Hello,

on my both odroid - linux systems i got an error after requesting new tasks:


4218 SiDock@home 27.12.2021 20:48:57 [error] Signature verification failed for cmdock-boinc-zcp_job_1.0_aarch64-unknown-linux-gnu.xml
4219 SiDock@home 27.12.2021 20:48:57 [error] Checksum or signature error for cmdock-boinc-zcp_job_1.0_aarch64-unknown-linux-gnu.xml

Has anyone else this problem?

thank you!

We temporary disabled workunits generation for more control of switching to new workuits set. We monitor queue size!

Hello,

on my both odroid - linux systems i got an error after requesting new tasks:


4218 SiDock@home 27.12.2021 20:48:57 [error] Signature verification failed for cmdock-boinc-zcp_job_1.0_aarch64-unknown-linux-gnu.xml
4219 SiDock@home 27.12.2021 20:48:57 [error] Checksum or signature error for cmdock-boinc-zcp_job_1.0_aarch64-unknown-linux-gnu.xml

Has anyone else this problem?

thank you!

Hi everyone,

yes, i have exactly the same problem. The download of the aarch64 application fails because of signature error for the .xml file

Thank You!

Greetings

oops, double post because of server overload