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
For legacy reductions that have sdss_ids, we will want to know which release they were a part of. This could be a a latest release in which the final public data was produced, e.g. for manga DR17, or it could be a minimum release of the first release, e.g. DR13 for manga. We need to modify the vizdb.releases table.
We could also modify the vizdb.sdssid_to_pipes table to have multiple rows for each sdssid for every release it is in.
We might need to do this for LVM since they will have a different MJD cutoff compared to MOS observations.
Some MJD cutoff info for prior data releases, by survey.
For legacy reductions that have sdss_ids, we will want to know which release they were a part of. This could be a a latest release in which the final public data was produced, e.g. for manga DR17, or it could be a minimum release of the first release, e.g. DR13 for manga. We need to modify the
vizdb.releases
table.We could also modify the
vizdb.sdssid_to_pipes
table to have multiple rows for each sdssid for every release it is in.We might need to do this for LVM since they will have a different MJD cutoff compared to MOS observations.
Some MJD cutoff info for prior data releases, by survey.
This is a manga target (not observed in drpall), but has a boss specobjid . To get observed manga galaxies need to join with manga_drpall table.
The text was updated successfully, but these errors were encountered: