This information is relevant to more than one handler.
Module information not relevant to a particular handler can be ignored,
and indeed may not be coded in a handler for which it is not required.

The Fera information can be configured in two ways.

1 - Module config mode

Each Fera module requires a record of the form

module module-name  vsn pattern  max-channels  n-databits  base-group-number


where 
name         is for clarity
vsn          is FERA module assigned VSN number
pattern      =0 for no pattern word
             =1 for pattern word (e.g. Silena ADCs)
             =2 for Pattern Register - special case
             =3 for RIS module (Afrodite) - special case
	     =4 for c1011 module - special case

max-channels is number of separate ADCs on the module
n-databits   is number of databits (remaining bits assumed to be SA)
base-group-number is user assigned - must be unique over all modules

Each channel of the module is assigned to a single item group starting from the base-group-number upwards. Since the first module below has 8 channels, then they are assigned to group numbers 1 to 8. In this case, the next module will assign group numbers from 9 upwards, etc.

e.g.

module s4418     0   1   8   12   1
module s4418     1   1   8   12   9
module s4418     2   1   8   12  17
module s4418     3   1   8   12  25
module s4418     4   1   8   12  33
module s4418     5   1   8   12  41
module s4418     6   1   8   12  49
module s4418     7   1   8   12  57
module s4418     8   1   8   12  65
module s4418     9   1   8   12  73
module pattern  21   2   5   16  100
module RIS      30   3  14   16  120
module c1011    32   4   2   16  200

The sort program will require a FORMAT definition like ...

param[1:105] (p)

2 - Group config mode

If group records are defined in the config file after all the module records, then the events are formatted differently as follows.

Each group requires a record of the form

group group-number vsn:sa vsn:sa ... (upto 8 vsn:sa pairs)

The Fera VSN-SA pairs are assigned individually to groups.
If the config file contained ...

group  1  0:0  0:1  0:2  0:3
group  2  0:4  0:5  0:6  0:7
group  3  1:0  1:1  1:2  1:3
group  4  1:4  1:5  1:6  1:7
group  5  2:0  2:1  2:2  2:3
group  6  2:4  2:5  2:6  2:7
group  7  3:0  3:1  3:2  3:3
group  8  3:4  3:5  3:6  3:7
group 11  4:0  4:1  4:2  4:3
group 12  4:4  4:5  4:6  4:7
group 13  5:0  5:1  5:2  5:3
group 14  5:4  5:5  5:6  5:7
group 15  6:0  6:1  6:2  6:3
group 16  6:4  6:5  6:6  6:7
group 17  7:0  7:1  7:2  7:3
group 100 21:0 21:1 21:2 21:3 21:4
group 20  30:0 30:1 30:2 30:3 30:4 30:5 30:6 30:7 30:8 30:9 30:10 30:11 30:12 30:13


The sort FORMAT could look like ...

leps[1:8]     (p1, p2, p3, p4)
clover[11:17] (p1, p2, p3, p4)
pattern[100]  (p1, p2, p3, p4, p5)
ris[20]       (p1, p2, p3, p4, p5, p6, p7, p8, p9, p10, p11, p12, p13, p14)

NOTE: It is the presence of one or more "group" records that changes the event formatting mode from module-based to group-based.

NOTE: The basegroup field of the module record is not used in Group Mode but still requires a value.

Variable length Group config mode

All the vsn:sa data words preceeding the id=X keyword are output as part of the fixed length section irrespective of the data value.

The vsn:sa data words following the id=X keyword are output only if the data word is non-zero. In this case "X" id or tag bits are added to the top of the data word.

If the group line was specified as follows ..

group  1  8:0 id=3  0:0  0:1  0:2  0:3

The sort FORMAT could look like ...

leps[1:8]     (p0, id1:3,p1:13, id2:3,p2:13, id3:3,p3:13, id4:3,p4:13)