Diigg,
There may be errors in the Locator database; that I can not say.
But are there any errors in the orbital data of 67P? To have.
I was able to correct the path error for ISEE-1 and ISEE-2.
In each file, I deleted 2 lines
for ISEE-1: 1983 93rd day h3.00 and 1983 95th day h12.63333
for ISEE-2: 1981 20th day h2.81667 and 1981 22nd day h12.41667
The unwanted loop has disappeared
Added after 1 hour 4 minutes:For Rosetta, I have 2 ssc files.
- ssc ArtBlos with a timeline at 3 epochs:
"Churyumov-Gerasimenko: 67P: 67P-Churyumov-Gerasimenko: 1975 P1" "Soil"
1st ending 2014 Aug 06 with EllipticalOrbit
2nd ending 2016 Oct 01 with xyzv file
3rd beginning 2016 Oct 01 (endless) with EllipticalOrbit
- ssc (from unknown source) with SpiceOrbit
"67p: 67P_Churyumov_Gerasimenko" "Sol"
Beginning "1900 01 01 00: 00: 00.000"
Ending "2101 01 01 00: 00: 00.000"
This file with Spice does not work because I must miss files.
EllipticalOrbit descriptions are generalist. They describe an orbit at a given moment and apply it to the entire timeline of which they are part. This induces errors in relation to reality.
To match Rosetta and 67P at the time of their meeting, it would take a xyz file for everyone at the same time.
Would someone have the model for the Philae lander?
Added after 2 hours 32 minutes:a position file for 67P (xyzv)
beginning 11 sept 1969 (date of discovery)
ending 11 dec 2018
gap between each line: 1 day
Source: HORIZONS
center: Sun
units: km
It does not add too much precision to the design of the orbit, but refines the position of the comet which has a period of revolution that oscillates around 6.50 years.
put .ssc in your folder for 67P (apart from LUT5, 'Visible false' and 'Clickable true', can be disabled)
put .xyzv in your data for 67P
disable your old files .ssc and .xyzv
Added after 59 minutes 4 seconds:DaveBowman2001,
indeed, there are transparencies but I did not find what produced them. The surfaces are described as opaque.
????