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
We should generate MOCs for all the SDSS catalogs and surveys. We should look into using either mocpy or hipsgen-cat, and explore the differences and similarities, and which one is better. For now these can be just spatial MOCs, but we could also explore creating STMOCs for space+time coverage. Do we want to create a new package sdss-moc that can generate these in the future?
Update or check the valis mocs/ endpoints to load the new products. Note Aladin-Lite has old SDSS catalogs already included, but only eboss.
The list of catalogs should be:
BHM summary file
MWM summary file
Astra summary files
(or possibly the allspec file)
manga and mastar dr17 summary files
eboss/boss dr17
apogee dr17
MOCs should be created for each data release and would be stored in the SDSS_HIPS directory in sdsswork for now.
The text was updated successfully, but these errors were encountered:
We should generate MOCs for all the SDSS catalogs and surveys. We should look into using either mocpy or hipsgen-cat, and explore the differences and similarities, and which one is better. For now these can be just spatial MOCs, but we could also explore creating STMOCs for space+time coverage. Do we want to create a new package
sdss-moc
that can generate these in the future?Update or check the valis
mocs/
endpoints to load the new products. Note Aladin-Lite has old SDSS catalogs already included, but only eboss.The list of catalogs should be:
MOCs should be created for each data release and would be stored in the SDSS_HIPS directory in sdsswork for now.
The text was updated successfully, but these errors were encountered: