support visit-level (calexp) cutouts?

[yymao]

After consulting @wmwv's notebook, I've made a major backend update, and the service now can in principle support visit-level (calexp) cutouts. However, for a given coordinate (RA, Dec), there are thousands of visits, and it is prohibitive to fetch and display all of them at once.

So I wonder what are the use cases when people want to get visit-level cutouts using this web service (opposite to using jupyter notebook)?

• Do people just want to visits that have a detection (say SNR larger than some threshold), similar to @wmwv's notebook did? If so, the cutout service need to identify the object using the RA and Dec given, and hence need to access the catalogs and find the nearest object, and use object ID to find SNR.
• Or do people want to specify visit numbers? In other words, look at cutouts given RA, Dec, and visit ID?
• Or other use cases that I haven't thought about.
• Or this web service should just not worry about visit-level cutouts at all?

Input on this will be very welcome!

[wmwv]

I think the first implementation should provide a form to specify visit numbers. If you don't specify any, then it will look for all. But there could be a checkbox (?) that says just search for the visit numbers and return them and then the user can select.

[wmwv]

On a minor technical note: The example Notebook I had was polling the forced-photometry catalogs based on the Object positions. The check to make sure it was in the catalog was to make sure it was in that region of sky. It should have had a measurement if the image fully covered the RA, Dec with enough room for the PSF. I need to make this part smarter and just use the actual WCS to do this check based just on RA, Dec.

[yymao]

@wmwv thanks for the input. When the user doesn't specify visit numbers, it'll be technically challenging to retrieve all possible images, so we'll probably need to make visit numbers a required input if the user wants visit-level images.

Which style do you think it's more useful to specify the visit numbers?

(1) Requires one visit number for each coordinate:

ra1 dec1 visit1
ra2 dec2 visit2
...

(2) Specify one visit number for each submission:

[visit: visit]
ra1 dec1
ra2 dec2
...