New Update to V4.0j R7 should fix problems with minor planet database - Printable Version +- Skyhound Forums (https://skyhound.com/forums) +-- Forum: General & Visual Observing (https://skyhound.com/forums/forumdisplay.php?fid=13) +--- Forum: Observing Close Approaching Asteroids (https://skyhound.com/forums/forumdisplay.php?fid=28) +--- Thread: New Update to V4.0j R7 should fix problems with minor planet database (/showthread.php?tid=2389) |
New Update to V4.0j R7 should fix problems with minor planet database - theskyhound - 2021-12-29 Hello, As advanced users of the minor planet database, I wanted to let you guys know that the latest update fixes several bugs in the minor planet database management. In particular, deleting a minor planet, or a set of elements, could truncate or corrupt your database. Adding a minor planet manually could cause similar problems. I recommend cleaning your database (using the built-in feature) after the update, by deleting as many minor planets as possible. There is no danger in doing so, as all necessary elements are not allowed to be deleted. Once the database is as clean as you can make it, close the Minor Planet Database dialog. Then re-open it and add new and more recent orbital elements. I apologize for these problems that I know have caused considerable trouble, and I wish you guys the best hunting in 2022! RE: New Update to V4.0j R7 should fix problems with minor planet database - PMSchu - 2021-12-30 Hi Greg, Thanks. Will the R7 (now R8) version use today's epoch date when the NEAs are updated? It looked like R6 was using the epoch date that was the farthest into the future. After I repopulated the MP DB using the full MPC download last month, none of the NEAs had their epoch dates changed to the current date, they were retaining the 2022 Jan 21 epoch. As new NEAs were downloaded they were assigned the 'Today's' date for their elements, as expected. Phil S. RE: New Update to V4.0j R7 should fix problems with minor planet database - theskyhound - 2021-12-30 I explained this in an earlier post. Please go back and find that conversation. I explained the issue and how it was baked into the process at the time. |