Message boards :
Theory Application :
Sherpa - longest runtime with Success - native
Message board moderation
Author | Message |
---|---|
Send message Joined: 2 May 07 Posts: 2258 Credit: 174,476,740 RAC: 28,166 ![]() ![]() ![]() |
[boinc pp jets 13000 180,-,3560 - sherpa 2.2.5 default 19000 190] Laufzeit 1 Tage 10 Stunden 19 min. 59 sek. - CPU Zeit 1 Tage 10 Stunden 19 min. 22 sek. |
![]() Send message Joined: 12 Jun 18 Posts: 126 Credit: 53,906,164 RAC: 0 ![]() ![]() |
Ten days, you must be a very patient person :-) |
![]() Send message Joined: 7 Feb 14 Posts: 99 Credit: 5,180,005 RAC: 0 ![]() ![]() |
It would be nice to see runRivet.log. |
Send message Joined: 2 May 07 Posts: 2258 Credit: 174,476,740 RAC: 28,166 ![]() ![]() ![]() |
[boinc pp jets 7000 800 - sherpa 2.2.2 default 34000 190] Laufzeit 2 Tage 13 Stunden 49 min. 57 sek. - CPU Zeit 2 Tage 5 Stunden 53 min. 23 sek. |
Send message Joined: 13 Jul 05 Posts: 169 Credit: 15,000,737 RAC: 0 ![]() ![]() |
Task 253573409: [boinc pp jets 7000 150,-,2160 - sherpa 2.2.0 default 6000 186] Run time 4 days 3 hours 41 min 11 sec CPU time 4 days 3 hours 10 min 24 sec Though my record in recent times is instead a Sixtrack task (but on a slower machine): Name workspace1_HEL_Qp_2_MO_0_1t_3s_1e7turns__5__s__62.31_60.32__1_1.5__7__80_1_sixvf_boinc21890_1 Run time 7 days 13 hours 0 min 26 sec CPU time 7 days 12 hours 51 min 12 sec My point is that some of us are happy to run long-lived tasks but it would help to be able to separate them out for operational reasons; hence my suggestion in another thread that the Theory-Native subproject be set aside for Sherpa 2.x tasks which are the ones that commonly over-run and need manual inspection of the log files. |
Send message Joined: 2 May 07 Posts: 2258 Credit: 174,476,740 RAC: 28,166 ![]() ![]() ![]() |
My point is that some of us are happy to run long-lived tasks but it would help to be able to separate them out for operational reasons; hence my suggestion in another thread that the Theory-Native subproject be set aside for Sherpa 2.x tasks which are the ones that commonly over-run and need manual inspection of the log files. Yes Henry, the idea is to find those successful longrunner with Sherpa 2.2.x to help us from Cern-IT or the Sherpa-Team (P.Skands). |
Send message Joined: 2 May 07 Posts: 2258 Credit: 174,476,740 RAC: 28,166 ![]() ![]() ![]() |
[boinc ppbar ue 1800 10 - sherpa 2.2.5 default 81000 192] Laufzeit 20 Stunden 59 min. 2 sek. CPU Zeit 20 Stunden 51 min. 9 sek. |
![]() Send message Joined: 7 Feb 14 Posts: 99 Credit: 5,180,005 RAC: 0 ![]() ![]() |
Yes Henry, Just get your hostid list from active hosts page on mcplots-dev.cern.ch. Then scrape html pages from lhcathome.cern.ch looking for long tasks. If you find someone, you check if it is sherpa on stderr output. |
Send message Joined: 13 Jul 05 Posts: 169 Credit: 15,000,737 RAC: 0 ![]() ![]() |
Just get your hostid list from active hosts page on mcplots-dev.cern.ch. Then scrape html pages from lhcathome.cern.ch looking for long tasks.I'm not clear how that would work - how do you distinguish a long-running task from one that's still sitting on the host unstarted? If you find someone, you check if it is sherpa on stderr output.I still have to search for the host and slot to find the logs. It would be much easier to only run the Sherpas on the machine where I can tolerate run times of a week or more; then it's easy to see if any Sherpa is running and for how long with top and only if it's more than say 10 hours in do I need to start poking in the logs trying to decide if it will finish or want to keep running until the heat death of the universe. |
![]() Send message Joined: 7 Feb 14 Posts: 99 Credit: 5,180,005 RAC: 0 ![]() ![]() |
I'm not clear how that would work - how do you distinguish a long-running task from one that's still sitting on the host unstarted?We're looking for successful tasks, so I would use this page and parameters. https://lhcathome.cern.ch/lhcathome/results.php?hostid=HOSTID&offset=0&show_names=0&state=4&appid=13 Then you select tasks by elapsed or run time. If time > YOUR_TIME, you have a long task and go here https://lhcathome.cern.ch/lhcathome/result.php?resultid=LONG_TASK_RESULTIDto read stderr output that contains "sherpa or not" information. |
![]() Send message Joined: 7 Feb 14 Posts: 99 Credit: 5,180,005 RAC: 0 ![]() ![]() |
I still have to search for the host and slot to find the logs. Not if it'a a native theory task. You can do different operations if plan class is vbox or native. You would scan all the hosts, not only yours. ;) |
![]() Send message Joined: 7 Feb 14 Posts: 99 Credit: 5,180,005 RAC: 0 ![]() ![]() |
Successfully crunched one of those longer tasks, I guess. boinc pp jets 7000 150,-,2160 - sherpa 2.2.5 default 2000 192 Run time: 1d9h52m35s resultid=254968079 |
Send message Joined: 2 May 07 Posts: 2258 Credit: 174,476,740 RAC: 28,166 ![]() ![]() ![]() |
[boinc pp ttbar 7000 - - sherpa 2.1.1 default 3000 198] Laufzeit 5 Tage 16 Stunden 47 min. 50 sek. - CPU Zeit 4 Tage 22 Stunden 16 min. 10 sek. |
![]() Send message Joined: 7 Feb 14 Posts: 99 Credit: 5,180,005 RAC: 0 ![]() ![]() |
https://lhcathome.cern.ch/lhcathome/result.php?resultid=255648161 pp jets 7000 150,-,2160 - sherpa 2.2.4 default 3000 196runtime: 10d 13h 58m 30s cputime: 7d 23h 19m 56s |
©2025 CERN