Provide VisitInfo as a table

[wmwv]

Provide the VisitInfo information as a table accessible through GCR (and likely anything else, it will be a simple table).

[wmwv]

Possibilities:

1. Use the VistInfo object.

PRO: This is what we want. CON: I think this requires reading all of the VistInfo objects for all files and recording in a DB.

2. Use the registry created on ingest. This contains:

id|run|visit|filter|date|dateObs|expTime|raftName|detectorName|detector|snap|object|imageType|testType|lsstSerial|wavelength
1|12469|12469|y|2022-01-18T02:10:37.915|2022-01-18T02:10:37.915|30.0|R24|S01|109|0|UNKNOWN|SKYEXP|IMSIM|LCA-11021_RTM-000|-666
2|12469|12469|y|2022-01-18T02:10:37.915|2022-01-18T02:10:37.915|30.0|R24|S02|110|0|UNKNOWN|SKYEXP|IMSIM|LCA-11021_RTM-000|-666
3|12469|12469|y|2022-01-18T02:10:37.915|2022-01-18T02:10:37.915|30.0|R24|S10|111|0|UNKNOWN|SKYEXP|IMSIM|LCA-11021_RTM-000|-666
4|12469|12469|y|2022-01-18T02:10:37.915|2022-01-18T02:10:37.915|30.0|R24|S11|112|0|UNKNOWN|SKYEXP|IMSIM|LCA-11021_RTM-000|-666
5|12469|12469|y|2022-01-18T02:10:37.915|2022-01-18T02:10:37.915|30.0|R24|S12|113|0|UNKNOWN|SKYEXP|IMSIM|LCA-11021_RTM-000|-666
6|12469|12469|y|2022-01-18T02:10:37.915|2022-01-18T02:10:37.915|30.0|R24|S20|114|0|UNKNOWN|SKYEXP|IMSIM|LCA-11021_RTM-000|-666
7|12469|12469|y|2022-01-18T02:10:37.915|2022-01-18T02:10:37.915|30.0|R24|S21|115|0|UNKNOWN|SKYEXP|IMSIM|LCA-11021_RTM-000|-666
8|12469|12469|y|2022-01-18T02:10:37.915|2022-01-18T02:10:37.915|30.0|R24|S22|116|0|UNKNOWN|SKYEXP|IMSIM|LCA-11021_RTM-000|-666
9|12469|12469|y|2022-01-18T02:10:37.915|2022-01-18T02:10:37.915|30.0|R30|S00|117|0|UNKNOWN|SKYEXP|IMSIM|LCA-11021_RTM-000|-666
10|12469|12469|y|2022-01-18T02:10:37.915|2022-01-18T02:10:37.915|30.0|R30|S01|118|0|UNKNOWN|SKYEXP|IMSIM|LCA-11021_RTM-000|-666

PRO: It exists CON: Doesn't record much of what we want. Probably only visit, filter, dateObs mapping is useful. (We can assume 30 second exposures so looking that up isn't a key use case.)

4. The OpSim DB (in flat-file form?) for the run used. PRO: Has everything we want, modulo dithering. CON: May not be exactly what was simulated, due to dithering, but also I fear there might be issues about precise bookkeeping of time.

[wmwv]

The VisitInfo remains the thing to do.

But it's possible that 2+3 (registry+OpSim run) covers most use cases and will be very quick to set up.

[wmwv]

It's also possible that the Image Simulation group already has this product trivially available.