The benevolent programmers are not mind readers. If enough people want some feature, the open source programmers who donate their time and effort to provide Stellarium, for free, will get around to it.Īs mentioned above, there is an appropriate public forum to discuss desired turn key features and issues with Stellarium. Stellarium's scripting features can do pretty much everything damanded of it here, but people do just want turn key features. Either way, the logs will show what happened and it will be fixed. Fixing the mount is very important there - it shouldn't dive off a cliff when it hears unintelligible jabber from some maniac! Not sending junk commands is also rather important to better handle mounts with suicidal tendencies. If Stellarium is sending a junk command, and causes the mount to not respond, that's an issue the logs will show. The only ways Stellarium, or any other ASCOM client disconnects a mount is if 1) the client asks for it or, 2) the mount no longer exists or responds. Guessing that it's Stellarium, without any basis for doing so, in an inappropriate public forum, doesn't help anything. Leave it to those who know what they're doing to fix the issue, wherever it may be. When it comes to software I'm strictly an end user. Give me something mechanical and I'll fix it. I've also shared the same with the mount manufacturer and switched to the recommended version. I'm not a programmer so that's about all the help I can provide. Logging is on and logs have been provided to Stellarium. I still haven't been able to split Sirius AB yet.Įdited by Nicole Sharp, 18 December 2022 - 03:15 AM. Sirius B is invisible on Stellarium.ĭo both Starry Nights and SkyTools show the correct position for Himalia? I also need to figure when the greatest elongations for Amalthea are but not sure how helpful that will be in splitting it from Jupiter (ditto for Deimos/Phobos with Mars). If someone can share a screenshot of Sirius B from their favorite planetarium application, that would be helpful. Hektor is the second-brightest minor planet in the Outer Solar System, after Pluto. Hektor Opposition was on December 9 but I haven't tried for that one yet. Accidentally observing a magnitude-15 spiral galaxy with a 5-inch Mak on an altazimuth mount was almost as exciting as finding Himalia but I need good charts to figure out what I'm looking at in the photos. This is with a 1540/127 (f/12) Maksutov-Cassegrain telescope on an altazimuth-tracking mount (the Orion StarSeeker 127 / Sky-Watcher Star Discovery 127). Regarding minimum aperture for Himalia, I had the wrong coordinates, but my photographs still showed galaxies down to magnitude 15 and stars down to magnitude 16, so I should have been able to see Himalia. The previous suggestion I received is to download the coordinates for Himalia directly from the Minor Planet Center, and then manually look up the coordinates for the date in question on Stellarium. SkyTrack, primarily for satellites, and costing a measly $9, also does that now. It's great to know that CdC is already querying JPL. Having an option to add any particular moon is not at all difficult for software when properly coded. There is no need to keep all of the data when, as you say, some of the moons are too faint to see with reasonable scopes. URA111 (162MB) goes out to about 2099 with an interpolation error of about 0.8m. SAT441 (631MB) goes out to about 2250 with an interpolation error of about 7.5m. One can calculate locally using that file, or just query JPL Horizons. JUP344 can be obtained here, and is only 298MB. There is no actual integration being done when one queries. When one uses JPL, the input time leads to the correct chunk, which gives the coefficients for the desired chunk. The data are chunked into about month long intervals, with Chebyshev polynomial coefficients. Himalia, and others, have been integrated out to about 2200 in JUP344. Properly coded software can "handle" them easily out to the limits of what's already been integrated. The notion that "software" cannot "handle" these orbits is just not true. And at magnitude 14.6, it is difficult to see in a smaller scope. I would not expect the orbit for Himalia to be correct, it is irregular and always changing.
0 Comments
Leave a Reply. |