MICEmine: Issueshttps://micewww.pp.rl.ac.uk/https://micewww.pp.rl.ac.uk/favicon.ico?16074423572019-03-20T17:22:35ZMICEmine
Redmine Analysis - Feature #1985 (Open): MC Analysis to support MAUS paperhttps://micewww.pp.rl.ac.uk/issues/19852019-03-20T17:22:35ZRogers, Chris
<p>Durga asked via email for some a comparison of Reconstructed MC to MC truth to support the MAUS paper.</p> Analysis - Feature #1967 (Open): diffuser geometryhttps://micewww.pp.rl.ac.uk/issues/19672018-05-09T15:22:58ZRogers, Chris
<p>Update to diffuser geometry...</p> Analysis - Support #1904 (Closed): Example coil geometryhttps://micewww.pp.rl.ac.uk/issues/19042017-01-10T18:01:51ZRogers, Chris
<p>I attach an example single coil geometry. You can reproduce the bz on-axis plot by doing</p>
<pre>
tar -xzf 2017-01-10_example-maus.tar.gz
cd 2017-01-10_example-maus
source /path/to/maus/env.sh
python make_field_map.py --simulation_geometry_filename SingleCoil.dat
# view bfield_vs_z.png in your favourite image browser
</pre> Analysis - Support #1871 (Closed): Global fitting for energy losshttps://micewww.pp.rl.ac.uk/issues/18712016-09-13T17:48:26ZRogers, Chris
<p>Scott asked to have a look at my code for global track fitting for energy loss analysis (say, including TOF and tracker).</p>
<p>The branch is</p>
<p>bzr+ssh://bazaar.launchpad.net/~chris-rogers/maus/tracking_errors/</p>
<p>I attach a "driver script" that should "just work" (haha) to do a fit on the upstream region. We can have a phone chat about it maybe?</p> Analysis - Feature #1867 (Closed): 2016/03 Run settingshttps://micewww.pp.rl.ac.uk/issues/18672016-09-06T04:09:41ZRogers, Chris
<p>Run settings for 2016/03</p> Analysis - Bug #1848 (Closed): Descope Demohttps://micewww.pp.rl.ac.uk/issues/18482016-05-12T07:55:05ZRogers, Chris
<p>Descope Demonstration of Ionisation Cooling lattice</p> Analysis - Feature #1839 (Open): 4D KDE area calculationhttps://micewww.pp.rl.ac.uk/issues/18392016-04-14T04:01:01ZSnopok, Pavelsnopok@gmail.com
<p>Chris, here is the file containing two arrays: one for the US tracker reference plane, one for the DS tracker reference plane. To read it in:</p>
<p>=====<br />import numpy as np<br />data=np.load('KDE.npz')<br />u=data['USKDE']<br />d=data['DSKDE']
=====</p>
<p>The array itself has 6250000 rows (50x50x50x50 grid) and five columns: [x,y,px,py,density (predicted by KDE)]. I wonder if you could try your Delaunay triangulation algorithm on it. The upstream distribution should be convex, but not necessarily the downstream.</p> Analysis - Support #1833 (Open): Run 7469 extracted data filehttps://micewww.pp.rl.ac.uk/issues/18332016-03-16T17:04:02ZBlackmore, Victoriav.blackmore@imperial.ac.uk
<p>Data extracted from the official MAUS 2.0 reconstruction of run 7469. This file contains a TTree with the following branches:</p>
<pre><code>TOF0_x: x position at TOF0 using PMT times (i.e. 'Rayner' method)<br /> TOF0_y: y position at TOF0 using PMT times<br /> TOF0_z: z position at TOF0 (from survey)<br /> TOF0_hitTime: Time particle crossed TOF0<br /> TOF0_px: x momentum at TOF0 using Rayner's reconstruction<br /> TOF0_py: y momentum at TOF0 using Rayner's reconstruction<br /> TOF0_pz: z momentum at TOF0 using Rayner's reconstruction<br /> TOF0_p: total momentum at TOF0 using Rayner's reconstruction<br /> TOF0_xPrime: x' angle at TOF0 using Rayner's reconstruction<br /> TOF0_yPrime: y' angle at TOF0 using Rayner's reconstruction</code></pre>
<pre><code>TOF0_xPixel: x position according to the pixel hit at TOF0<br /> TOF0_yPixel: y position according to the pixel hit at TOF0<br /> TOF0_hSlab_tMinus: Time recorded by PMT on horizontal slab hit positioned at -ve x<br /> TOF0_hSlab_tPlus: Time recorded by PMT on horizontal slab hit positioned at +ve x<br /> TOF0_vSlab_tMinus: Time recorded by PMT on vertical slab hit positioned at -ve x<br /> TOF0_vSlab_tPlus: Time recorded by PMT on vertical slab hit positioned at +ve x<br /> TOF0_hSlab: Horizontal slab number hit<br /> TOF0_vSlab: Vertical slab number hit</code></pre>
<pre><code>TOF1_x: x position at TOF1 using PMT times (i.e. 'Rayner' method)<br /> TOF1_y: y position at TOF1 using PMT times<br /> TOF1_z: z position at TOF1 (from survey)<br /> TOF1_hitTime: Time particle crossed TOF1<br /> TOF1_px: x momentum at TOF1 using Rayner's reconstruction<br /> TOF1_py: y momentum at TOF1 using Rayner's reconstruction<br /> TOF1_pz: z momentum at TOF1 using Rayner's reconstruction<br /> TOF1_p: total momentum at TOF1 using Rayner's reconstruction<br /> TOF1_xPrime: x' angle at TOF1 using Rayner's reconstruction<br /> TOF1_yPrime: y' angle at TOF1 using Rayner's reconstruction</code></pre>
<pre><code>TOF1_xPixel: x position according to the pixel hit at TOF1<br /> TOF1_yPixel: y position according to the pixel hit at TOF1<br /> TOF1_hSlab_tMinus: Time recorded by PMT on horizontal slab hit positioned at -ve x<br /> TOF1_hSlab_tPlus: Time recorded by PMT on horizontal slab hit positioned at +ve x<br /> TOF1_vSlab_tMinus: Time recorded by PMT on vertical slab hit positioned at -ve x<br /> TOF1_vSlab_tPlus: Time recorded by PMT on vertical slab hit positioned at +ve x<br /> TOF1_hSlab: Horizontal slab number hit<br /> TOF1_vSlab: Vertical slab number hit</code></pre>
<pre><code>TKU_s1_x: x position at station 1 of the upstream tracker (from scifi track)<br /> TKU_s1_y: y position at station 1 of the upstream tracker (from scifi track)<br /> TKU_s1_z: z position at station 1 of the upstream tracker (from scifi track)<br /> TKU_s1_px: x momentum at station 1 of the upstream tracker (from scifi track)<br /> TKU_s1_py: y momentum at station 1 of the upstream tracker (from scifi track)<br /> TKU_s1_pz: z momentum at station 1 of the upstream tracker (from scifi track)<br /> TKU_s1_p: total momentum at station 1 of the upstream tracker (from scifi track)<br /> (and similar for stations 2, 3, 4, 5 as TKU_s2_*, TKU_s3_*, TKU_s4_*, TKU_s5*)</code></pre>
<pre><code>TKU_PValue: P value of track (from scifi track)<br /> TKU_chiSquare: Chi square value of track (from scifi track)<br /> TKU_pattRec_r: Radius of circle from helical pattern recognition<br /> TKU_pattRec_dipAngle: Angle of helix from helical pattern recognition<br /> TKU_pattRec_x0: x position of centre of circle from helical pattern recognition (in local co-ordinates)<br /> TKU_pattRec_y0: y position of centre of circle from helical pattern recognition (in local co-ordinates)</code></pre>
<pre><code>TKU_good: A variable I meant to remove, same as 'cut_TKU_hitAllStations'</code></pre>
<pre><code>cut_TOF0_goodPMTPosition: if 1, this particle passed through a calibrated area of TOF0<br /> cut_TOF1_goodPMTPosition: if 1, this particle passed through a calibrated area of TOF1<br /> cut_goodRaynerReconstruction: if 1, the Rayner reconstruction method converged for this particle<br /> cut_TKU_hitStation1: if 1, this particle hit station 1 of the upstream tracker<br /> cut_TKU_hitStation2: if 1, this particle hit station 2 of the upstream tracker<br /> cut_TKU_hitStation3: if 1, this particle hit station 3 of the upstream tracker<br /> cut_TKU_hitStation4: if 1, this particle hit station 4 of the upstream tracker<br /> cut_TimeOfFlight: if 1, this particle has a time of flight between 26.5 and 40ns<br /> cut_hit_all_detectors: if 1, this particle hit TOF0, TOF1 and all 5 stations of the upstream tracker<br /> cut_TOF0_singleHit: if 1, there was one and only one spacepoint in TOF0<br /> cut_TOF1_singleHit: if 1, there was one and only one spacepoint in TOF1<br /> cut_TKU_singleTrack: if 1, there was one and only one track in the upstream tracker<br /> cut_TKU_PValue: if 1, the P-value of the track was >= 0.01<br /> cut_allPassed: if 1, all cuts above are also 1.</code></pre>
<p>Things to be aware of:<br /> 1. If there are multiple spacepoints/tracks in TOF0/TOF1/TKU, only the first is recorded in this root file<br /> 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.</p>
<p>---> 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:</p>
<pre><code>cut 0: Fill into histogram, regardless of whether it passes any cuts<br /> cut 1: Fill histogram if PMT-timed position at TOF0 is OK<br /> cut 2: Fill histogram if PMT-timed position at TOF1 is OK<br /> cut 3: Fill histogram if Rayner Reconstruction at TOFs is OK<br /> cut 4: Fill histogram if time-of-flight is OK<br /> cut 5: Fill histogram if all 5 tracker planes were hit<br /> cut 6: Fill histogram if all detectors hit<br /> cut 7: Fill histogram if there was only one spacepoint at TOF0<br /> cut 8: Fill histogram if there was only one spacepoint at TOF1<br /> cut 9: Fill histogram if there was only one track in TKU<br /> cut 10: Fill histogram if cut1 && cut2 && cut3 && cut4<br /> cut 11: Fill histogram if cut10 && cut7 && cut8<br /> cut 12: Fill histogram if cut11 && cut6 && cut9<br /> cut 13: Fill if cut12 && Pvalue of track > 0.01<br /> cut 14: Fill if all cuts are passed</code></pre>
<p>---> 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.</p> Analysis - Bug #1808 (Closed): Optics review paperworkhttps://micewww.pp.rl.ac.uk/issues/18082016-01-08T12:14:31ZRogers, Chris
<p>Optics review paperwork</p> Analysis - Feature #1806 (Closed): Rate analysis based on 7469https://micewww.pp.rl.ac.uk/issues/18062016-01-05T14:24:04ZRogers, Chris
<p>Discussion of rate analysis based on run 7469</p> Analysis - Feature #1750 (Closed): Optics for SSD in the absence of M1https://micewww.pp.rl.ac.uk/issues/17502015-09-21T09:56:43ZRogers, ChrisAnalysis - Feature #1699 (Rejected): MICE at step ivhttps://micewww.pp.rl.ac.uk/issues/16992015-06-26T13:15:41ZRogers, Chris
<p>Paper that describes MICE as installed at step iv</p> Analysis - Feature #1637 (Closed): Physics shifter scripthttps://micewww.pp.rl.ac.uk/issues/16372015-03-09T11:54:48ZRogers, Chris
<p>Need to make a physics shifter script that:</p>
<ul>
<li>Takes as argument a set of run numbers</li>
<li>Downloads the runs</li>
<li>Executes some analysis of detector efficiencies, etc</li>
</ul> Analysis - Feature #1600 (Closed): Analytical form for transfer matrix in transverse coordinates,...https://micewww.pp.rl.ac.uk/issues/16002014-12-16T13:41:49ZRogers, Chris
<p>attached...</p> Analysis - Feature #1547 (Closed): MICE Step Pi in G4beamlinehttps://micewww.pp.rl.ac.uk/issues/15472014-08-22T07:00:32ZSnopok, Pavelsnopok@gmail.com
<p>Copied Step Pi deck parameters from MAUS into G4beamline. Ran 10000 particles @ betaT=333 mm, epsT=6 mm, z=-4050 mm. Magnetic field on axis looks reasonable, agrees with the field map calculated by Diktys Stratakis. However, betaT does not look right, figure attached.</p>