Project

General

Profile

Support #20457

Discuss/confirm the order of transition commands to be sent to artdaq processes

Added by Kurt Biery 12 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
07/26/2018
Due date:
% Done:

0%

Estimated time:
Experiment:
-
Co-Assignees:
Duration:

Description

Here is the email from Enrico:

Moreover, about ranking:

The boardreaders have ranks from 0 to X, eventbuilders X to Y, aggregators Y to Z and finally RoutingMaster Z+1
I didn't receive any requirement for the RoutingMaster rank so can you also check this?

Enrico

On 24/07/2018 14:31, Enrico Gamberini wrote:

Hi all,
Giovanna mentioned me that, with the new artdaq release, event builders are doing also the data logging part.

Since I have to reshuffle the FSM a bit, I would like to ask you what are the requirement (and exceptions) to follow in the new situation, as for example order of configure and start/stop.

The current situation is:

CONFIGURE: configure is sent to all artdaq processes at the same time except in the BoardReaders node in which the timing is configured (completing the transition) before the other types.

START: RoutingMaster ; Aggregators (DataLoggers + Dispatcher) ; EventBuilders, BoardReaders (again timing before others) ; OnlineMonitor and InhibitMaster

STOP: OnlineMonitor and InhibitMaster ; BoardReaders (again timing before others) ; EventBuilders ; Aggregators (DataLoggers + Dispatcher) ; RoutingMaster

Exceptions:
- daq.shutdown command is not sent to Dispatchers
- processes are killed after DataLoggers go to UNKNOWN

Is this logic confirmed, of course removing the DataLoggers from the logic?

Thank you,
Enrico



Also available in: Atom PDF