SctData.ModuleConfiguration Class Reference

Represents the configuration of a module. More...

Collaboration diagram for SctData.ModuleConfiguration:

[legend]List of all members.

Public Member Functions
	ModuleConfiguration (ABCDModule data)
ABCDModule	getData ()
ChipConfiguration	getChipConfiguration (int chip)
boolean	isPresent ()
	presence means module configurations are present in the ROD and therefore sent triggers and read out by the histogramming code
boolean	isActive ()
	active means a module "takes part in a scan" ie has its configuration modified by the histogramming engine
void	setActive (boolean active)
boolean	usingPrimaryClock ()
void	setUsingPrimaryClock (boolean usePrimaryClock)
boolean	channelIsMasked (int ichannel)
void	maskChannel (int ichannel)
byte	getGroupId ()
	Group ID This is used to indicate which slave DSP will receive the module's data (if group based distribution is set), and also to allow different module groups to be triggered independently (for cross-talk studies).
void	setGroupId (byte param)
String	getClassName ()
void	write (OStream s, ObjectManager o) throws java.io.IOException
Static Public Member Functions
Streamable	read (IStream s, ObjectManager o) throws java.io.IOException
Private Attributes
ABCDModule	data
ChipConfiguration[]	chips = new ChipConfiguration[Parameters.nChipModule]

---

Detailed Description

Represents the configuration of a module.

Just a placeholder for now, but will probably be an interface to ABCDModule. It is worth noting that this class and its components define access to the data in terms of the physical setting e.g. DAC settings. If a user wants to think of a variable in terms of a higher level quantity, such as charge, mV etc then he should use an appropriate strategy for performing the conversion. This is motivated by the realisation that typically DAC step sizes are only approximate so expressing the setting in terms of e.g. mV is just as meaningless as expressing it in terms of DAC steps. However, we have decided to stick with functions in terms of nominal values for now.

Author:

Matthew Palmer

Definition at line 16 of file ModuleConfiguration.java.

---

Member Function Documentation

byte SctData.ModuleConfiguration.getGroupId (   )

Group ID This is used to indicate which slave DSP will receive the module's data (if group based distribution is set), and also to allow different module groups to be triggered independently (for cross-talk studies). valid range: [0,3] Definition at line 91 of file ModuleConfiguration.java. References sctConf.ABCDModule.groupId.

---

The documentation for this class was generated from the following file:

• ModuleConfiguration.java

---