G4NuMI setup Decoder ring

A normal output for the G4NuMI hadron/muon monitor data Ntuple has the following form "nuNtuple_18000_bbbb_E_NoKill.root"
    The number 18000 corresponds to the monoenergetic muon bean used, the series of b's or B's correspond to the amount of steel in the Absorber Core gaps, and the letter at the end should be referenced against the table below and encompasses the rock constituents. The NoKill ending moniker denotes that the run had the G4NuMI particle kill energy set to the lowest possible value. The steel used for the BluBlocks and Core blocks had probably WRONG density of 7.75 g/cm3. The percentage by weight of the BluBlocks in the G4NuMI was 0.1 C / 0.1 Si / 0.4 Mn / 98.2 Fe / 1.0 Ni / 0.2 Cu and for the Core I used 1018 steel which is 0.2 C / 0.9 Mn / 98.9 Fe.
    All runs up to and including _J_ had a rockMat density of 2.53 g/cm3, DolomiteRock 2.79g/cm3 and Maquoketa Shale 2.79g/cm3. This meant that if the composition of a rock sample was 50% rockMat (Dolomite w/o water) and 50% Maquoketa Shale the density would be .5*2.53+.5*2.79 = 2.66g/cm3. But if the density of the rock sample was 2.80g/cm3 Geant4 scales the amount of Maquoketa Shale and rockMat by 2.80/2.66, which effectively increases the nuclear Z and increases energy loss. Also for the steel slabs wedged into the gaps were lined up with the downstream edge of the last steel Absorber Core block. This based on a photo in VMS from earlier installation. The last photo showing any aspect of the steel slabs in the gap have the plates lined up with the downstream edge of the BluBlocks. The G4NuMI geometry has now been changed to line up the downstream edges of the steel slabs with the downstream edge of the BluBlocks.