SETI orphans
Message boards :
Number crunching :
SETI orphans
Message board moderation
Previous · 1 . . . 7 · 8 · 9 · 10 · 11 · 12 · 13 . . . 21 · Next
| Author | Message |
|---|---|
Dave Stegner  Send message Joined: 20 Oct 04 Posts: 540 Credit: 65,583,328 RAC: 62 
 |
Congratulations Mark. It has been a good run. You could come over to Rosetta and join us. Dave |
 betreger   Send message Joined: 29 Jun 99 Posts: 10274 Credit: 29,581,041 RAC: 149
|
Congrats Mark you got your billion, with a little help, now show us a picture of your toaster. |
kittyman  Send message Joined: 9 Jul 00 Posts: 50494 Credit: 1,018,363,574 RAC: 2,276
 |
Well, I'm out. Barring any rare resends at this point. It's been a good twenty years. Be looking forward to any news after the final processing of all that we have done. Meow meow meow! "Learn from yesterday. Live for today. Hope for tomorrow." Albert Einstein "With cats." kittyman 
|
|
Tom M Send message Joined: 28 Nov 02 Posts: 4936 Credit: 276,046,078 RAC: 1,048 |
Please correct me if I'm wrong in Rosetta operation understanding. If you move the allowed task computation time while the cache has tasks you can end up with a lot of "runs longer than it should" tasks. My understanding is the "Watch Dog" timer will kick if the task runs more than 4 hours past the "current" allowed task computation. So if you shorten up your allowed task computation time you will probably get more watch dog cancels till the cache is full of the "new" allowed processing time. I think if you go from small the larger it doesn't cause as much trouble. I think. Tom M "I owe", "I owe", "Its off to work I go" (from a bumper sticker on a smallish Mercedes Benz) (on the back of a Semi Tractor) "If you can read this bumper sticker, I've LOST MY TRAILER!" |
|
Grant (SSSF) Send message Joined: 19 Aug 99 Posts: 12990 Credit: 208,696,464 RAC: 690 
|
Please correct me if I'm wrong in Rosetta operation understanding.And with generally 4 day deadlines (although apparently some Tasks do have longer deadlines), which is why a very small cache is best, i've found 1 & 0.02 work pretty well for Rosetta only. For those with multiple projects, a smaller cache would be even better. Even though the Runtimes are fixed, the Estimated completion time for new types of Tasks can be way more, or way less, than the actual processing time. So often people with larger caches get more work than they can handle when a new type of Task (or a new Application with no APR history) is released. Grant Darwin NT |
Keith T.  Send message Joined: 23 Aug 99 Posts: 919 Credit: 537,293 RAC: 20 
|
Please correct me if I'm wrong in Rosetta operation understanding. Yes, You can adjust"Target Runtime" here https://boinc.bakerlab.org/rosetta/prefs.php?subset=project The default is 8 hours, you can select anything from 2 to 36 hours. There is a fair amount of discussion on some old Rosetta threads if you search. I used contribute to the RALPH project https://ralph.bakerlab.org/ as well as Rosetta. RALPH is Rosetta Alpha. RALPH message boards also have more discussion about the fine tuning of Rosetta. |
|
Dave Stegner Send message Joined: 20 Oct 04 Posts: 540 Credit: 65,583,328 RAC: 62
|
All users are welcome. Come help us "Seti Orhpans" fight Covad19 at Rosetta Stay safe . Dave |
Link  Send message Joined: 18 Sep 03 Posts: 833 Credit: 1,807,369 RAC: 1 
|
It sends data to compute as many possible protein configurations/docking configurations as length of CPU run allows. Yes, the downloaded files will be used for more work. This is good to decrease the load on the servers, even I can't recall issues over there like we know from SETI. Also you are not loosing so much time for starting the tasks. OTOH if a task errors out later, more work is lost. Must see how stable your computers are running Rosetta, that's different for every computer and nobody really knows why. If time is short, some another user gets same data to continue modeling. Well, many users will get same data anyway, they generate (hundreds of?) thousands of models from the same data. And if deadline miss occurs user can shorten allowable task computation time to avoid deadline miss (but project will need to resend data somewhere else to get full results). The user can even decrease the runtime after the WU has started if he might miss the deadline (or increase if he wants to, for example when server out of WUs, did that once myself and doubled my cache that way), just change it on the website, force scheduler request and restart BOINC, the task will start with new target CPU runtime or if you don't restart BOINC, all following tasks will start with it. It is however not so critical if you miss the deadline a bit, a new task will be send out, but your accepted and validated, IIRC even if you return it after the other host. The starting points are generated randomly on the host before the actual crunching, so both results will be different and useful for the project, you just need to return the result before it's purged from the database. That's also the reason, why Rosetta uses a quorum of 1, no two results are the same anyway. 
|
Raistmer  Send message Joined: 16 Jun 01 Posts: 6242 Credit: 106,370,077 RAC: 275 
|
Please correct me if I'm wrong in Rosetta operation understanding. It sends data to compute as many possible protein configurations/docking configurations as length of CPU run allows. Default is 8h. And user can change it. So, if user allows more hours to run, already downloaded database and particular protein data will be used more fully. If time is short, some another user gets same data to continue modeling. Hence, if deadline allows better to use longer run times. And if deadline miss occurs user can shorten allowable task computation time to avoid deadline miss (but project will need to resend data somewhere else to get full results). Is it correct? SETI apps news We're not gonna fight them. We're gonna transcend them. |
|
Raistmer Send message Joined: 16 Jun 01 Posts: 6242 Credit: 106,370,077 RAC: 275
|
Created team forum. Suggestions welcome. Joined, but will ask no work for now from WCG. SETI apps news We're not gonna fight them. We're gonna transcend them. |
Sirius B  Send message Joined: 26 Dec 00 Posts: 21809 Credit: 3,081,182 RAC: 15 
|
Created team forum. Suggestions welcome. |
|
Sirius B Send message Joined: 26 Dec 00 Posts: 21809 Credit: 3,081,182 RAC: 15
|
Their Open Pandemics project will be CPU to start with as they want the project up & running & from the 2 threads on that, it seems they are considering GPU once that is done.I would like to attach to some project that study SARS-CoV-2 on GPU. |
|
Raistmer Send message Joined: 16 Jun 01 Posts: 6242 Credit: 106,370,077 RAC: 275
|
Had some experience with F@h on early days o days of GPU computing, with ATi HD4870 card. They favor ATi hardware AFAIK. Unfortunately, my ATi discrete GPU burned (with real smoke!) just before SETI hibernations (~month before). SETI apps news We're not gonna fight them. We're gonna transcend them. |
Ian&Steve C.  Send message Joined: 28 Sep 99 Posts: 3150 Credit: 1,282,604,591 RAC: 15,062
|
GPUGRID does supporting research for many diseases including COVID-19, but it’s not directly for just that. They might have some more focused COVID-19 work in the future. I think the only project doing direct COVID-19 study on GPUs is Folding@home, but that’s not on BOINC. Seti@Home classic workunits: 29,492 CPU time: 134,419 hours  
|
Freewill  Send message Joined: 19 May 99 Posts: 456 Credit: 354,398,348 RAC: 26,522
|
I would like to attach to some project that study SARS-CoV-2 on GPU. Yes, I have signed up to be notified as well. Looking forward to working on it. 
|
|
Raistmer Send message Joined: 16 Jun 01 Posts: 6242 Credit: 106,370,077 RAC: 275
|
I would like to attach to some project that study SARS-CoV-2 on GPU. Sure. It seems WCG in process of making project for that, but will it CPU only or not - time will tell. Signed up for news for now. SETI apps news We're not gonna fight them. We're gonna transcend them. |
juan BFP  Send message Joined: 16 Mar 07 Posts: 9764 Credit: 572,710,851 RAC: 8,616 
|
I would like to attach to some project that study SARS-CoV-2 on GPU. If you find one please share with us. 
|
|
Raistmer Send message Joined: 16 Jun 01 Posts: 6242 Credit: 106,370,077 RAC: 275
|
I attach devices to diffferent projects in particular priority list. For now it's SARS-cov-2 study with Rosetta leading. But Rosetta can't do GPU. So, I would like to attach to some project that study SARS-CoV-2 on GPU. And E@h comes as backup everywhere. SETI apps news We're not gonna fight them. We're gonna transcend them. |
|
Grant (SSSF) Send message Joined: 19 Aug 99 Posts: 12990 Credit: 208,696,464 RAC: 690
|
Thus they can't be taking 1GB of memory at present.Most of the present Tasks need between 300-600MB RAM. Way down on the 1.3GB i have seen previously. Grant Darwin NT |
Ulrich Metzner  Send message Joined: 3 Jul 02 Posts: 1253 Credit: 13,565,513 RAC: 31
|
|
©2020 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.