The following requirements appear to be appropriate for verification, or partial verification, as part of Operations Rehearsal #2.
See - DM-24991Getting issue details... STATUS .
Assumptions and limitations
I have left out some verifications that appear trivial in the OR2 context or simply common to any SP interactions, e.g., logging in. These are well established de facto and at this point require more rigorous verification including edge cases.
The assumptions I have made are:
- OR2 will produce images but no catalogs; images will not be analyzed for sources. Testing catalog display, or catalog-image overlays, will therefore not be natural.
- OR2 will most likely produce only equivalents to daytime in-dome data, and therefore images will have no WCSes in sky coordinates.
- A supplementary table covers additional requirements that become relevant for on-sky images with even a crude WCS.
- On the time scale of OR2 it will not yet be possible to produce an image metadata service (ObsTAP, in particular) populated in near-real-time with acquired images. For this reason, the Portal verifications outlined below will have to be driven either via API from the Notebook Aspect or via file upload. No Portal image query operations will be possible.
- On the time scale of OR2 no functional User File Workspace visible both from the Notebook Aspect and Portal Aspect will be available.
I have not yet understood the on-disk file format for images that will be used in OR2; this might affect some details of this assessment and I'll try to refine this point.
I make a "full/partial" distinction between requirements whose full main body is relevant to OR2 and requirements which even in the best case of available effort could not be verified in full. Example: DMS-PRTL-REQ-0045 covers visualization of uploaded catalog and image data; I assume that only image data will be available, so this is a "partial". However, note that in no case would the normal activities of OR2 allow a comprehensive and conclusive verification of any of these requirements, including all relevant edge cases, without extra effort to make this a goal of the rehearsal. ("No free conclusive verifications.")
I make a "natural/artificial" distinction between requirements that seem likely to be exercised in the course of other plausible OR2 activities and others that could be exercised but would be "side trips" for the OR2 team.
Available verifications
Requirement ID | Title | Verification Element(s) | Test Case(s) | Full/Partial | Natural/Artificial | Comments |
---|---|---|---|---|---|---|
Basic Notebook Aspect operation | ||||||
DMS-NB-REQ-0005 | Interactive Python Environment | Full | Natural (in part) | The ability to run notebooks is central to the planned OR2 activities. It would probably be artificial to use the Python Console feature instead of a notebook, but it certainly could be tested. | ||
DMS-NB-REQ-0006 | Unix Shell Access | Full | Natural | Most likely this capability will be needed at some point. | ||
DMS-NB-REQ-0007 | Pre-installed Containerized Software Releases | Full | Natural | This is a core capability required in OR2. | ||
DMS-NB-REQ-0009 | Data Access Middleware Availability | Full | Natural | Butler access is a core capability required in OR2. | ||
DMS-NB-REQ-0010 | Common Astronomy Package Availability | Full | Natural | This is likely to be heavily used in OR2, for making plots. | ||
DMS-NB-REQ-0011 | User Package Installation | Full | Natural (probably) | It's likely that someone will want to use an additional package of their own choosing. | ||
DMS-NB-REQ-0013 | Persistent User Home File Space | Full | Natural | This is likely to be a core capability required in OR2. | ||
DMS-NB-REQ-0016 | Shared File Space | Partial | Natural | This is a core capability required in OR2. It is unlikely that the access controls mentioned in the requirement's Discussion will be exercised to any extent, however. | ||
Specific Notebook Aspect capabilities | ||||||
DMS-NB-REQ-0032 | Image Visualization | Full | Natural | Use of afw.display with either the matplotlib or Firefly back ends seems certain to be part of OR2. | ||
DMS-NB-REQ-0030 | Access to Portal Visualization API | Partial | Natural | Covered, for images. Relatively unlikely to be covered for catalogs. | ||
API Aspect | ||||||
DMS-API-REQ-0034 | Butler Interface to Data Products | Partial | Natural | Some elements of this will automatically be covered by running notebooks in the LDF environment as part of OR2. | ||
Specific Portal Aspect capabilities | ||||||
DMS-PRTL-REQ-0045 | Visualization of Uploaded Tabular and Image Data | Partial | Natural | OR2 should provide many opportunities to upload images for visualization. It does not seem likely to produce catalog-style tabular data. | ||
DMS-PRTL-REQ-0062 | Display Native Single-Visit Image Data Products | Partial | Natural | OR2 will produce raw images and single-epoch calibration images, but likely not PVIs, and certainly not difference images. | ||
DMS-PRTL-REQ-0067 | Display Calibration Image Data Products | Full | Natural | If CPP is run, OR2 is likely to produce all the major types of processed calibration image products. | ||
DMS-PRTL-REQ-0069 | Image Property Sheet | Partial | Artificial | A header display UI is available, but due to work cut off by DM-10, additional planned work to ensure that it is populated with useful information when driven via afw.display was not carried out. it is more useful when looking directly at an uploaded file in its on-disk format. | ||
DMS-PRTL-REQ-0070 | Provide Coordinate Display Tools for Images | Partial | Natural | Only partial verification is possible without WCS data, as only pixel coordinates will be able to be displayed. | ||
DMS-PRTL-REQ-0071 | Image Pixel Content Display | Full | Natural | Any plausible use of the image display would likely include using the mouse to inspect pixel values. | ||
DMS-PRTL-REQ-0072 | Image Spatial Manipulation | Full | Artificial (mostly) | The requirement covers a wide range of capabilities, most of which are unlikely to be extensively explored without a specific directive to do so. | ||
DMS-PRTL-REQ-0074 | Image Appearance Manipulation | Full | Natural (mostly) | Rescaling images and applying different colormaps appears to be a likely activity as part of normal inspection of the produced images. | ||
DMS-PRTL-REQ-0075 | Image Mask and Variance Overlays | Partial | Natural | If CPP is run, presumably it will produce meaningful mask planes that would be of interest to visualize. "Partial" because it would not be possible to test with the mask plane lists of PVIs or coadded images, which might present additional difficulties (e.g., number of planes, length of their names, etc.); eventually the requirement needs verification against all mainstream image data types. | ||
DMS-PRTL-REQ-0077 | Image Overlays: Adjustment of Colors and Positions | Partial (very) | Artificial | A fraction of the overlay tool capability (e.g., the distance tool) should be available for no-WCS images. It's not clear that even using it, let alone adjusting it, would be a natural activity in OR2. | ||
DMS-PRTL-REQ-0084 | Point Coordinate Display | Partial | Natural | This is a child of DMS-PRTL-REQ-0070 with greater specificity. | ||
DMS-PRTL-REQ-0085 | Distance Measurement Tool | Partial | Artificial | Only the pixel-coordinates capability can be exercised without a WCS. It's not clear that this would be particularly natural to use in OR2, on calibration images. | ||
DMS-PRTL-REQ-0098 | Statistical Measurement on Image Data | Full | Artificial | The tool exists but does not yet have the full list of capabilities enumerated in the requirement, nor has it been iterated on with Rubin/LSST pipelines users, so it's not clear that it will be all that useful in OR2. However, it would be valuable to ask the OR2 team to at least try it out; any feedback would be useful. (Note that the Portal team is well aware that the Pipelines team is inherently not very interested in having these sorts of computations done directly in Firefly rather than in the stack. The capability to have the stack computations triggered from the Portal was incomplete at DM-10.) | ||
DMS-PRTL-REQ-0111 | Image Data Download | Partial | Artificial | "Partial" because no workspace will be available, and because it can only be tested for image viewing, not image metadata viewing, in the OR2 environment. "Artificial" because it's almost inconceivable (to gpdf) that a Pipelines user would be interested in downloading to their own computer a copy of the image data pushed to Firefly by afw.display . |
Additional verifications possible if on-sky images with WCSes are produced
Requirement ID | Title | Verification Element(s) | Test Case(s) | Full/Partial | Natural/Artificial | Comments |
---|---|---|---|---|---|---|
DMS-PRTL-REQ-0070 | Provide Coordinate Display Tools for Images | Full | Natural (mostly) | Exploring conversion to, e.g., Galactic or B1950 equatorial coordinates would not be a natural activity. | ||
DMS-PRTL-REQ-0073 | Multi-Image Scaling and Aligning | Partial | Natural | "Partial" because it seems unlikely that the ability to handle coadded images could be tested explicitly (though there is no real reason to expect a difference from single-epoch calibrated images in this area). | ||
DMS-PRTL-REQ-0086 | Coordinate Grid Overlays | Not useful without a WCS | ||||
DMS-PRTL-REQ-0087 | Astrophysical Compass Overlay | Not useful without a WCS |