You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I appreciate that it's an inherited table from the MPC and so needs to follow that format but it seems to me that a firstIncludedObservation for the "Date of first observation included in orbit solution" to complement the lastIncludedObservation would make sense for assessing the fitted arc length/orbit quality?
The text was updated successfully, but these errors were encountered:
From my reading of the DPDD and DP0.3 data schema, a combination of these columns and lastIncludedObservation would give you that information:
nobs int MPCORB: Number of observations
nopp int MPCORB: Number of oppositions
arc float MPCORB: Arc (days), for single-opposition objects
arcStart timestamp MPCORB: Year of first observation (for multi-opposition objects)
arcEnd timestamp MPCORB: Year of last observation (for multi-opposition objects)
Is there something I'm missing?
Looking at what the MPC provides this information is not provided so the Rubin pipelines would need to extract that information from the MPC records for each object
I appreciate that it's an inherited table from the MPC and so needs to follow that format but it seems to me that a
firstIncludedObservation
for the "Date of first observation included in orbit solution" to complement thelastIncludedObservation
would make sense for assessing the fitted arc length/orbit quality?The text was updated successfully, but these errors were encountered: