Inheritance diagram for RunningTagUpdateMode:

Collaboration diagram for RunningTagUpdateMode:

Static Public Attributes
int	STRICT = 1
	Allow multiple validity for payloads in the staging tag which don't have to start exactly at the first valid run but have to cover the whole area from their first validity to infinity.

int	ALLOW_CLOSED = 2
	Similar to strict but allow validity to not extend to infinity.

int	FIX_CLOSED = 3
	Similar to strict but automatically extend validity to infinity.

int	SIMPLE = 4
	Only allow trivial (0,0,-1,-1) validities in the staging tag and only one validity per payload name.

int	FULL_REPLACEMENT = 6
	Replace full state of the globaltag. More...

Detailed Description

Define the different modes for the update of a running tag

Definition at line 23 of file runningupdate.py.

Member Data Documentation

◆ FULL_REPLACEMENT

int FULL_REPLACEMENT = 6

static

Replace full state of the globaltag.

Similar to ALLOW_CLOSED but any payload present and open in the running tag that is not part of the staging tag will be closed. After the update the new valid payloads will be exactly the ones in the staging tag

Definition at line 40 of file runningupdate.py.

The documentation for this class was generated from the following file:

framework/scripts/conditions_db/runningupdate.py

Static Public Attributes

Detailed Description

Member Data Documentation

◆ FULL_REPLACEMENT