Common DFOS tools:
Policy for hiding frames

dfos = Data Flow Operations System, the common tool set for DFO
*make printable

Guidelines for hiding frames

compiled by Sabine Moehler

see also: tool description hideFrame

The dfos tool hideFrame can be used to hide frames without information or with misleading information. Here are a few rules about when a file should be hidden.

Examples for data to be hidden are

On the other hand, a valid flat that has a wrong header keyword (e.g. DPR.TYPE) should get this value corrected (also by using the hideFrames dialog but asking DBCM for the correction), and not be hidden.

Examples for grey areas are

In the following cases files should not be hidden, but comments should be provided either for the raw data or the products:

If you decide to hide files *after you have certified them*, it is very important to check that they are not included in any harvested AB, and that they are not available for further associations. Otherwise a calSelector user will run into trouble since these download requests are doomed to fail. Therefore, these checks should be made:

Note that hideFrame v1.3+ takes care of these requirements.

Master calibrations created from these files must be hidden as well.

Last update: April 26, 2021 by rhanusch