Originally posted by: Assimilator1
I would of given ya a Beer Andy for the heads up but you didn't tell us what the project is about
Thx anyway
Well I just went to their forum ,& it seems they don't even have a basic website describing what it's about! :Q
But would I be right in saying that it's for tracking NEOs? or is it for finding them?
Lmao
You're right!!
I suppose
this is about as close as it gets!
A quote from the news on the front page
"This funding will provide partial support for this project for the next three years, allowing us to acquire the required computer hardware and to get started with the software development, focusing on two Near Earth Asteroids (NEAs) research areas:
1) develop a search strategy for NEAs surveys that maximizes the volume covered in the space of the orbital elements of the NEAs;
2) demonstrate the applicability and advantages of using distributed computing to monitor the impact hazard posed by NEAs to the Earth."
And this quote from
this thread might help
"Let's start with this easy question. Orbit@home is a project based on BOINC and ORSA, monitoring the orbit of all the asteroids passing near the Earth. Every time a new asteroid is discovered or re-observed, the orbit of the asteroid is updated and propagated in future to check for possible impacts with the Earth.
As bigger and better telescopes are built, the number of orbits to update every day increases, so more computing power is needed in order to do it. It is at this point that the distributed computing philosophy enters and helps doing the work. The basic idea is the following: each different client can work with the data relative to a single asteroid, because there is no correlation between asteroids (excluding extremely rare cases, like asteroid-asteroid impact or gravitational perturbation; both these cases can be handled in an improved version of orbit@home). If the number of clients available is greater than the number of orbits to update (times a redundancy factor), it is possible in principle to update all the orbits in the same time needed by a single computer to update a single orbit. This is what makes the orbit@home project so appealing."
Any clearer?
and thanks for the beer :beer:
Facebook
Twitter