|
1)
Message boards :
Number crunching :
the Number of points
(Message 26504)
Posted 19 May 2014 by tom310 Post: Hi Eric, the ~300 points for 55ks is what you are usually pay, so I am fine. ;) |
|
2)
Message boards :
Number crunching :
the Number of points
(Message 26499)
Posted 19 May 2014 by tom310 Post: I got 54,279.75s 323.57 46,627.69s 604.88 46,611.45s 1,126.51 SixTrack v451.07 (pni) As far I known, the point system awards something else (results?) more then CPU time. Although this example is a little bit extreme. Never had significantly more than 500 points for a WU, so at least the last one came as a surprise. But I stopped to care, as it comes with the project. If you want to run for points, there are projects paying ten times more. |
|
3)
Message boards :
Number crunching :
Invalid tasks
(Message 26473)
Posted 17 May 2014 by tom310 Post: Hi, I have a wingman with 888 WU´s http://lhcathomeclassic.cern.ch/sixtrack/show_host_detail.php?hostid=10137504 All of them are done within a second while my machine works since 15 hours on two of them. As of now there are ~490 validation pending and ~400 validation inconclusive. None is validated. I think this machine does not like SixTrack v451.07 (sse2) at all. Or something else. |
|
4)
Message boards :
Number crunching :
Invalid tasks
(Message 26275)
Posted 12 Mar 2014 by tom310 Post: Eric, honestly, you need some coaching in regard to vacation. http://www.worthamphotography.com/beachchairsunset.html See you later ;) |
|
5)
Message boards :
Number crunching :
Invalid tasks
(Message 26259)
Posted 10 Mar 2014 by tom310 Post: Hi Eric, hi Ray, I had one or two 10^5 WUs that were ruled out, but the error might have a 10 times higher probability with 10 times longer WUs. I also had a bunch of non-inconclusive tasks with a Win/Linux wingmanship. Is it possible to take some of the "partially inconclusive" tasks and rerun them with fewer and fewer turns (bisection method) to narrow down the error? It looks reproducible to me. Greetings Tom PS: At least we have vacation-like weather here. |
|
6)
Message boards :
Number crunching :
Invalid tasks
(Message 26240)
Posted 8 Mar 2014 by tom310 Post: Enjoy your vacation, you deserve it. The project has produced 2 billion credits since August 2012, 10 times more than in all the years before. Coincidently, I joined in August 2012. I should have some vacation too. :-) |
|
7)
Message boards :
Number crunching :
Retrospect: June, July, August 2013 WU?
(Message 26235)
Posted 7 Mar 2014 by tom310 Post: Happened to me too, http://lhcathomeclassic.cern.ch/sixtrack/forum_thread.php?id=3735#25517 I think it is related to this http://lhcathomeclassic.cern.ch/sixtrack/forum_thread.php?id=3729#25475 Every workunit that was not purged or validated at the time of the update, remains in the Limbo, forever or at least 50 years. |
|
8)
Message boards :
Number crunching :
Invalid tasks
(Message 26225)
Posted 28 Feb 2014 by tom310 Post: Hi Eric, here are two more http://lhcathomeclassic.cern.ch/sixtrack/workunit.php?wuid=13524328 http://lhcathomeclassic.cern.ch/sixtrack/workunit.php?wuid=13521217 Looks like there is a discrepancy between v466.03 and v466.05. Tom |
|
9)
Message boards :
Number crunching :
Invalid tasks
(Message 26224)
Posted 27 Feb 2014 by tom310 Post: Hi Eric, I got another one. Here two v446.03 kicked out the v446.05. http://lhcathomeclassic.cern.ch/sixtrack/workunit.php?wuid=13506238 Ha! I got 4 credits for that one as indemnification. Greetings Tom |
|
10)
Message boards :
Number crunching :
Invalid tasks
(Message 26219)
Posted 26 Feb 2014 by tom310 Post: Hi, I have two invalid tasks and one inconclusive, that probably turns out to be invalid. They were downloaded at the same time on two different computers, that are connected to the same modem. The tasks were returned at different times. Both computers have valid tasks before and after that as well as valid non-LHC tasks. invalid http://lhcathomeclassic.cern.ch/sixtrack/result.php?resultid=28733989 http://lhcathomeclassic.cern.ch/sixtrack/result.php?resultid=28733914 inconclusive http://lhcathomeclassic.cern.ch/sixtrack/result.php?resultid=28733987 Could this be a download error? Is there any validation of a file after it was downloaded? Tom Edit: I just realized that all three are calculated using v466.03, while the other computers used v466.05. But also I have some workunits that show no discrepancy between v466.03 and v466.05. |
|
11)
Message boards :
LHC@home Science :
GPU Computing
(Message 25641)
Posted 12 Jun 2013 by tom310 Post: This was already discussed elsewhere: http://lhcathomeclassic.cern.ch/sixtrack/forum_thread.php?id=3743 But I want to add just another two cents. Since I joined this project, there was an idle time of about 50% of time where no WU's were available. With GPUs running, this would be 70% or higher, so I see no benefit here. Most of the WU's were crunched within a few days, which sounds ok for me considering the size and pace of work of an organization like CERN (please Eric, do not take this personally). The tail of undone work lurking around for a longer time has two underlying reasons: computers storing huge numbers of WU's from different BOINC projects, always crunching data close to the corresponding deadline and computers downloading WU's and dropping out. I do not see why GPU users are more or less reliable than CPU users in both cases. Lately, the server announced more than once that the amount of returned data was putting the Sixtrack infrastructure to the limit (disk-space-wise), GPU computing would... [I think you can extrapolate this]. Furthermore, and this is discussed in the above mentioned thread, GPU development is still fast-moving and immature. Manufacturer support is patchy at best, and often poor. Having worked on Small Angle Neutron Scattering, I acknowledge the temptation to try new and more fancy things (I thought about writing toys) but I also see an incredible amount of effort to achieve only little result. Maybe there is a need for faster computing in the future, especially when the project wants to study space charge effects with a very very large number of particles, there will be a place for GPUs. But I think this requires standardized GPU capabilities, so you do not need a custom-made application for each available GPU/driver version. And if Sixtrack focuses on Keppler, I already hear the other GPUs cry foul. Having said all this, to me Sixtrack is an MVP (most valuable project) candidate in the BOINC family and I dedicate all I have (unfortunately only two old dual cores) to this project, although the pay, compared to other projects, is lousy (I must be a true scientist). |
|
12)
Message boards :
News :
More work coming now.
(Message 25558)
Posted 10 May 2013 by tom310 Post: I think the one or two you got are leftovers from last week (May 4th) which were returned as inconclusive or timed out. I think Eric removed 26k WUs over night as they were not working. The total credit for yesterday was 184k which does not fit with massive crunching. The remaining 29k WUs can not be downloaded for some unknown reason. |
|
13)
Message boards :
Number crunching :
new WUs? not for me. why?
(Message 25552)
Posted 9 May 2013 by tom310 Post: See here http://lhcathomeclassic.cern.ch/sixtrack/forum_thread.php?id=3737#25545 |
|
14)
Message boards :
News :
More work coming now.
(Message 25544)
Posted 8 May 2013 by tom310 Post: Hi Eric, nobody seems to get work as Tasks ready to send remains unchanged and the Tasks in progress are dropping slightly. My BOINC Event log usually it says: 4/30/2013 7:38:19 AM | LHC@home 1.0 | Sending scheduler request: To fetch work. This time: 5/8/2013 3:28:54 PM | LHC@home 1.0 | Requesting new tasks for CPU Something for you to crunch. ;-) Tom |
|
15)
Message boards :
Number crunching :
Can't find workunit
(Message 25517)
Posted 12 Apr 2013 by tom310 Post: Hi LHC/Sixtrack people, I have two workunits that are lost in space. Result ID 14684812 Result ID 14684815 The corresponding workunit can not be found. My wingman failed to report a result within the deadline and then the workunits disappeared. Is this somehow important for you? I just wonder what happened. tom |
©2024 CERN