-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Include flag value for InterStellar Objects #28
Comments
Why can't this be easily replicated with other queries like e> 1? |
Well there's a NEO flag and that could be done with q<1.3 also so I suspect it's for similar reasons in that filtering on the indexed flags field is much faster than a full table scan on an unindexed float column |
NEO one might have a reason, I will inquire. It is on the slippery slope of why not a TNO flag, Centaur flag, JFC flag, etc. |
NEO flag comes from MPC - See the MPCORB extended version format. If a flag for this is wanted, the SSSC needs to petition the MPC to add it first. I will refer this issue to the relevant working group lead. |
Current data schema saves the MPC flags. so its structure does not change whether or not there is an MPC flag for ISOs. So no change needed to the Rubin Solar System data schema. |
Should the MPCORB hexadecimal
flags
include a reserved value for interstellar objects for easier filtering (in the hope that Rubin will find many more of these important objects...)The text was updated successfully, but these errors were encountered: