RobEmu star in DE domain

Simple simulation of ATLAS ROB (emulator).

Derived from: DEStar
Location: ~gjc/ptolemy/src
Version: 1.0 "18/03/99"
Author: G. J. Crone

Inputs

netInput

message

Message representing input received through the network

Outputs

netOutput	message	Message representing output sent through the network
EB_Output	message	Message representing data collection to EBIF

States

myid	IntState	Node number of this ROB	"1"
debugLevel	IntState	Amount of output to print on screen: 0 = none, 1 = errors, 2 = errors + info, 3 = ... + debugging, 4 = ... + heavy debugging or all	"2"
cpuSpeed	IntState	Frequency (MHz) of hardware on which ROB runs	"300"
request_prepare_time	FloatState	Time taken to set up an event Data or RoiData request	"10.0"
ROBFloat	FloatState	ROI size dependent contribution to response preparation time	"0.112"
ROSeventData_prepare_time	FloatState	Time taken to prepare data to be sent to Event Builder	"0.0"
fragment_size	IntState	Size of data fragments in bytes	"1024"
delete_handling_time	FloatState	Time taken per event to handle a delete requst	"5.0"
magic_delay	FloatState	Arbitrary tunable delay	"0.0"
srcident	IntState	address of src node in Event Builder to which ROB sends data	"700"
detector	StringState	name of the detector for which this ROB has data	"DUMMY"
startTime	FloatState	Time of generation of first event	"0.0"

Details

This node listens for data requestes and makes up a data messsage to satisfy them. This node does not accept any front end input. Delete requests may cause data requests to be delayed but no other action is taken.

The number of data requests (Data or RoiData) that have not yet been sent out is calculated as each new request is read and the maximum is printed at wrapup.

Messages Received

DataRequest: Receipt of a DataRequest causes a Data message to be generated and scheduled for output on the netOutput at request_prepare_time after the ROB next becomes available.
RoiDataRequest: Receipt of an RoiDataRequest causes an RoiData message to be generated and scheduled for output in the same way as a DataRequest causes a Data message to be generated.
DeleteData: Receipt of a DeleteData message only affects the scheduling of subsequent Data and RoiData messages by adding delete_handling_time to the time at which the ROB will be available for each event to be deleted.

See: source code, RobEmu users