chris wrote:[That's not a bug, actually . . . The / character is used for 'paths' For instance, to select the Moon you could enter Sol/Earth/Moon (though just 'Moon' will work within the Solar System) So / is not permitted in object names.
Hmmm. Then I guess I should rephrase that as an enhancement request
![Smile :)](./images/smilies/icon_smile.gif)
It'd be nice if somehow a / could be used in an object name, since the prefix C/ is often used when designating comets in the professional databases, and Pascal followed that convention in comets.ssc. Maybe with a quoting character as a prefix?
chris wrote:Celestia uses double precision numbers for orbital elements, which means it will recognize up to 16 significant digits. I doubt that any orbit has actually been determined to such precision, however.
I've been careful to use the term "precision" and not "accuracy" when describing the differences. Highly precise values (with lots of digits) are not necessarily accurate (i.e. not necessarily correct). I was glad to find that Celestia has no problems with the exponential format that Horizons generates. That saves a lot of work! Somehow I had gotten the impression that the input routines didn't like lots of digits. Maybe the limitation is with numbers expressed as nnn.nnn without the exponent at the end? *shrug*