Project

General

Profile

Support #1833

Run 7469 extracted data file

Added by Blackmore, Victoria over 6 years ago. Updated over 5 years ago.

Status:
Open
Priority:
Normal
Assignee:
Start date:
16 March 2016
Due date:
% Done:

0%

Estimated time:

Description

Data extracted from the official MAUS 2.0 reconstruction of run 7469. This file contains a TTree with the following branches:

TOF0_x: x position at TOF0 using PMT times (i.e. 'Rayner' method)
TOF0_y: y position at TOF0 using PMT times
TOF0_z: z position at TOF0 (from survey)
TOF0_hitTime: Time particle crossed TOF0
TOF0_px: x momentum at TOF0 using Rayner's reconstruction
TOF0_py: y momentum at TOF0 using Rayner's reconstruction
TOF0_pz: z momentum at TOF0 using Rayner's reconstruction
TOF0_p: total momentum at TOF0 using Rayner's reconstruction
TOF0_xPrime: x' angle at TOF0 using Rayner's reconstruction
TOF0_yPrime: y' angle at TOF0 using Rayner's reconstruction
TOF0_xPixel: x position according to the pixel hit at TOF0
TOF0_yPixel: y position according to the pixel hit at TOF0
TOF0_hSlab_tMinus: Time recorded by PMT on horizontal slab hit positioned at -ve x
TOF0_hSlab_tPlus: Time recorded by PMT on horizontal slab hit positioned at +ve x
TOF0_vSlab_tMinus: Time recorded by PMT on vertical slab hit positioned at -ve x
TOF0_vSlab_tPlus: Time recorded by PMT on vertical slab hit positioned at +ve x
TOF0_hSlab: Horizontal slab number hit
TOF0_vSlab: Vertical slab number hit
TOF1_x: x position at TOF1 using PMT times (i.e. 'Rayner' method)
TOF1_y: y position at TOF1 using PMT times
TOF1_z: z position at TOF1 (from survey)
TOF1_hitTime: Time particle crossed TOF1
TOF1_px: x momentum at TOF1 using Rayner's reconstruction
TOF1_py: y momentum at TOF1 using Rayner's reconstruction
TOF1_pz: z momentum at TOF1 using Rayner's reconstruction
TOF1_p: total momentum at TOF1 using Rayner's reconstruction
TOF1_xPrime: x' angle at TOF1 using Rayner's reconstruction
TOF1_yPrime: y' angle at TOF1 using Rayner's reconstruction
TOF1_xPixel: x position according to the pixel hit at TOF1
TOF1_yPixel: y position according to the pixel hit at TOF1
TOF1_hSlab_tMinus: Time recorded by PMT on horizontal slab hit positioned at -ve x
TOF1_hSlab_tPlus: Time recorded by PMT on horizontal slab hit positioned at +ve x
TOF1_vSlab_tMinus: Time recorded by PMT on vertical slab hit positioned at -ve x
TOF1_vSlab_tPlus: Time recorded by PMT on vertical slab hit positioned at +ve x
TOF1_hSlab: Horizontal slab number hit
TOF1_vSlab: Vertical slab number hit
TKU_s1_x: x position at station 1 of the upstream tracker (from scifi track)
TKU_s1_y: y position at station 1 of the upstream tracker (from scifi track)
TKU_s1_z: z position at station 1 of the upstream tracker (from scifi track)
TKU_s1_px: x momentum at station 1 of the upstream tracker (from scifi track)
TKU_s1_py: y momentum at station 1 of the upstream tracker (from scifi track)
TKU_s1_pz: z momentum at station 1 of the upstream tracker (from scifi track)
TKU_s1_p: total momentum at station 1 of the upstream tracker (from scifi track)
(and similar for stations 2, 3, 4, 5 as TKU_s2_*, TKU_s3_*, TKU_s4_*, TKU_s5*)
TKU_PValue: P value of track (from scifi track)
TKU_chiSquare: Chi square value of track (from scifi track)
TKU_pattRec_r: Radius of circle from helical pattern recognition
TKU_pattRec_dipAngle: Angle of helix from helical pattern recognition
TKU_pattRec_x0: x position of centre of circle from helical pattern recognition (in local co-ordinates)
TKU_pattRec_y0: y position of centre of circle from helical pattern recognition (in local co-ordinates)
TKU_good: A variable I meant to remove, same as 'cut_TKU_hitAllStations'
cut_TOF0_goodPMTPosition: if 1, this particle passed through a calibrated area of TOF0
cut_TOF1_goodPMTPosition: if 1, this particle passed through a calibrated area of TOF1
cut_goodRaynerReconstruction: if 1, the Rayner reconstruction method converged for this particle
cut_TKU_hitStation1: if 1, this particle hit station 1 of the upstream tracker
cut_TKU_hitStation2: if 1, this particle hit station 2 of the upstream tracker
cut_TKU_hitStation3: if 1, this particle hit station 3 of the upstream tracker
cut_TKU_hitStation4: if 1, this particle hit station 4 of the upstream tracker
cut_TimeOfFlight: if 1, this particle has a time of flight between 26.5 and 40ns
cut_hit_all_detectors: if 1, this particle hit TOF0, TOF1 and all 5 stations of the upstream tracker
cut_TOF0_singleHit: if 1, there was one and only one spacepoint in TOF0
cut_TOF1_singleHit: if 1, there was one and only one spacepoint in TOF1
cut_TKU_singleTrack: if 1, there was one and only one track in the upstream tracker
cut_TKU_PValue: if 1, the P-value of the track was >= 0.01
cut_allPassed: if 1, all cuts above are also 1.

Things to be aware of:
1. If there are multiple spacepoints/tracks in TOF0/TOF1/TKU, only the first is recorded in this root file
2. So that all of the branches line up, empty variables are filled with TMath::Infinity() (or TMath.Infinity() for pyROOT). For example: A particle hits TOF0 and TOF1, but does not make it to the tracker.. TOF0_x contains a number, TOF1_x contains a number, but TKU_{station}_x contains TMath::Infinity. Not screening these out might cause some oddness in histogram stats... The attached example script shows how you can screen them.

---> Attached file: data_plots.zip, contains histograms of all entries that pass/fail a selection of these cuts. For simplicity, I've numbered them as "cuts 0 -- 14". The cuts are:

cut 0: Fill into histogram, regardless of whether it passes any cuts
cut 1: Fill histogram if PMT-timed position at TOF0 is OK
cut 2: Fill histogram if PMT-timed position at TOF1 is OK
cut 3: Fill histogram if Rayner Reconstruction at TOFs is OK
cut 4: Fill histogram if time-of-flight is OK
cut 5: Fill histogram if all 5 tracker planes were hit
cut 6: Fill histogram if all detectors hit
cut 7: Fill histogram if there was only one spacepoint at TOF0
cut 8: Fill histogram if there was only one spacepoint at TOF1
cut 9: Fill histogram if there was only one track in TKU
cut 10: Fill histogram if cut1 && cut2 && cut3 && cut4
cut 11: Fill histogram if cut10 && cut7 && cut8
cut 12: Fill histogram if cut11 && cut6 && cut9
cut 13: Fill if cut12 && Pvalue of track > 0.01
cut 14: Fill if all cuts are passed

---> The attached file 'run7417.dat' is the calibration file needed to produce positions at TOF0 and TOF1 using the PMT times. If a new version of MAUS changes the TOF calibrations, this file will need to be reproduced.


Files

run7417.dat (1.19 KB) run7417.dat Calibration file used to calculate (x, y) positions at TOF0 and TOF1 using PMT times Blackmore, Victoria, 16 March 2016 17:04
make_emittance_plot.py (7.93 KB) make_emittance_plot.py Python script used to create 'emittance_across_tracker_10MeV_slices.pdf' Blackmore, Victoria, 17 March 2016 13:26
emittance_across_tracker_10MeV_slices.pdf (17.8 KB) emittance_across_tracker_10MeV_slices.pdf Blackmore, Victoria, 17 March 2016 13:26
MC_cut_results.zip (2.48 MB) MC_cut_results.zip Blackmore, Victoria, 26 March 2016 10:04
load_cuts.py (463 Bytes) load_cuts.py Rogers, Chris, 29 March 2016 11:09
cut_results.zip (2.36 MB) cut_results.zip Blackmore, Victoria, 15 June 2016 16:12
time_of_flight_and_tracker_momentum.pdf (17.1 KB) time_of_flight_and_tracker_momentum.pdf Blackmore, Victoria, 16 June 2016 16:34
tracker-at-tof1_geometry-160_M2.5.0_v1.csv (4.45 MB) tracker-at-tof1_geometry-160_M2.5.0_v1.csv Rogers, Chris, 13 July 2016 07:44
run7469_extracted_data__MAUS2pt5_b.root (31.5 MB) run7469_extracted_data__MAUS2pt5_b.root Blackmore, Victoria, 22 July 2016 22:49
data_cut_comparisons.zip (5.78 MB) data_cut_comparisons.zip Blackmore, Victoria, 27 July 2016 21:09
mc_cut_comparisons.zip (5.74 MB) mc_cut_comparisons.zip Blackmore, Victoria, 27 July 2016 21:25
run7417_calibration_file_MC.txt (1.14 KB) run7417_calibration_file_MC.txt Blackmore, Victoria, 27 July 2016 21:25
mc_3mm200_07469_MAUS2pt5_extracted_data_c__withMCTOFCalib.root (80.7 MB) mc_3mm200_07469_MAUS2pt5_extracted_data_c__withMCTOFCalib.root Blackmore, Victoria, 27 July 2016 21:25
tracker-at-tof1_geometry-160_M2.5.0_v2.csv (17.8 MB) tracker-at-tof1_geometry-160_M2.5.0_v2.csv Rogers, Chris, 03 August 2016 10:49
MC_tracker-at-tof1_geometry-160_M2.5.0_v1 (22 MB) MC_tracker-at-tof1_geometry-160_M2.5.0_v1 Rogers, Chris, 20 October 2016 14:07
8590_data_extrapolated_tracks.csv (18.9 MB) 8590_data_extrapolated_tracks.csv Rogers, Chris, 06 December 2016 15:26
8590_mc_extrapolated_tracks.csv (2.21 MB) 8590_mc_extrapolated_tracks.csv Rogers, Chris, 06 December 2016 16:01
mc_3mm200_07469_MAUS-v260_2_extrapolated_tracks.csv.gz (1.05 MB) mc_3mm200_07469_MAUS-v260_2_extrapolated_tracks.csv.gz Rogers, Chris, 06 January 2017 16:49
plots_mc_3mm200_07469_MAUS-v260_2_mc.tar.gz (1.85 MB) plots_mc_3mm200_07469_MAUS-v260_2_mc.tar.gz Rogers, Chris, 06 January 2017 16:49
mc_3mm200_07469_MAUS-v284_2_extrapolated_tracks.csv.gz (8.64 MB) mc_3mm200_07469_MAUS-v284_2_extrapolated_tracks.csv.gz Rogers, Chris, 19 April 2017 10:13
7469_reco_extrapolated_tracks.csv.gz (7.9 MB) 7469_reco_extrapolated_tracks.csv.gz Rogers, Chris, 02 May 2017 10:21
#1

Updated by Blackmore, Victoria over 6 years ago

Uploading a new reprocessing from MAUS 2.1.

Also adding a script and pdf plot of the emittance across the tracker in 10MeV slices -- particles are randomly assigned to 'station 1' or 'station 5', then emittance is calculated and plotted as a function of pz. Particles in this sample are equivalent to the "cut14" passed samples.

(No corrections or mean-position subtraction is done, the emittance here is just the 4th root of the determinant of the covariance matrix. Vertical error bars are statistical (emittance/sqrt(N)) and horizontal error bars are the bin width)

#2

Updated by Blackmore, Victoria over 6 years ago

https://github.com/victoriablackmore/Extract-MAUS-data is the code used to extract this data file (and also contains the python script that runs over it and makes the pass/fail cut plots)

#3

Updated by Blackmore, Victoria over 6 years ago

Attaching the extracted reconstructed MC, going through the same program (linked from GitHub), and the pass/failed cuts plots

There's a new variable in this root file (cut_tof1_tku_momentum) that attempts to define a region on a plot of momentum at TKU vs momentum at TOF1. However, this cut does not make its way into the overall 'cut_allPassed' variable. The variable is there to look at, but it's not yet used (nor does it appear in the many pass/fail plots).

The distributions in the MC still look odd in the tracker (not as odd as before, but still odd)

#4

Updated by Rogers, Chris over 6 years ago

Hi Victoria, could you add spill, mc event number (for mc) and recon event number to the root file? I would like to relate the cut flags back to the original MAUS root file? Cheers!

#5

Updated by Blackmore, Victoria over 6 years ago

  • File run7469_extracted_data__MAUS2pt1b.root added
  • File run7469_extracted_data__MAUS2pt1b.root added

Sure. (There's no 'truth' MC here, just the reconstructed MC, for the record)

The spill number comes from the MAUS spill objects GetSpillNumber(), but the reconstructed event number comes from counting the loops over the reconstructed events object (Adam told me a while ago not to trust the event number function, and instead to just use the loop counter -- I don't know if that's still true, but it's what I'm still doing)

The spill number is in the branch 'SpillNumber', and the reconstructed event number is in the branch 'ReconstructedEventNumber'

(The git repository should be up to date -- so if you see something silly you can track it down)

#6

Updated by Rogers, Chris over 6 years ago

Thanks. By the way, where does the MC data come from? Do you have a URL for it? I presume the real data is from reco.mice.rl.ac.uk

#7

Updated by Drielsma, Fran├žois over 6 years ago

Hello Chris,

The file is located at http://reco.mice.rl.ac.uk/MAUS-v2.1.0/MC/mc_3mm200_07469_3.root.

It was produced from 100 G4BL chunks after the multiple corrections mentioned in the chain of emails:
  • Fix output position of G4BL (-99.92 mm in x)
  • Fix position of the quad fields (moved ~500 mm upstream)
  • Fix dimensions of the quad fields (0.3309 m half length)

I have since unveiled yet another problem that the mirrors in the CKOV are defined as regular PS with a density of 1.06 but are in fact a foam with density 0.12... This causes a 10 MeV/c offset in the MC. Ryan is aware and probably has corrected it by now. We still, however, have an additional offset of 10 MeV/c at TOF1 which seems to originate upstream of TOF0 for a currently unknown reason, I am digging...

#8

Updated by Rogers, Chris over 6 years ago

Hum, I tried loading event and spill number as in attached file and get output

Loading cuts ROOT file blackmore_data/run7469_extracted_data__MAUS2pt1b.root
0 0 -2.18275327939e-60 0.0
1 1 -0.000114954425953 4.94065645841e-324
2 1 -0.000114954425953 9.88131291682e-324
3 1 -2.18275327939e-60 1.48219693752e-323
4 1 -3.29014704019e+110 1.97626258336e-323
5 1 -1.30120806415e+197 2.47032822921e-323
6 1 -5.38012113181e+68 2.96439387505e-323
7 1 -0.000114954425953 3.45845952089e-323
8 1 -0.000114954425953 3.95252516673e-323
9 1 -0.000114954425953 4.44659081257e-323
10 1 -2.18275327939e-60 4.94065645841e-323
11 0 2.95821624332e+18 5.43472210425e-323

The first column is entry number, second column is cut_allData which looks okay, third and fourth column are spill/event number which look messed up. Probably I am doing something silly...

#9

Updated by Blackmore, Victoria over 6 years ago

  • File run7469_extracted_data__MAUS2pt1c.root added

Nope, I just assigned ints as doubles when declaring the spill and event number branches (who'd have thought it'd go THAT crazy... silly mistake nonetheless.)

Here's the fixed one, which works fine with your script. MC one will be along shortly.

#10

Updated by Blackmore, Victoria over 6 years ago

  • File deleted (run7469_extracted_data__MAUS2pt1b.root)
#11

Updated by Blackmore, Victoria over 6 years ago

  • File deleted (run7469_extracted_data__MAUS2pt1b.root)
#12

Updated by Blackmore, Victoria over 6 years ago

  • File mc_3mm200_07469_3_extracted_data_c.root added

Here's the MC with the fixed spill & event number branches. I've also removed the old root files, so we'll hopefully not get confused.

#13

Updated by Blackmore, Victoria over 6 years ago

  • File run7469_extracted_data__MAUS2pt1d.root added

Adds new branches for:

- Pulls at upstream tracker stations: TKU_s1_pull, TKU_s2_pull, TKU_s3_pull, TKU_s4_pull, TKU_s5_pull
- Errors on values reported by scifi track point: TKU_s1_x_error, TKU_s1_y_error, TKU_s1_px_error, TKU_s1_py_error, TKU_s1_kappa_error (and similar for stations 2--5 ). The branches for TKU_s*_kappa_error may be replaced with an error on Pz in the future, but right now just returning what the track point tells me.

No changes to the cuts, so no new pass/fail cut plots.

#14

Updated by Blackmore, Victoria over 6 years ago

  • File run7469_extracted_data__MAUS2pt1f.root added

Updating data file with correct electron time-of-flight peak information

(When I added the tof-tracker momentum cut, Scott's suggested electron TOF was 25.95ns, whereas it's more like 25.48 -- I used Scott's TOF when starting to implement his cuts, but should have stuck with the 'real' value -- this restores the real value)

#15

Updated by Blackmore, Victoria over 6 years ago

  • File mc_3mm200_07469_4_extracted_data_a.root added
  • File cut_output_mc_3mm200_4_exctracted_data_a.zip added

Adding latest MC after running it through this program along with its pass/fail cut plots.

There's something odd about the behaviour at TOF0 in the horizontal which is throwing off the Rayner reconstruction (compare x pixel positions at TOF0 to 'x' according to the PMT times). The distribution becomes very offset, despite using the same calibration files. TOF0 y and TOF1 x and y look believable. (But without believing TOF0 xPixel --> x, the rest of the Rayner reconstruction isn't believable)

--> Any thoughts, Durga?

#16

Updated by Blackmore, Victoria over 6 years ago

Updated github repository: https://github.com/victoriablackmore/Extract-MAUS-data

-- Now includes Scott's muon mass calculation cut in 'cut_allPassed'. (Though I've corrected the equation to (p_track + p_correction)/(beta*gamma))
-- Simplified cuts for whether tracks hit 1--5 tracker stations, using pattern recognitions get_num_points().
-- Removed some now redundant cut variables

-- cut_allPassed now actually includes passing all cuts. This is true if and only if we have a good convergence on the Mark Rayner TOF reconstruction, have a muon-compatible time of flight, hit TOF0, TOF1 & 5 stations of TKU, have only one hit in TOF0, TOF1 and TKU, have a Pvalue > 0.01 and a mass between 90 & 120MeV.

-- run7469_extracted_data__MAUS2pt3pt1_b.root is the latest extracted root file from MAUS v2.3.1 (2.4 to come soon once I've done updating..)
-- cut_results.zip is an updated plotting script and the pass/fail plots for each individual cut and the cumulative 'cut_allPassed'. Note that since I've removed some redundant cuts, there's now fewer of them. Cuts are:

_noCut: Fill into histogram, regardless of whether it passes any cuts
_cut1: Fill histogram if PMT-timed position at TOF0 is OK
_cut2: Fill histogram if PMT-timed position at TOF1 is OK
_cut3: Fill histogram if Rayner Reconstruction at TOFs is OK
_cut4: Fill histogram if time-of-flight is OK
_cut5: Fill histogram if all 5 tracker planes were hit
_cut6: Fill histogram if all detectors hit
_cut7: Fill histogram if there was only one spacepoint at TOF0
_cut8: Fill histogram if there was only one spacepoint at TOF1
_cut9: Fill histogram if there was only one track in TKU
_cut10: Fill histogram if particle mass is OK
_cut11: Fill histogram if Pvalue is OK
_cut12: Fill if all cuts are passed

(a mean calculated muon mass for cut_allPassed of 105.4 isn't too shabby...)

#17

Updated by Blackmore, Victoria over 6 years ago

I've tightened up the mass cut to accepting between 99 and 112MeV, which cleans up the tof-tracker momentum plot quite nicely (also attached).

#18

Updated by Blackmore, Victoria over 6 years ago

  • File run7469_extracted_data__MAUS2pt5_a.root added

A new extracted data file for MAUS 2.5. Plots for pass/fail cuts coming shortly(ish).

#19

Updated by Rogers, Chris over 6 years ago

Attached is the tracker tracks extrapolated to TOF1. The file name holds version information i.e. geometry #160, MAUS v2.5.0 for recon, and version 1 (in case we find a bug and I need to do an update)

#20

Updated by Blackmore, Victoria over 6 years ago

  • File mc_3mm200_07469_MAUS2pt5_extracted_data_a.root added

Attaching MC root file for MAUS v2.5

#21

Updated by Blackmore, Victoria over 6 years ago

  • File deleted (run7469_extracted_data.root)
#22

Updated by Blackmore, Victoria over 6 years ago

  • File deleted (data_plots.zip)
#23

Updated by Blackmore, Victoria over 6 years ago

  • File deleted (readData.py)
#24

Updated by Blackmore, Victoria over 6 years ago

  • File deleted (data_plots_MAUS2pt1.zip)
#25

Updated by Blackmore, Victoria over 6 years ago

  • File deleted (mc_3mm200_07469_3_extracted_data.root)
#26

Updated by Blackmore, Victoria over 6 years ago

  • File deleted (run7469_extracted_data__MAUS2pt1c.root)
#27

Updated by Blackmore, Victoria over 6 years ago

  • File deleted (mc_3mm200_07469_3_extracted_data_c.root)
#28

Updated by Blackmore, Victoria over 6 years ago

  • File deleted (run7469_extracted_data__MAUS2pt1d.root)
#29

Updated by Blackmore, Victoria over 6 years ago

  • File deleted (run7469_extracted_data__MAUS2pt1f.root)
#30

Updated by Blackmore, Victoria over 6 years ago

  • File deleted (mc_3mm200_07469_4_extracted_data_a.root)
#31

Updated by Blackmore, Victoria over 6 years ago

  • File deleted (cut_output_mc_3mm200_4_exctracted_data_a.zip)
#32

Updated by Blackmore, Victoria over 6 years ago

  • File deleted (run7469_extracted_data__MAUS2pt3pt1_b.root)
#33

Updated by Blackmore, Victoria over 6 years ago

  • File deleted (run7469_extracted_data__MAUS2pt3pt1_c_tighterMassCut.root)
#34

Updated by Blackmore, Victoria over 6 years ago

Updating extracted data file:

  • cut_allPassed has been modified to remove the mass cut (added in the last update) and replace it with a cut on the momentum lost between TOF1 and TKU.
    • removed: cut_muon_mass branch
    • added: cut_momentum_loss branch
    • modified: cut_allPassed now depends on cut_momentum_loss and not cut_muon_mass

MC file will follow shortly.

#35

Updated by Blackmore, Victoria over 6 years ago

  • File deleted (run7469_extracted_data__MAUS2pt1.root)
#36

Updated by Blackmore, Victoria over 6 years ago

  • File deleted (run7469_extracted_data__MAUS2pt5_a.root)
#37

Updated by Blackmore, Victoria over 6 years ago

  • File deleted (mc_3mm200_07469_MAUS2pt5_extracted_data_a.root)
#38

Updated by Blackmore, Victoria over 6 years ago

Cut plots shown at CM45 for run 7469 data file: run7469_extracted_data__MAUS2pt5_b.root (zip file includes the .cpp used to create them)

#39

Updated by Blackmore, Victoria over 6 years ago

Updating with MC, using a MC calibration for the TOF positioning by PMT

  • run7417_calibration_file_MC.txt -- speed of light in scintillator + cable length corrections for MC (derived from run 7469, contrary to file name)
#40

Updated by Rogers, Chris over 6 years ago

Attached new version for tracker at tof1; now includes tracks extrapolated to the diffuser. The z position is in the listing (so you can see which track is where). Let me know if you need anything else.

#41

Updated by Rogers, Chris about 6 years ago

Attached extracted MC file; my routines may have gotten confused by the fact that all spill numbers are 1. I think this arises due to the way MC is stitched together from many reconstructions each with 1 spill...

#42

Updated by Rogers, Chris about 6 years ago

Victoria asked me to run the track extrapolation script for run 8590 real data; extrapolated data files attached. Victoria, I have made some quite significant changes to the bureaucracy in my script - so can you check that you are happy (and let me know if you are not). Thanks!

#43

Updated by Rogers, Chris about 6 years ago

Attached the extrapolation for 8590 mc. Note I only include the first 10 MC files in here, i.e. a glob like 000025/0000?/*_sim.root - I can run over all 1000 files or so, but grateful to hear back about whether the data is useful first!

#44

Updated by Rogers, Chris almost 6 years ago

Attached extrapolated tracks for the MC data set. I think the 7469 geometry is the right one to use here. I had a slightly modified set of z positions for diffuser and TOF, based on input from Victoria. All of my spill numbers are 1, as this is what is recorded in the originating file. I can force to increment the spill number or something if required.

#46

Updated by Rogers, Chris over 5 years ago

Extrapolated tracks file for 7469 data MAUSv2.8.4

#47

Updated by Rogers, Chris over 5 years ago

  • File 7469_reco_extrapolated_tracks.csv.gz added

For some reason it failed to upload. Let me try again...

#48

Updated by Rogers, Chris over 5 years ago

Last file got corrupted during upload. Let's try again.

#49

Updated by Rogers, Chris over 5 years ago

  • File deleted (7469_reco_extrapolated_tracks.csv.gz)

Also available in: Atom PDF