Euclid DB-View Web Service

Home Contact Help user undefined project ALL Tables EAS page Preferences

FlagRuleSet Overview

Attribute name	Attribute type	Docstring
AdditionalItemsToFlag	str	If a flagCondition evaluates to true, all items mentioned in all of its conditions will be automatically flagged - even those that only occur in conditions that do fail. In addition, all of their ancestors in the data model hierarchy will be flagged - to enable the display of flags occurring deep down in the data product when looking at higher levels of the data product. If additional items need to be flagged (e.g. the statistics of a list where one or more items have been flagged), they should be listed here.
Category	str	Defines categories of flags. There is a separate table of these, indicating the allowed values of flags. New flagCategory entries are not supposed to be entered into the archive by output from the pipeline - they are meant to be manually entered/updated in the archive for "proliferation control" purposes. New categories may or may not be allowed to be entered by manual quality checks or quality flag reassessments (a policy question). This is not an enumeration type, in order to allow insertion of new categories without having to modify the data model.
Explanation	str	Explanation of the flagRuleSet
FlagConditions	FlagCondition	List of conditions to be evaluated
InputDpNames	str	The name of the Input data product (e.g. DpdVisAstrometricParametersDetailed, DpdMerBksCalibratedFrame, etc.)
Name	str	Name of the flagRuleSet
Selector	str	A tag to be referenced when writing pipeline scripts, for selecting a (group of) FlagRuleSet(s) to be applied in a given run of the DynamicFlags PE. E.g. "include all FlageRuleSets with Selector="dpdVisFrame"
Severity	str	Severity of the dynamic flags, enumerated string
Subcategory	str	A more specific classification of a flag. A given flag subcategory can only occur together with a specific flag category, whereas a flag category can "contain" many flag subcategories. This table should also be "read only" seen from the pipeline, perhaps also for human flags - or at least with strict "proliferation control".

empowered by