Questions

How much should modules know?

• Should modules know about run state (and variations depending on different run types)?
• Should modules (and CpChips?) know their phi,eta address? (Implied by present suggestions for completely general eta and phi dependent trigger thresholds)
• Should they use some global mapping service?
• My answers: no, yes, not sure

Parts, PartManager, etc

• Should modules hard code creation of their subcomponents in their constructors or read them from parts files?
• How do we cope with modules which have variable subcomponents eg different pluggable daughtercards?
• How do we cope with modules which have very different FPGA loads (eg debug version of CpChip code). Separate classes with different sets of methods or single more complicated class?
• My feelings: probably a bit of mix and match depending on each module. Some variations can be specified in the database, others may be better with separate classes.

Granularity

• Do we need access or detailed control of individual subcomponents of modules? (Eg change BCmux mode on a subset of channels). Or are global modes enough?