LHC@home

This new version updates cranky to v0.29. It now prints the parameters from the rivet log early and also the timestamps are in local time. The work unit deadline has also been increased to 10 days.

It's still a beta app.
At -dev it was announced to become a non-beta app.
??

It's still a beta app.
At -dev it was announced to become a non-beta app.
??

Not until the credit issue is solved. This is still pending.

Not until the credit issue is solved. This is still pending.

Looks much better now.
Both tasks are from the same client.

Old
https://lhcathome.cern.ch/lhcathome/result.php?resultid=220670558
runtime: 8227.16
CPU-time: 4990.17
Credit: 8.15

New
https://lhcathome.cern.ch/lhcathome/result.php?resultid=222886697
runtime: 7283.42
CPU-time: 3936.66
Credit: 90.40

Looks much better now.

Unfortunately only the first one.
Other results still get low credits:

222968397 	111688357 	10575017 	7 May 2019, 11:09:57 UTC 	7 May 2019, 13:48:40 UTC 	Fertig und Bestätigt 	9,507.56 	5,512.14 	11.83 	Theory Native v1.01 (native_theory) x86_64-pc-linux-gnu

Unfortunately only the first one.

For me only the first two tasks. Beginners luck.
The third task get low credits again.

Completed and validated - Run time: 9,373.00 sec. - CPU time: 10,646.50 sec. - Credit 8.48

what surprises me: as per info from the Server Status page, Theory Native shows between 16 and 20 crunchers in the "users in past 24 hours" column.

Is this really so? Or are these figures wrong for any reason?

I couldn't image that it made sense to develop this native app for just such a small number of users.
Or am I missing something?

It could just be that users are continuing to use the standard VBox version, either because they don't know it's an available option for Linux or, like myself, CAN'T use it as my 3 hosts are all Windows.

what surprises me: as per info from the Server Status page, Theory Native shows between 16 and 20 crunchers in the "users in past 24 hours" column.I

I just assumed that they have tried it, gotten hung up with a long runner, and abandoned it. The remaining people are either willing to babysit their machine, or haven't run into the problem yet.
I am waiting for the numbers to pick up a bit before jumping in again.

Master file download succeeded
Server error: feeder not running
Tested with and without Test-Application-Preference and
reset of Project.

Mon 13 May 2019 02:29:21 AM MDT | LHC@home | Started upload of TheoryN_2279-800506-55_0_r1972795353_result
Mon 13 May 2019 02:29:24 AM MDT | LHC@home | Finished upload of TheoryN_2279-800506-55_0_r1972795353_result
Mon 13 May 2019 02:32:19 AM MDT | LHC@home | Sending scheduler request: To report completed tasks.
Mon 13 May 2019 02:32:19 AM MDT | LHC@home | Reporting 2 completed tasks
Mon 13 May 2019 02:32:19 AM MDT | LHC@home | Requesting new tasks for CPU
Mon 13 May 2019 02:34:21 AM MDT | | Project communication failed: attempting access to reference site
Mon 13 May 2019 02:34:21 AM MDT | LHC@home | Scheduler request failed: Timeout was reached
Mon 13 May 2019 02:34:23 AM MDT | | Internet access OK - project servers may be temporarily down.
Mon 13 May 2019 02:41:41 AM MDT | LHC@home | Sending scheduler request: To report completed tasks.
Mon 13 May 2019 02:41:41 AM MDT | LHC@home | Reporting 2 completed tasks
Mon 13 May 2019 02:41:41 AM MDT | LHC@home | Requesting new tasks for CPU
Mon 13 May 2019 02:41:43 AM MDT | LHC@home | Scheduler request completed: got 0 new tasks
Mon 13 May 2019 02:41:43 AM MDT | LHC@home | Server can't open database
Mon 13 May 2019 02:59:49 AM MDT | LHC@home | Computation for task Theory_3365477_1557644839.539115_0 finished
Mon 13 May 2019 03:41:48 AM MDT | LHC@home | Sending scheduler request: To report completed tasks.
Mon 13 May 2019 03:41:48 AM MDT | LHC@home | Reporting 3 completed tasks
Mon 13 May 2019 03:41:48 AM MDT | LHC@home | Requesting new tasks for CPU
Mon 13 May 2019 03:42:01 AM MDT | LHC@home | Scheduler request completed: got 0 new tasks
Mon 13 May 2019 03:42:01 AM MDT | LHC@home | Server error: feeder not running
Mon 13 May 2019 04:42:05 AM MDT | LHC@home | Sending scheduler request: To report completed tasks.
Mon 13 May 2019 04:42:05 AM MDT | LHC@home | Reporting 3 completed tasks
Mon 13 May 2019 04:42:05 AM MDT | LHC@home | Requesting new tasks for CPU
Mon 13 May 2019 04:42:17 AM MDT | LHC@home | Scheduler request completed: got 0 new tasks
Mon 13 May 2019 04:42:17 AM MDT | LHC@home | Server error: feeder not running

Server error: feeder not running

same problem here; and strange enough: the Server Status Page shows that the feeder is running.

what surprises me: as per info from the Server Status page, Theory Native shows between 16 and 20 crunchers in the "users in past 24 hours" column.I

I just assumed that they have tried it, gotten hung up with a long runner, and abandoned it. The remaining people are either willing to babysit their machine, or haven't run into the problem yet.

Native theory won't gain wider acceptance until it has a mechanism for graceful shutdown. My watchdog script circumvents the "run past deadline" and the "disk limit exceeded" problems but it does so by aborting the task. That's not user friendly to volunteers who expect credits. Hopefully the new native Theory allows graceful shutdown. Or maybe crunchers can add it by putting a <completion_trigger_file> line in one of the config files.

Native theory won't gain wider acceptance until it has a mechanism for graceful shutdown.

It may be one of the reasons, yes.


Another one is most likely the poor credit reward.
Let's see what Laurence's changes will bring.
I personally doubt that NTheory will find a stable "credit factor".
As far as I understand it this would require tasks with similar runtime/CPU-time.
What we have here are runtimes between a few minutes and lots of hours.

Hopefully the new native Theory allows graceful shutdown. Or maybe crunchers can add it by putting a <completion_trigger_file> line in one of the config files.

It's very tricky to implement a method that allows this (based on the current code). A completion_trigger_file or any other trigger would only make sense if you already have such a method.

This Pythia6 had a problem to finishing successful:
https://lhcathome.cern.ch/lhcathome/workunit.php?wuid=115417792
[boinc pp jets 8000 25 - pythia6 6.428 dwt 100000 60]

This Pythia6 had a problem to finishing successful:
https://lhcathome.cern.ch/lhcathome/workunit.php?wuid=115417792
[boinc pp jets 8000 25 - pythia6 6.428 dwt 100000 60]

From 62 attempts 43 ended successful.

Strange is, that cranky is running for 1 or 1.5 hours and then EXIT_CHILD_FAILED.

This task ended after 10 Minutes for three Volunteers::
https://lhcathome.cern.ch/lhcathome/workunit.php?wuid=115538576
boinc pp zinclusive 7000 -,-,50,130 - madgraph5amc 2.6.1.atlas default 100000 62]

This task have a problem after some hours of work:
https://lhcathome.cern.ch/lhcathome/workunit.php?wuid=115589537
[boinc pp jets 8000 25 - pythia8 8.212 tune-A14-CTEQL1 100000 62]

This task have also a problem to finish for three Volunteers:
https://lhcathome.cern.ch/lhcathome/workunit.php?wuid=115612872
[boinc pp jets 8000 25 - herwig++ 2.6.1a default 100000 62]