Fixed wrong mapping from sectors to board. It was
authorcholm <cholm@f7af4fe6-9843-0410-8265-dc069ae4e863>
Mon, 12 Jul 2010 13:30:05 +0000 (13:30 +0000)
committercholm <cholm@f7af4fe6-9843-0410-8265-dc069ae4e863>
Mon, 12 Jul 2010 13:30:05 +0000 (13:30 +0000)
commit9324dfea536ebaed8aeedf9a1731a145bed9c59a
tree3b1bb36c4ea5e6c13633aadf922c38ab488022b9
parent8cc1cb63dc13e6a1eca7a6cf4a7608df317b016d
Fixed wrong mapping from sectors to board.   It was

   Inners:  Sector  0-> 9  mapped to board 0x00
            Sector 10->19  mapped to board 0x10
   Outers:  Sectir  0->19  mapped to board 0x01
            Sector 20->39  mapped to board 0x11

The correct mapping is the opposite:

   Inners:  Sector  0-> 9  mapped to board 0x10
            Sector 10->19  mapped to board 0x00
   Outers:  Sectir  0->19  mapped to board 0x11
            Sector 20->39  mapped to board 0x01

Note, that this _only_ effected the QA histograms, since it's the
only place where the Sector2Board member function is called.   I found
this bug in our laborartory set-up.
FMD/AliFMDAltroMapping.cxx