Common DFOS tools:
= Data Flow Operations System, the common tool set for DFO
The tool is distributed through the utilities
- use DFS-provided hide_raw_files for option 1
||uses ABbuilder; filterRaw
||mail to firstname.lastname@example.org
[For tradition, the tool name is 'hideFrame', although the tool will
probably be more often used for change requests than for hide requests.]
This tool assists in creating a standardized hide (option 1) or header change
request (option 2) to the archive:
|1 - Hide frame(s) (hide invalid SCIENCE or CALIB frames)
2 - Change keyword(s) (e.g. from SCIENCE to CALIB)
In Option 1, the
user is prompted to enter a list of ARCFILE names and a reason for the request. These files are then directly hidden (no DBCM ticket).
In option 2, the user is prompted for a list of ARCFILE names and the change request. That
list is then sent to the email address of the Database content management (DBCM) group
and creates a DBCM ticket.
How to use
Type hideFrame -h for on-line help, hideFrame -v for the version number. Type
to open the dialog.
How to install
The tool comes as part of utilPack.
- Hiding a raw file in the archive, and changing header keywords, are operations which are standardized with this tool
- The user can insert ARCFILE name(s) by typing, or copy and paste
- The extension .fits is automatically truncated by the tool.
- The user should provide a reason for changing or hiding, for the record.
- In option 1, the user should check for any of the hidden raw files to be removed from the files in the VCAL directory.
- In option 2, the user is prompted to confirm sending the request to email@example.com;
a copy is sent to $OP_ADDRESS.
- The tool uses 'nail' to send the email; that tool delivers an email which
appears to be sent by the operator's personal account (instead of the operational account)
which makes auto-reply easier.
- The mail generates an AR ticket; the sender will be notified about the
resolution upon closing the ticket.
| Last update: April 26, 2021 by rhanusch