An acquisition task may be needed to initiate the processing. The following example shows such a pattern where a wait task is created to check the presence of input data in the acquisition time window 10:00 to 12:00. A task is dedicated to raise a red alarm, by 11:00, if no data is are not yet arrived, to have operators and analysts aware in advance to be and careful about this. As soon as incoming data are detected, the data event is set, wait task wait task runs every 5 minutes and set the data event when input data are found ; it shall sleep 60 seconds, after setting the event, before completing, to ensure the server receives the event and starts the data task, before wait task completion and immediate requeue, thanks to cron. data task (validation and preprocessing) . It will then set the ready event and acq family will become complete, provided underneath tasks are complete or queued, so that rt/wait and late_alert do not run any further.
| Code Block |
|---|
family acq
complete acq/data eq complete
task data
trigger rt/wait:data
event ready
family rt
complete data:ready
task wait
event data
cron 10:00 12:00 00:05
endfamily
task late_alteralert
trigger not data:ready
time 11:00
endfamily
|
...
In some situation, we may want the acquisition family to detect if data are already available (catchup mode), and start the processing immediately, before reaching the real-time mode, when the wait task is submitted regularly to check data arrival during the time interval.
| Code Block |
|---|
family acquisition
complete acq/data eq complete
family rt
complete data:ready or nrt eq complete
task wait
event data
cron 10:00 12:00 00:05
endfamily
task late
trigger not data:ready
time 11:00
family nrt
complete data:ready
task wait
event data
endfamily
task data
trigger rt/wait:data or nrt/wait:data
event ready
endfamily
|