Problem: As flows has evolved, the pipeline has become more of a general SN photometry and candidate tracking one than the initial limited scope one for VLT + supporting observations we envisioned. Given that scope, how does pointing and OB generation fit in? How do we currently do our cuts, and how should we expose this to users to create their own local sequence lists from our catalogs? This might need to be merged with #22 to make sense.
Proposal:
Initially, we decided to use the most restrictive instrumental set-up to create the reference list via its pointing criteria. Meaning using the (VLT) NIR to set the conditions for the optical. But with the use of color-terms, this should be unnecessary. Ultimately, we probably want to allow a unique reference list for each instrument and target combination based on catalog reference star colors, magnitudes, and positions.
For now, the default should be to use the NIR instrument to set the criteria for the target, and to use that reference list also for the optical, as it is currently done. However, many objects won't have VLT data and need a different (less restrictive) criteria. So we need a way to enter a criteria for each object, and failing that, using a conservative default. I know we currently have some dummy defaults.
But ideally, we should test using a separate cut-off for each target/instrument pairing. This would need to go into the catalogs script. When fetching the catalog, we would also feed in the current instrument, and it would search for a different set of criteria, and fallback to the default for the object if it doesn't exist. Something like that.
The querying of the catalog around the object is currently wide enough to accommodate basically any professional ground based telescope that would be used with FLOWS, so I think we can leave that in place as is. But the creation of the final reference list from that initial circular region needs to be customized for each instrument.
Problem: As flows has evolved, the pipeline has become more of a general SN photometry and candidate tracking one than the initial limited scope one for VLT + supporting observations we envisioned. Given that scope, how does pointing and OB generation fit in? How do we currently do our cuts, and how should we expose this to users to create their own local sequence lists from our catalogs? This might need to be merged with #22 to make sense.
Proposal:
Initially, we decided to use the most restrictive instrumental set-up to create the reference list via its pointing criteria. Meaning using the (VLT) NIR to set the conditions for the optical. But with the use of color-terms, this should be unnecessary. Ultimately, we probably want to allow a unique reference list for each instrument and target combination based on catalog reference star colors, magnitudes, and positions.
For now, the default should be to use the NIR instrument to set the criteria for the target, and to use that reference list also for the optical, as it is currently done. However, many objects won't have VLT data and need a different (less restrictive) criteria. So we need a way to enter a criteria for each object, and failing that, using a conservative default. I know we currently have some dummy defaults.
But ideally, we should test using a separate cut-off for each target/instrument pairing. This would need to go into the catalogs script. When fetching the catalog, we would also feed in the current instrument, and it would search for a different set of criteria, and fallback to the default for the object if it doesn't exist. Something like that.
The querying of the catalog around the object is currently wide enough to accommodate basically any professional ground based telescope that would be used with FLOWS, so I think we can leave that in place as is. But the creation of the final reference list from that initial circular region needs to be customized for each instrument.