1 / 7

Development Steps (1 of 3)

Development Steps (1 of 3). Create prototype “MiceModule” code Done (Malcolm) Produce working TofRec code that can reconstruct up to the level of space points using digitised simulation: TofDigits from Monte Carlo Work in progress (Aron) TofDigits from Real Data Done (Aron)

jui
Télécharger la présentation

Development Steps (1 of 3)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Development Steps (1 of 3) • Create prototype “MiceModule” code Done(Malcolm) • Produce working TofRec code that can reconstruct up to the level of space points using digitised simulation: • TofDigits from Monte CarloWork in progress (Aron) • TofDigits from Real Data Done (Aron) • TofSlabHits from TofDigits Work in progress (Aron) • TofSpacePoints from TofSlabHits Work in progress (Aron) • Create data files area for calibration, decoding and modeling files Done (Malcolm) • Produce calibration code for SciFi Done (Malcolm) • Produce decoding code for SciFi Work in progress (Takashi) • Produce calibration files for SciFi Done (Malcolm) • Produce decoding files for SciFi Work in progress (Takashi) • Produce calibration code for TOF Work in Progress (Aron) • Produce decoding code for TOF Done (Aron) Malcolm Ellis - Software Meeting - 31st May 2006

  2. Development Steps (2 of 3) • Produce calibration files for TOF Work in Progress (Aron) • Produce decoding files for TOF Done (Aron) • Validate MiceModule code (in particular transformations and HepRep representation) (Lara) • Migrate to use of MiceModule in TOF Simulation Done (Malcolm) • Migrate to use of MiceModule in TOF Digitsiation (Aron) • Migrate to use of MiceModule in TOF Reconstruction (Aron) • Migrate to use of MiceModule in SciFi Digitisation (Malcolm) • Migrate to use of MiceModule in SciFi Simulation (Malcolm) • Migrate to use of MiceModule in SciFi Reconstruction (Malcolm) • Produce and validate MiceModule files for the KEK test beam setup Done • First version completed by Aron, Terry, Ben and Mike • Second version with sensitive detectors recently tagged Malcolm Ellis - Software Meeting - 31st May 2006

  3. Development Steps (3 of 3) • Final verification of MiceModule files (TBD) • Prepare Simulation of KEK test beam setup (TOF & SciFi) (Malcolm and Aron) • Test each stage of Reconstruction (hits, clusters, points, tracks, matching) with Simulation (Malcolm and Aron) • Test real data code in Reconstruction (unpacking, calibration, etc) (Malcolm and Aron) • Prepare analysis NTuples/Histograms (Malcolm and Aron) • Perform analysis of KEK test beam data (Malcolm and Aron) • Current tag: SensitiveDetectors_20060530 Malcolm Ellis - Software Meeting - 31st May 2006

  4. G4 Visualisation Malcolm Ellis - Software Meeting - 31st May 2006

  5. G4 Visualisation Malcolm Ellis - Software Meeting - 31st May 2006

  6. Sensitive Detectors • MiceModules can be used to define a sensitive detector, which is automatically built in the G4MICE Simulation: • PropertyString SensitiveDetector TOF • At the moment, only TOF implemented. SciFi will be next, then EmCal, etc, etc. • MICEDetectorConstruction now radically simplified c.f. RAL and KEK detector constructors (although currently no field maps nor RF!) • Code in DetModel only requires SD code as a minimum. • Also provide G4 code for more complicated geometry (e.g. SciFi fibres, LH2 absorbers, RF cavities). • Instantiation of Sensitive detector makes a link between the G4 physical volume and the corresponding MiceModule, so there is no need for decoding station/plane/slab numbers from the G4 volume name (see next page) Malcolm Ellis - Software Meeting - 31st May 2006

  7. TofSD • TofSD currently creates plausible looking hits (see below), however needs proper testing before moving onto the SciFi TofHit* hit = new TofHit; hit->SetStripNo( _module->propertyInt( "Slab" ) ); hit->SetPlaneNo( _module->propertyInt( "Plane" ) ); hit->SetStationNo( _module->propertyInt( "Station" ) ); ... _event->tofHits.push_back( hit ); • Sim.out output: 7 TofHits 0 1 -13 105.658 1e-06 -2.0123 1.22934 -10 0.225864 0.00386447 0.0056235 2961.12 2963.01 60 1 1 1 KekOctoberKekT1KekT1SciFi 0 1 1 -13 105.658 1e-06 -2.01226 1.2294 23 0.33601 0.00386447 0.0056235 2961.12 2963.01 83 2 1 1 KekOctoberKekR1KekR1SciFi 0 2 1 -13 105.658 1.61106 -16.2538 20.3344 8237 27.7532 -3.88422 6.11332 2895.83 2897.76 8297.04 4 1 8 KekOctoberKekTOFKekTOFHorizontalKekTOFSlab8KekTOFSlab8SciFi 0 3 1 -13 105.658 2.58205 -16.3 20.4058 8267 27.8534 4.7092 9.32669 2837.56 2839.55 8330.7 4 2 1 KekOctoberKekTOFKekTOFVerticalKekTOFSlab3KekTOFSlab1SciFi 0 4 1 -13 105.658 1.01176 -16.2913 20.4452 8280.66 27.899 4.73125 11.0165 2836.54 2838.54 8337.04 4 2 1 KekOctoberKekTOFKekTOFVerticalKekTOFSlab3KekTOFSlab1SciFi 0 5 1 -13 105.658 1e-06 -12.0378 30.3456 10830.8 36.4113 4.73125 11.0165 2836.54 2838.54 10885.9 6 1 1 KekOctoberD2 0 6 5 11 0.510999 1.00635 -16.2913 20.4452 8280.66 27.899 -5.52527 -0.741058 48.2201 48.544 6.40721 4 2 1 KekOctoberKekTOFKekTOFVerticalKekTOFSlab3KekTOFSlab1SciFi 1 Malcolm Ellis - Software Meeting - 31st May 2006

More Related