1 / 3

Opera @ ETH

Opera @ ETH . Ongoing activities. Fixing Geant 4 MC Crash when producing more than 300 events in one run -> solved Crash when producing more than 700 events in one run -> Memory Leak in Geant4 processing, still searching for it Computation Time behaves „weird“

alban
Download Presentation

Opera @ ETH

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. Opera @ ETH

  2. Ongoing activities • Fixing Geant 4 MC • Crash when producing more than 300 events in one run -> solved • Crash when producing more than 700 events in one run -> Memory Leak in Geant4 processing, still searching for it • Computation Time behaves „weird“ • Some generated events of the beamfile are skipped and not used in the MC • to get 700 events, the beamfile is read till event 726

  3. What I plan to do next • Geant4 MC with charm-beamfiles • produced by the adapted NEG (Nomad Event Generator), compare later with NUX • Investigate the kinematics to produce a scheme for the discrimantion of the charm decay channels in the analysis • Work with Claudia (ETH) to combine MC for brick and full detector • Wait for real data

More Related