SETI orphans
Message boards :
Number crunching :
SETI orphans
Message board moderation
Previous · 1 . . . 6 · 7 · 8 · 9 · 10 · 11 · 12 . . . 43 · Next
| Author | Message |
|---|---|
Sirius B   Send message Joined: 26 Dec 00 Posts: 24881 Credit: 3,081,182 RAC: 7 
|
Did that which is why country now blank. :-) |
|
Sirius B Send message Joined: 26 Dec 00 Posts: 24881 Credit: 3,081,182 RAC: 7
|
Created a new thread on the suggestions/feedback board asking if it is possible to add "International" to the list of countries. |
 Tom M Send message Joined: 28 Nov 02 Posts: 5124 Credit: 276,046,078 RAC: 462  |
There is a "Seti Orphans" team available on World Community Grid. It appears to have 2 members right now. Just created one for PrimeGrid. Can't find a private Team Message Area on World Community Grid. Suggested they add that feature in the Website support forum. Tom A proud member of the OFA (Old Farts Association). |
|
Sirius B Send message Joined: 26 Dec 00 Posts: 24881 Credit: 3,081,182 RAC: 7
|
Had that happen in the past. See this thread |
|
Sirius B Send message Joined: 26 Dec 00 Posts: 24881 Credit: 3,081,182 RAC: 7
|
When it happened to me, I searched the site & came across that thread. Left them running & they all completed on time. Ran many a project (ones that interested me). That's computing. :-) For example, BoincStats has me at 19.7M, yet Boinc combined stats has me at 20.4M. Boinc combined is correct. BoincStats never picked up the .7M from Reisel Sieve. Over the years had many glitches with Boinc from drives going kaput. It happens. |
Alien Seeker  Send message Joined: 23 May 99 Posts: 57 Credit: 511,652 RAC: 32 
|
The more I see of other projects, the more I appreciate how well SETI actually works (worked) I was just thinking the same. QuChemPedIA@home tasks can't be paused by BOINC, which makes them always run at 100% CPU power (I'll have to try a script to kill -STOP/kill -CONT them and see whether it works), (some) Universe@Home tasks auto-abort with "exceeded disk limit", LHC@home non-VirtualBox tasks incorrectly advertise a partial CPU count, causing more of them to run than the actual number of CPU, Cosmology@Home non-VirtualBox tasks use vsyscall, which is disabled by default in recent Linux kernels (admittedly, so does SETI@home stock app, but the code is available and the Debian package works fine)... What a mess. There are workarounds around some of these problems, and QuChemPedIA is a young project, but still. Gazing at the skies, hoping for contact... Unlikely, but it would be such a fantastic opportunity to learn. My alternative profile |
|
Tom M Send message Joined: 28 Nov 02 Posts: 5124 Credit: 276,046,078 RAC: 462 |
The more I see of other projects, the more I appreciate how well SETI actually works (worked) I have experimented with running Boinc with VM software. And am now crunching Cosmology@Home with 4 virtual machines on my Windows box. It was a turnkey startup. I don't know how often Cosmology@H checkpoints. But apparently Rosetta@Home is more reliable on restarts if the "leave non-gpu tasks in memory" box is checked. I rarely have restarts on WCG so I am not clear about if/how it check points. Except for the Africa Rainfall project it's tasks run from less than an hour up to around 4-5 hours. Tom M A proud member of the OFA (Old Farts Association). |
Raistmer  Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 
 |
Just wanted to say, now when we involved in few different projects with their own oddities we will appreciate the way SETI worked much-much more! :) But... it's said few times already, LoL :D Rosetta just killed 2 tasks I attempted to run for it on smartphone. It seems partially-involved hosts are no-no for this project - work will miss deadlines, work will be aborted in the middle... SETI, oh, dear SETI, how I miss you :)... SETI apps news We're not gonna fight them. We're gonna transcend them. |
|
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14654 Credit: 200,643,578 RAC: 874 
|
Still no checkpointing, and after running for almost 3 hours now, it's at 30% finished. Such a speed demon has seldom been seen in this Universe :-)If it's not checkpointing, it may not be reporting progress accurately, either. If BOINC isn't told a "fraction done" periodically, it makes one up, with unreliable consequences. People who run GPUGrid can see this very clearly at the moment. Their app both checkpoints and reports accurate progress every 10% of the way. Tasks stay at 0% for the first 60 seconds: then make it up as they go along to 10%, and report accurately after that. |
Link  Send message Joined: 18 Sep 03 Posts: 834 Credit: 1,807,369 RAC: 0 
|
As far as I can tell, at least with "leave appilcations in memory while suspended" disabled, BOINC will not switch to another application before the currently running one has checkpointed, it will always switch directly after a checkpoint (if it thinks it's necessary to do it). 
|
alanb1951    Send message Joined: 25 May 99 Posts: 10 Credit: 6,904,127 RAC: 34
|
A few bits of extra information for those who sign up for WCG... If you've got a machine with limited memory stick to Smash Childhood Cancer and Mapping Cancer Markers - both have relatively small memory footprints and are quite cache-friendly. (And steer clear of MIP1 - see below - as it thrashes memory...) Grumpy Swede please note! If you've got enough memory to consider running larger tasks, be aware that some projects (especially Microbiome Immunity Project, which uses Rosetta code) are very hard on memory, even if they don't necessarily seem to have huge footprints. It is probably a bad idea to try running more than one MIP1 task per 4 or 5MB of Level 3 cache (and there are threads about MIP performance on the WCG forums where you can check on this!)... If you want to run WCG "Fight Aids @ Home" be aware that the deadline is 24 hours(!) so it's probably a good idea to restrict the number of FAH2 tasks that WCG sends - there's a useful facility to say the maximum number of tasks of a given type you want on your machine at any given time (and it does seem to respect that pretty well...). If you are a Linux user with a very recent kernel, you might find that SCC throws SIGSEGV because it uses vsyscall - WCG are supposed to be doing a re-compile of the program to use a newer version of the standard library that should eliminate the issue on those machines that can't re-enable vsyscall (or don't want to!) If you decide to run the Africa Rainfall Project, be aware that it only checkpoints 8 times during a run (simulating 2 days, and checkpointing every 6 model hours) - most reasonably new machines will probably take 10+ hours to run one of these, and older machines (and those with small caches) may take a lot longer. There's a COVID-19 application in Alpha test at WCG at the time of writing this; it is apparently using one of the reasonably memory-efficient applications but it remains to be seen what its actual memory footprint might be. It will probably end up in the "o.k. for any machine" category... By the way, tuning a system to get a decent balance of work is quite an exercise at a lot of projects (WCG is not exceptional in this!); I doubt I'm unique in having put quite a lot of effort into trying to get a balance I'm [mostly] happy with (and it gets re-evaluated every time a new project appears...) The best strategy will depend on the hardware in use, of course (see above about MIP1 and cache, for instance,) Good luck to all those who do go to WCG, and happy crunching wherever you land! Cheers - Al. |
Siran d'Vel'nahr  Send message Joined: 23 May 99 Posts: 7379 Credit: 44,181,323 RAC: 238 
|
Just wanted to say, now when we involved in few different projects with their own oddities we will appreciate the way SETI worked much-much more! :) Hi Raistmer, The tasks at Rosetta are only given a 4 day deadline. On my 8th Gen Intel PC my tasks were running high priority constantly. Also, the v4.12 i686 Linux app has an issue where it won't set checkpoints. Just an FYI. :) Have a great day! :) Siran CAPT Siran d'Vel'nahr - L L & P _\\// Winders 11 OS? "What a piece of junk!" - L. Skywalker "Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath |
|
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121
|
Just wanted to say, now when we involved in few different projects with their own oddities we will appreciate the way SETI worked much-much more! :) Yep, looks like it's hard to find useful application for partionally-involved no-so-fast host besides of SETI. My netbook managed to miss Einstein's GW app deadline... What a hurry with GW discovery to restrict deadlines??I could understand hurry for new cure development, butto discover pattern in the data recorded months ago.... :/ SETI apps news We're not gonna fight them. We're gonna transcend them. |
Unixchick  Send message Joined: 5 Mar 12 Posts: 815 Credit: 2,361,516 RAC: 22
|
did we overload Rosetta, or does it have a regular maintenance on Saturday's?? edit: nevermind, it looks up again. |
|
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121
|
Added Einstein and Rosetta on Linux host with NV GPU recently. Strange thing - Einstein runs GW app, sinle task ( CPU has 4 corers), few Rosetta tasks in "ready to start"state but not running. Is GW app multi-CPU one?? And can E@h use NV GPU under Linux? 1050Ti ran CUDA special before, now idle.... Or should I find third project or chage OS on that host?... BTW, happy Cosmonautics day to all!!!! 12 April here already!! SETI apps news We're not gonna fight them. We're gonna transcend them. |
|
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121
|
Got answer on it already - no, not multithreaded. Rosetta tasks now crunching too (3 of them), but almost hour passed.... Why did they wait so long (in ready to start !) ?? Some issue in BOINC scheduling it seems %) SETI apps news We're not gonna fight them. We're gonna transcend them. |
|
Grant (SSSF) Send message Joined: 19 Aug 99 Posts: 13755 Credit: 208,696,464 RAC: 304 
|
Rosetta tasks now crunching too (3 of them), but almost hour passed....The default runtime is 8 hours. Why did they wait so long (in ready to start !) ??Memory or HDD space limitations? Current Tasks don't use much, 250-500MB RAM, 610MB HDD space) but there are plenty of Tasks that will need 1.3GB RAM, 1GB HDD space. Grant Darwin NT |
Ian&Steve C.  Send message Joined: 28 Sep 99 Posts: 4267 Credit: 1,282,604,591 RAC: 6,640
|
if you're talking about the GW nvidia GPU app, yes it can use more than 1 core, that app requires a lot of CPU support to feed the GPU. I noticed this on a few systems. it tries to pull >100% of a thread, making it spill over into a second thread. will happen more on a slow CPU. Seti@Home classic workunits: 29,492 CPU time: 134,419 hours  
|
Wiggo  Send message Joined: 24 Jan 00 Posts: 34975 Credit: 261,360,520 RAC: 489
|
Funny that I've always had to use an app_config.xml with Rosetta or it would rob cores needed for GPU work by Einstein (and I needed the heat off those GPU's during cooler times of the year, like now). <app_config> <project_max_concurrent>N</project_max_concurrent> </app_config> N=2 in my case with rigs that have 4 core CPU's with dual Nvidia GPU's. Cheers. |
|
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121
|
Rosetta tasks now crunching too (3 of them), but almost hour passed....The default runtime is 8 hours. AFAIK if task can't run it will say that in its status. Waiting for memory or smth alike... SETI apps news We're not gonna fight them. We're gonna transcend them. |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.