A thought about Nebula and BOINC
Message boards :
Number crunching :
A thought about Nebula and BOINC
Message board moderation
| Author | Message |
|---|---|
|
Ben Send message Joined: 15 Jun 99 Posts: 54 Credit: 60,003,756 RAC: 150 
|
The reason stated, in the Nebula section of this website, that the back end processing is not suitable for BOINC is that it is very data intensive. It seems to me that one part could be done with distributed computing though. If work units were sent out with all the beam data rather than just one beam, an app could remove multibeam RFI. Perhaps as a separate app and using the results sent in by the main app. It would add more data load to the servers but only for the, hopefully, small fraction of work units that come back with "interesting" results. ID: 1979942 ·  |
|
Filipe Send message Joined: 12 Aug 00 Posts: 218 Credit: 21,281,677 RAC: 20 
|
If work units were sent out with all the beam data rather than just one beam, an app could remove multibeam RFI. For what i have read before, this will be implemented in SETI@home version 10 ID: 1979950 · |
|
Ben Send message Joined: 15 Jun 99 Posts: 54 Credit: 60,003,756 RAC: 150
|
If work units were sent out with all the beam data rather than just one beam, an app could remove multibeam RFI. Is there a time line for that or is it just whenever volunteers step up to do it? ID: 1979953 · |
|
Filipe Send message Joined: 12 Aug 00 Posts: 218 Credit: 21,281,677 RAC: 20
|
Only when the Seti@home team have the budget to develop the code. ID: 1980312 · |
©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.