Introduction

This can be used to develop applications that sequentially process a stream of data in anyway the user desires. For the user for which even this is too restrictive see section 11.5. Beyond this one restriction what you can do is, as the adverts say, only limited by your imagination. If you look on the examples directory, you will find that example 2 is a complete, ready to run, set of user routines.

The standard user interface consists of 3 routines, all of which are optional:-

USER_DEFINE_MEMORY_SIZE

This can be used to extend the default size of any of the ZEBRA memories used by SNOMAN. For example this routine could be used to extend the memory used to hold the event data structure or the HBOOK histograms and ntuples.

USER_DEFINE_TASK

When running unmodified, SNOMAN uses a user supplied event loop program or otherwise the JOBP titles bank to determine what processors to run. Such execution time control may be disastrous when developing a specific application so this routine can be used to hardwire what SNOMAN is to run and can force it to ignore any user supplied processing sequence.

USER

This routine can be used to insert code that can effect any SU. At the initialisation and termination of each SU and during execution of each processor, this routine is called twice, once before executing call SU and again afterwards. For the call before the SU, the user can prevent the call taking place, so can append code before, after and even instead of the SU.

There are dummy versions of all these routines, with full instructions on how to use them, in the code directory.