OCM Data Acquisition Control

Note

daqOcmServer hosts the Data Acquisition control interface daqif.OcmDaqControl under URI path /daq.

class daqif.OcmDaqControl

OCM Data Acquisition control interface.

StartDaq(id, file_prefix, prim_sources, meta_sources, properties) → DaqReply

Create and start new data acquisition. If id is not provided (left empty) daqOcmServer will create a unique identifer automatically.

The format for prim_sources and meta_sources is a space separated list of sources in the format: <name>@<rr-uri>, e.g. meta-source@zpb.rr://example:1234/daq.

The format might be changed in future version to be part of the JSON property parameter.

There must be at least 1 data source.

Fail-fast

If any source fails to start the command will fail.

Parameters
  • id (str) – Optional unique identifier of data acquisition.

  • file_prefix (str) – Optional file name prefix.

  • prim_sources (str) – List of primary data sources (e.g. detectors).

  • meta_sources (str) – List of metadata sources (e.g. FCF Device Manager or CCS).

  • properties (str) – JSON properties.

Returns

If id was provided that is returned as an acknowledgement, otherwise the id generated by daqOcmServer is returned.

Return type

DaqReply

Raises

DaqException – On fatal error.

StopDaq(id) → DaqReply

Stops data acquisition and keep any data acquired.

Fail-Fast

If all data sources fail the command will report error by throwing DaqException. A partially successful execution is reported using normal status reply (which includes information about any partial failure). This is done because it is prioritized to create a partially complete data product over discarding all acquired data.

Parameters

id (str) – Id of data acquisition to stop.

Return type

DaqReply

Raises

DaqException – On fatal error.

ForceStopDaq(id) → DaqReply

Like StopDaq() the command stops data acquisition and keeps any data acquired. The only difference is that if non-fatal error occurs the Data Acquisition is marked as stopped whereas StopDaq() would not.

Fail-slow

The command is resilient to non-fatal errors. If any non-fatal errors occur the error flag in the reply is set but no exception is thrown. If fatal error occur DaqException is thrown.

Warning

Any data source that failed to stop properly will not be able to provide data to the Data Acquisition or the final Data Product.

Although daqOcmServer is always left in a consistent state, any data source that failed to stop may not. Manual intervention my be necessary to restore a problematic data source to a functional state.

Parameters

id (str) – Id of data acquisition to forcibly stop.

Return type

DaqReply

Raises

DaqException – On fatal error.

AbortDaq(id) → DaqReply

Aborts data acquisition and discards any data acquired.

Fail-fast

If any error occur DaqException is thrown and the DAQ state remains in Aborting.

Parameters

id (str) – Id of data acquisition to abort.

Return type

DaqReply

Raises

DaqException – On fatal error.

ForceAbortDaq(id) → DaqReply

Like AbortDaq() the command aborts data acquisition and discards any data acquired. The only difference is that if non-fatal error occurs the Data Acquisition is marked as aborted whereas AbortDaq() would not.

Fail-slow

The command is resilient to non-fatal errors. If any non-fatal errors occur the error flag in the reply is set but no exception is thrown. If fatal error occur DaqException is thrown.

Warning

Although daqOcmServer is always left in a consistent state, any data source that failed to abort may not. Manual intervention may be necessary to restore a problematic data source to a functional state.

Parameters

id (str) – Id of data acquisition to forcibly abort.

Return type

DaqReply

Raises

DaqException – On fatal error.

UpdateKeywords(id:str, keywords:str) → DaqReply

Update keywords for specified Data Acquisition. For each keyword:

  • If it already exist*, it is updated with the provided value,

  • otherwise it is added.

*) OCM will compare keyword name as provided, while considering it it’s an ESO hiearchical keyword or standard FITS keyword.

Fail-fast

Command will not make any attempt to be robust against errors. Failures are treated as fatal and DaqException will be thrown.

Parameters
  • id (str) – Id of data acquisition to update.

  • keywords (str) – JSON encoded set of keywords. Refer to JSON keywords schema for details.

Return type

DaqReply

Raises

DaqException – On fatal error.

AwaitDaqState(id, state, substate, timeout) → AwaitDaqReply

Await a particular Data Acquisition state. This is mainly used to support sequencing of higher level coordination activities.

The command will reply when condition is fulfilled or times out. When it times out this is indicated in the reply with AwaitDaqReply.timeout set to true.

Condition is fulfilled whenever the requested state and substate is either achieved or no longer possible to achieve. Awaiting e.g. the condition. DaqState.StateMerging/ DaqSubState.Scheduled will be fulfilled also for DaqState.StateCompleted/DaqSubState.Aborted. Perhaps a more likely scenario is that multiple state transitions occurred before request was handled, such that a subsequent state is reported instead of the requested state/substate.

Note

OCM v1.0.0 implements all substates in DaqState.StateAcquiring and py:attr:DaqState.StateCompleted/DaqSubState.Aborted. As such it is not possible to await other states.

Parameters
Returns

Current Data Acquisition status and indication if operation timed out.

Return type

AwaitDaqReply

Raises

DaqException – On fatal error (e.g. invalid arguments).

GetDaqStatus(id) → DaqStatus

Get Data Acquisition status.

Parameters

id (str) – Id of data acquisition to get status for.

Return type

DaqStatus

Raises

DaqException – On fatal error.

GetActiveList() → List[DaqStatus]

Get list of active Data Acquisitions (i.e. not in daqif.DaqState.StateCompleted).

Returns

List of active Data Acquisitions.

Return type

List[DaqStatus]

Raises

DaqException – On fatal error.