Celestia Forums

Hello to all
i'd like to improve this script before i release it on the motherlode.
Beta testing and suggestions welcomed

http://asolignac.free.fr/celestia/NWSv1beta.celx

NB : the script will ask you for systemaccess() permission as it outputs results to an html file and a few jpg screenshots. Everything will be created under the celestia root folder. The script needs to be ended properly (escape key) for the html file to be read back.


For better fun, be sure to use these two files or similar ones :

Dirl's comets
http://www.celestiamotherlode.net/catalog/show_addon_details.php?addon_id=788
Arlene's asteroids
http://www.celestiamotherlode.net/catalog/show_addon_details.php?addon_id=646


A small disclaimer : although this script uses "real (outdated) data", it may NOT help you foretell the fate of our planet or species. It is intended to be a toy / demonstration / educational tool. Also, keep in mind that a top view deprives the observer from a 3 dimensional perception.

Enjoy!

oh and by the way, the script outputs the closest approach to Earth, compared to all previous ones recorded by the script.

So as the script goes, you will have to wait longer and longer to get a closer approach...

Ranges and timescales can be specified in the script.

You left out one detail:

What is this script supposed to do?

Fair enough...
i guess the night has been too long

so, the script will use the available asteroid / comet data to record the closest approach to Earth during the simulation, marking objects with small triangles if they enter a defined range, and bigger triangles if they enter a closer range.
Whenever an object comes closer to Earth than ANY before him, its name, distance, etc will be output to an html file, and a screenshhot will be taken.

The number of screenshots should not be more than a dozen if you run the script for a couple hours...

The idea was originally to see how the NEO impact risk would show up in a closed-loop simulation of the solar system.

Now, i know the simulation and the NEO data are very approximative. It is more a demonstrative tool, to figure out distance and time scales (frequency of approaches). It also shows how objects can make "redundant" approaches after decades.

cheers
amaury

One feature i realize would be necessary is a calibration test, to adjust the timescales on slow computers... otherwise the mainloop of the script may not run a sufficient number of times per second.

This is particularly true with big asteroids.ssc files...