Sorry for the downtime. Compiling mysql took longer than anticipated.
Not only that, But I also messed up the server so it took some time to recover.
And even more issues caused unavailability till I could get physical access.
Note: the even is now over.
19 Sep 2019, 7:37:06 UTC · Discuss
PADLS TOTAL rule 51 experiment results
Over three months, more than 700,000 unique CFs ODLS were found in the project, including 5 rare groups of ODLS pairs (three and four)
4aaDeGad55oibfG3R1RrfDqfd HnfCEigSPPx2j1wSk7j4eHbzu WRqTwJBMwRSrxCwU8HuABxmVd XMdqZKcXKLmHNmAVVRU7kEHhu ZzXhNvGzUL8TAnCnw6wE3qCnU
This project has badges now!
They are based on total credit, but I did not want to be usual, so I choose thematic thresholds.
Lv. 8) Over 6204 credits. Lv. 9) 37224 Lv.10) 197600 Lv.11) 785997 Lv.12) 2629687 Lv.13) 6873318 Lv.15) 16350666 Lv.17) 84584914
Padls Total subproject running fine
Better late than never. The PADLS Total experiment described in this thread is running fine on this server and is producing good results.
Technical: the search space has been split to so called segments. From each segment one workunit is generated. The workunits can be made any size, but are currently set to run approximately two hours on my computer. Once result of a workunit is returned to the server, it is picked up by the validator program. This program checks the result validity, saves the result into the database and generates a new workunit to continue processing the segment.
Results are exported twice a day in, and they are available for download as text or sql.
The search algorithm is not the most efficient, but gives reasonable results. A effort was initiated to install the subproject over at Ice00's server server.
25 Jul 2019, 8:37:19 UTC · Discuss
Testing Padls Total
Experiment with name Padls Total now entered testing phase.
A new application was developed for this project which is currently available as a beta for Linux. This application finally supports checkpoints. Please, decide if you really want to participate in the beta work. The work generator is also being tested, so there are many tasks available and if you have beta work enabled, you may get way too much.
If you enable beta applications, be prepared to have:
* tasks suddenly aborted by server
* your completed tasks not validated for weeks
* no credit assigned for weeks
* tasks crash or get stuck running
* no apps for our favorite platform
* strict deadlines
* wrong run-time estimate
This is batch 15, 21 and 22 on the server_status page.
Another remark: it is not necessary to run the beta work continuously. Run it for a while and then disable it. Leave some to me to test. Credit allocation, windows application, automated result publication and deadline adjustments will all be done before the application leaves beta mode.
The server might not be available all the time as I am trying different storage solution.
Programming talk and development updates are in this thread.
18 Jun 2019, 21:01:09 UTC · Discuss
©2019 Tomáš Brada