Reading runs 6715--6729 with MAUS is not possible without two modifications:

1. A "hack" to the unpacker. Instructions from Yordan:

a. Open the file
/third_party/build/unpacking-mice/src/MDprocessManager.cpp
and edit the line 253
from     if (MDequipMap::GetName(GetEquipmentType())!="VRB") {
to          if (MDequipMap::GetName(GetEquipmentType())!="VRB" && MDequipMap::GetName(GetEquipmentType())!="VLSBMaster") {

b. rebuild the unpacking:
source env.sh
cd /third_party/build/unpacking-mice/build/
cmake  -DCMAKE_INSTALL_PREFIX=${MAUS_ROOT_DIR}/third_party/install -DSTEPIV_DATA=1 ../
make
make install 

2. Changing TOF_trigger_station = "tof1" to TOF_trigger_station = "tof0" in $MAUS_ROOT_DIR$/src/common_py/ConfigurationDefaults.py (line 535)

Doing the above has worked with MAUS version 1.0.

As there is no valid calibration for TOF0 during these runs, space point reconstruction is extremely poor. Instead, I have stripped off the horizontal and vertical slab hits into a separate root file (archive attached to this entry). Assumptions used when converting slab numbers to (x, y) co-ordinates are also attached.

First, a naive look at the data.

The attached plots show histograms of the horizontal and vertical slab hits at TOF0 for each "task" (corresponding to a beam setting in the run plan). Vertical slab hits are converted into an x-coordinate, centred on the slab (see assumptions pdf in previous entry), and horizontal slab hits are converted into y-coordinates centred on the slabs.

At this point, I'm just counting every slab hit returned -- i.e. there's no accounting of multiple hits or requiring that a particle goes through both planes of the TOF.

There's no dramatic change in the distribution of slab hits, and the means vary by a few mm only.

The above histograms are then normalised to the same number of entries as task 5.1

Next, try and match up horizontal and vertical slab hits into pixels (without having a TOF calibration, I see no other way of doing this than by brute force...)

Analysis code is attached (though I apologise for its inelegance, I've not attempted to tidy it.. it is what it is).

A 'pixel' is made if and only if there is one horizontal and one vertical slab hit for a particle. All other slab hits are ignored. This reduces the number of "hits" at TOF0 to about 70% of what they were without this cut (for the reference beam).

The attached plots show, for each task:

(top, left): 2D pixel profile at TOF0
(top, middle): Projection of 2D profile onto the x-axis (equivalent to vertical slab hits)
(top, right): Projection of 2D profile onto the y-axis (equivalent to horizontal slab hits)
(bottom, middle): Mean value of y at each x
(bottom, right): Mean value of x at each y.

(ran out of allowable files to attach to the previous entry)

Also attached is the x and y profiles for 'pixel-worthy' hits, normalised to the same number of entries as task 5.1.

I think this is closed?