1

Observing Lists get corrupted

Dave Chapman

February 07, 2025 12:50

None

Follow

Has anyone else had this problem? Last fall I created a couple of observing lists of asteroids that I wanted to image. Recently I noticed that those lists were missing objects I had included, and also had asteroids included that I had not selected. They were easy enough to repair, but discouraging. A similar problem occurred with observing lists of NGC objects I want to image. Some of the NGC numbers pointed to completely different objects and the names of those objects showed up on the sky chart when highlighted. For example NGC 7789 was linked to NGC 6167 and NGC 6940 was linked to Collinder 91. Again, easy enough to fix, but discouraging. What is going on?

• Facebook
• Twitter
• LinkedIn

4 comments

• 1
  
  Garry Bluhm February 10, 2025 23:57

  Dave,
  Caroline’s Rose is one of my favorites and checked a couple of my Observing Lists to find it linked to NGC 2423 and not as NGC6167 as you have. Definitely something buggy going on.

• 1
  
  Dave Chapman February 13, 2025 14:20

  Thanks for confirming! I also had asteroid observing lists messed up

• 1
  
  Dirtbagpook February 15, 2025 23:51

  Uh oh. I too have noticed this behaviour now that you mention it. When I search for 'NGC 7789' select 'Show Observations' from the 'More' menu (or bring up the Contextual Menu option from the Sky View and then tap the 'Show Observations' icon), observations of NGC 6811 are listed. The same is true for NGC 2281. Show Observations produces a list for NGC 6281.

  Fortunately, I'm pretty sure my total number of observations is correct. 

  I feel better, but not much, that I have an alternative authority for my observations. I'd feel much better if they allowed us to export all our observations (& related Observation Session Notes) from their LiveSky. The issue 'Only 3,000 records exported' I reported in 2023 still exists when I last checked in Oct 2024.

  Best,

  Mark Force

• 1
  
  psap May 01, 2025 00:55

  Here’s another recent post reporting the same issue: Bug Report: Minor Body Orbit Data Update Changes Observed Object Names. It seems that a database update—whether automatic or manual—triggers this mismatch.