6// In general negative return codes signal some fatal condition where continuing is just a waste of cpu
7
8// SubsysReco module return codes:
9// ABORTRUN: signals that processing should be aborted for this run, the process will exit with a non zero exit
10// ABORTEVENT: abort reconstruction of the current event, reset everything and process the next event
11// EVENT_OK: generic good return
12// DISCARDEVENT: tell a connected output manager not to save this event but continue processing
13// DONOTREGISTERSUBSYSTEM: during registration, module indicates it doesn't want to be registered
14
15// Synchronization
16// SYNC_OK: all good
17// SYNC_FAIL: synchronization failed (leads to a search for matching events by the sync manager)
18// SYNC_NOOBJECT: no synchronization object in this input manager, take current event without check
19// RESET_NODE_TREE: internal use - under certain conditions during the synchronization process Fun4All needs to reset the node tree to clear the prvious event