Common DFOS tools:
Documentation
|
| dfos
= Data Flow Operations System, the common tool set for DFO |
 make printable |
New:
v1.2:
- new option 3 to overwrite already ingested mcalib
|
The tool is distributed through the utilities
package (utilPack).
|
| |
v1.3:
- check for hidden files in VCAL and harvested ABs
v1.3.2:
-
option 3 disabled
- config file obsolete
|
![[ used databases ]](database.png "[ used databases ]") databases |
none |
![[ used dfos tools ]](tool_icon.gif "[ used dfos tools ]") dfos
tools |
uses ABbuilder; filterRaw |
![[ output used by ]](/images/text.gif "[ output used by ]") output |
change/hide request |
![[ upload/download ]](download-page-blue.gif "[ output used by ]") upload/download |
mail to dbcm-help@eso.org |
|
[For tradition, the tool name is 'hideFrame', although the tool will
probably be more often used for change requests than for hide requests.]
hideFrame
Description
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) |
The
user is prompted to enter a list of ARCFILE names and a reason for the request. That
list is then sent to the email address of the Database content management (DBCM) group
and creates a DBCM ticket.
The user has two options:
1 - hide frame(s) (in case of invalid SCIENCE or CALIB frames)
2 - change keyword(s) (e.g. DPR.CATG from SCIENCE to CALIB; multiple changes can be submitted)
Output
None.
How to use
Type hideFrame -h for on-line help, hideFrame -v for the version number. Type
hideFrame
to open the dialog.
How to install
The tool comes as part of utilPack.
Configuration file
None.
Operational aspects:
- 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 (to make life easier for DBCM)
- The user should provide a reason for changing or hiding, for the records
- The user is prompted to confirm sending the request to dbcm-help@eso.org;
a copy is sent to $OP_ADDRESS
- In option 1, the tool checks that the files from the request are not
included in any harvested AB, and that they are not available for further associations
- 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