- Do we need a big FITS header for FF visualization? We can use @weiren2’s draft JSON file as a starting point.
- Discuss “blink” functionality. Can we execute image functions in full-screen mode?
- Functions associated with
read_mouse(e.g., defining a circular region).
- We should investigate the possibility of putting displays (e.g., images, command entry, and plots/graphs) in separate browser windows. This will allow better use of space, especially on multiple displays.
- Visualization is almost working at SLAC. There is some problem with JS-Python communication.
- The PO for the “BNL-like” machines has been placed. Will be used for raft-scale images for now, but can support the full focal plane. The BNL HW exists.
- @tony_johnson’s ingest code exists in a separate branch. It uses lots of I/O. The speed is OK if it’s in memory or SSD.
@jjt’s suggestion for the segment descriptors (if we need them) in the single-extension FITS header:
We have two constraints:
- Header keywords can only contain eight characters
- The header is a flat structure - every keyword must be unique.
I propose: ABCDscrr, where:
- ABCD is the 4-character text that describes the keyword (e.g., “WDTH”).
- s is one character that numbers the segment in the CCD (hexadecimal: 0-F).
- c is one character that numbers the CCD in the raft (0-8).
- rr is two characters that number the row/column of the raft (0-4 each).
I hope that four characters is sufficient to describe the keywords.
There are 16921 = 3024 amplifiers in the focal plane. We could get away with encoding the amplifier identifier with a single 3-digit hexadecimal number (0-BCF). That would allow five text characters.