New post
0

Updating Minor Body Orbit Data Corrupts Observing Lists (Answer: Needs Path To Reproduction, For Now Try Restart SkySafari So All The Lists Are Always Revalidated)

If I add one or more asteroids to an observing list, and then Update Minor Body Orbit Data (in Settings->Solar System), all the asteroids in the list change to different asteroids.

Example:

I created an observing list and added asteroid (424) Gratia to the list.

Then, I updated minor body orbit data.

Then, I looked at the observing list and it contains only the asteroid (460) Scania.

So, the asteroid I added to the list has changed into a different asteroid.

5 comments

  • 0
    Avatar
    Dean

    I have just experienced this myself, except with comets.

    I had just created a new observing list containing three comets, and selected the "Highlight Objects" option so that I could see all of them while in Orbit mode.

    I then chose to update the Minor Body Orbit Data. After the update was complete, two of the three comets had changed to different ones. I then had to delete the incorrect comets and re-select and add the correct ones again.

     

    It would appear that you need to look into this issue.

     

    SkySafari Pro 6.3.1, Mac OS 10.14.4

  • 0
    Avatar
    Bill Tschumy

    We will look into this ASAP.  Thanks for reporting it.

  • 0
    Avatar
    Bill Tschumy

    I think I know what is happening.  If you quit the app and restart, does the list now show the correct comet or asteroid?  If so then I suspect we aren't properly revalidating the objects in the list after a minor body update.  If you restart the apps all the lists are always revalidated.

  • 0
    Avatar
    Bill Tschumy

    Also, is it the case that Peter is using iOS and Dean is using Mac?  I'm pretty sure that iOS does revalidate after a minor body update but possibly not.

  • 0
    Avatar
    Dean

    Well, by my logic I would suspect that the OS makes no difference since both have reported the same issue.

    I just tried updating the Minor Body Orbit Data again, but the observing list content did not change this time. Perhaps one needs to wait until the Orbit Data is further out of date before it will trigger the problem. Or maybe it only happens with newly created observing lists. Or maybe you need to create a list with different objects in it than the first list.

    At any rate, with the possible issue of needing to wait until the orbit data ages enough, coupled with the permutations of the other possible elements, it could take days to nail down which element causes the issue. So I'm afraid the ball's in your court for now.

    If I see another occurrence I'll try restarting the application to see if that restores the list and report it here. (although I'd still consider it to be a bug.)

    I rarely use observing lists, but they come in handy if I want to highlight several objects at the same time.

Please sign in to leave a comment.