LHC@home

We have started the integration of ATLAS into LHC@Home and we are sending a few test WU just to see if they work ok. These WU are exactly the same as the multicore WU on ATLAS@Home but we are not using the results. The ATLAS app is currently a beta app so you need to enable running beta apps in the project preferences if you want to try ATLAS WU. We welcome volunteers (especially seasoned ATLAS@Home crunchers!) to try out the test tasks.

Ok, I will see if I could run some tasks. Do you need a feedback? Only negative ones?

Validate error: https://lhcathome.cern.ch/lhcathome/workunit.php?wuid=53646494

Hi
Same as Luigi, Validate error.
I ran on a Win10, with Boinc 7.6.33 and VB 5.1.12
Let us know when there are more ATLAS to test :-)

I made a small mistake in one of the parameters of the WU, but I fixed that this morning and the new WU are failing with a different problem. I am investigating...

After fixing some backend infrastructure issues, we now have the first successful WU! We will keep a small trickle of test WU in the system so let us know of any problems you see.

One task calculated now. All works fine :)

Will the Atlas-WUs here take into account the settings regarding NumberOfWUs and NumberOfCores from the Website or do we have to setup an app_config ?

---

Supporting BOINC, a great concept !

I tried to get some of these tasks but I see the server says 0 tasks to send and 12 in progress........of course I tried to get some first with no luck.

---

Volunteer Mad Scientist For Life

These WU are exactly the same as the multicore WU on ATLAS@Home

I was lucky and got my first WU here.

If they are really the same as on Original-project, the rutime is to small. Please check this result: https://lhcathome.cern.ch/lhcathome/result.php?resultid=112410796

CPU-time as 4-Core-WU at Original-Atlas is for this machine something with 4 hours, here it is only something with 33 minutes, but the WU got validated.

---

Supporting BOINC, a great concept !

These WU are exactly the same as the multicore WU on ATLAS@Home

I was lucky and got my first WU here.

If they are really the same as on Original-project, the rutime is to small. Please check this result: https://lhcathome.cern.ch/lhcathome/result.php?resultid=112410796

CPU-time as 4-Core-WU at Original-Atlas is for this machine something with 4 hours, here it is only something with 33 minutes, but the WU got validated.

Sorry, I forgot to mention that these WU process 5 events instead of the normal 50 events used in the original project. This is to give a quick turnaround of tasks so problems can be seen quickly. So a short CPU time is expected.

Will the Atlas-WUs here take into account the settings regarding NumberOfWUs and NumberOfCores from the Website or do we have to setup an app_config ?

They should do as they act upon the scheduling in the server rather than the client. I am just testing now for myself but there are no tasks.

Edit: It doesn't work at the moment but we should be able to get it working.

Last 3 tasks ended into an error

First showing the Login prompt and after a short time: "Can't connect to default. Skipping." ... and the VM shuts down.



https://lhcathome.cern.ch/lhcathome/result.php?resultid=112535871
https://lhcathome.cern.ch/lhcathome/result.php?resultid=112535831
https://lhcathome.cern.ch/lhcathome/result.php?resultid=112535833

Last 3 tasks ended into an error

No panic, it's working now.
The line <enable_shared_directory/> was missing.

btw: It would be nice to have at least Alt-F3 (top) enabled.

Results of one single core VM and a dual_core VM:

https://lhcathome.cern.ch/lhcathome/result.php?resultid=112535885 --> Run time 55 min 5 sec - CPU time 49 min 52 sec
https://lhcathome.cern.ch/lhcathome/result.php?resultid=112552204 --> Run time 36 min 22 sec - CPU time 56 min 22 sec

It seems credit is assigned to elapsed time and not to used cpu-time.

I have had 20 total, there is 4 waiting to run. The 1st one on the 16th had validate error, the rest are good it seems.

They are all mcore on my PC.

I have all mine set to no limit which is 1core, I can check if goes up.

I crunched 8 wu's today, which all worked fine (except for one, but that was my fault playing around with the ram settings).

is it possible that there are multicore wu's which are using the allocated cores (2 cores + 2 HT = 4 in my case) and multicore wu's which are just using 1 core, regardless how much cores are allowed by the boinc manager? because i havent changed my settings according to allowed cores for boinc and some wu used 4 and some used just 1 (or is it because i played with the ram settings).

Boinc-Manager: 7.4.22
OS: Linux 4.8
Virtualbox. 5.1.14

ok, i crowed too soon. last two tasks failed with validate error:

https://lhcathome.cern.ch/lhcathome/result.php?resultid=112760511
https://lhcathome.cern.ch/lhcathome/result.php?resultid=112760579

unfortunately, the editing function in this forum only works until 60 mins after the post, so i had to make a new one...

Those two were from the first batch of bad WU which were still hanging around.

Thanks everyone for the testing! I've submitted some longer WU now, processing 50 events like in the regular ATLAS@home.

The #CPU settings are not working as expected, but Laurence is looking into it.

As for credit, see the discussion here which shows that running 1 core gives much more credit due to longer elapsed time. This seems to be a feature of the standard CreditNew algorithm that we are all using.

Scrub that comment about multicore, they were the actual atlas tasks.