After successful testing the new application, this time built for Linux, I loaded Rows_PADLS_rule38 as batch 13. Windows build will come eventually.

Experiment: https://boinc.progger.info/odlk/forum_thread.php?id=104

Credit will not be awarded during validation, but later during assimilation of the batch. Credit will be granted based on the number of Latin squares checked.

Some tasks, that were already over were deleted from the database. Boinc is unfortunately not space effective.

ATM, I've completed 528 of these and counting. All successful. No credit though. :( An example.
https://boinc.tbrada.eu/result.php?resultid=101991

Explanation of credits: https://boinc.tbrada.eu/forum_thread.php?id=3016

Explanation of credits: https://boinc.tbrada.eu/forum_thread.php?id=3016

Gotcha. Thanks.

The title of this thread and the main news item on the front page says this is Rule 38 as the new work units, however rule 38 does not exist in my account, but Rule 58 does, all the work units I have received are Rule 58.
Has there been a typo and the wrong number written down?

Conan

Thank you.
The forum is right and error happened while updating the app name in database.

Tasks ready to send 0
Задания обрабатываются 9004

https://boinc.tbrada.eu/server_status.php

Tomas Brada
The job queue is empty.

Will we wait for the completion of this porcion WUs?
You can not run the next branch of the experiment (PADLS rule 15) in the new Application?

I think the participants would like to have new tasks :)

The job queue is empty.

Will we wait for the completion of this porcion WUs?

I think the participants would like to have new tasks :)

I do not need to wait for competition of the current batch. But I do not have any more rows to load into project. The application (padls3) is using the two generators that you sent me(ASS_DLK10A_R38+PSEVDOASS_DLK_NEW_R38). If there are more rows for this app, then I can load them easily.

I am not able to build a new application until next week.

You can not run the next branch of the experiment (PADLS rule 15) in the new Application?

I do not know. That is your expertise.

I do not need to wait for competition of the current batch. But I do not have any more rows to load into project. The application (padls3) is using the two generators that you sent me(ASS_DLK10A_R38+PSEVDOASS_DLK_NEW_R38). If there are more rows for this app, then I can load them easily.

This branch has no more WUs.

You can not run the next branch of the experiment (PADLS rule 15) in the new Application?

I do not know. That is your expertise.

You did not understand.

I have a new branch of the experiment PADLS rule15.
But you should start this branch in the new Application.
These are again modified generators 1 and 2.

I am not able to build a new application until next week.

OK.

Tasks ready to send 89
Задания обрабатываются 1393

https://boinc.tbrada.eu/server_status.php

Tomas Brada
where do new WUs come from?
Errors of processing? Overdue tasks?

Can you send me the preliminary results of the PADLS rule 38 experiment?

I repaired Error where retried tasks wont get assigned to hosts. (because of too high "reliability" requirement)
1399 Tasks in progress.
I started read-only assimilation (to give you partial results)
New tasks come from mainly two sources: tasks aborted by users and overdue tasks.

It appears that the large rollback caused a disturbance in the database, which will take few hours to settle. Until then, you might get network errors. But boinc is built to handle this and will report the tasks later.
Edit: the event is over, if it still does not work, report here

According to the Project, I have 766 WU's In Progress. As of 6 hours ago I had 0 WU's on my hosts, and that was the case for almost 12 hours. It looks like most of those WU's should come up for resends in about another 3 hours. I checked on one host and the sample WU's I researched don't show up as ever having made it to the host, so there must have been some problem with the original Downloads.
I do see that 2 of my hosts have gotten about 100 fresh resends recently though, so hopefully the queue will get everything through fine soon.

Mumps: There was a timeout at your host 3315, which could have been caused by the yesterday glitch. Other than that everything is nominal.
I added server option to prevent lost results in case of a glitch, but I do not expect it to be needed.