class AliMUONVDigit: public TObject

 dtor

 Whether we're equal to object.
 WARNING : only based on our identifiers (de,manu,channel,cathode), not our
 content (i.e. charge, status...)

 Compare two digits, trying to get as complete an order as possible.
 We sort by DE, then by charge, then by manu, etc...

 Build a single integer with id information

 Return detection element id part of the uniqueID

 Return manuChannel part of the uniqueID

 Return manuId part of the uniqueID

 Return the cathode part of the uniqueID

 Unpack uniqueID into 4 elements

 Return the name of this digit, composed of its id parts.

 Dump to screen.

 If opt=="tracks", info on tracks are printed too.

 The last part of the printout indicated the status of the digit :
 (S) means that digit is saturated
 (C) means that digit has been calibrated
 [fC] means that digit's charge is in femto-coulombs (fC)
 (U) means that digit is part of (has been used in) a cluster
 (+) is noise-only digit (added by the simulation)
 (X) has the IsConverted flag on (e.g. has been embedded)

 Advertise that we can be sorted in TCollections

 The detection element this digit belongs to

 The x-index of this digit (>=0)

 The y-index of this digit (>=0)

 Cathode number this digit is on (0 or 1)

 The charge of this digit, calibrated or not depending on IsCalibrated()

 Raw ADC value of this digit

 The electronic card id this digit belongs to (manuId for tracker, localboardId for trigger)

 The channel within ManuId() this digit belongs to (manuChannel for tracker, localBoardChannel for trigger)

 Whether the ADC has saturated

 Set the saturation status

 Whether this (simulated) digit is purely noise

 Set the noiseOnly status

 Whether this (simulated) digit got corrected by chamber efficiency

 Set the efficiencyApplied status

 Whether this digit has been calibrated or not (see note 1 in AliMUONVDigit.cxx)

 Set the calibrated status (see note 1 in AliMUONVDigit.cxx)

 Whether this digit has charge in femto coulomb (see note 1 in AliMUONVDigit.cxx)

 Set the unit value (see note 1 in AliMUONVDigit.cxx)

 Whether or not this digit was obtained from a conversion (e.g. real to simulated)

 Whether this digit is used somewhere (typically in a cluster)

 Set the used status

 A word describing the status of the neighbours of this digit

 Set the statusMap

 Set the ADC value

 Set the ix and iy of this digit

 Set the charge of this digit

 Add a charge

 Merge this with other

 Whether this digit is a tracker digit (false if belongs to trigger)

 FIXME: how to get this information w/o hard-coding, yet being efficient ?
    Use one fFlags that must be set when creating the digit for instance ?

 Below are methods only relevant for MC digigts.
 Whether we implement MC methods.

 Hit number that contributed to this simulated digit

 Set the hit number

 Hit age

 Set hit age

 Number of tracks contributing to this digit

 Add a track (and its charge) to the list of tracks we handle

 Return the i-th track number

 Return the i-th track charge

 Patch track with a mask

 Return the localBoardNumber from the uniqueID

 Return the localBoardChannel from the uniqueID