1 / 8

MC discussion

Discover the necessary samples and how to locate them for protoDUNE analysis in the DUNE project. Explore the provided links and utilize the job scheduling system.

yfarmer
Download Presentation

MC discussion

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. MC discussion Heidi Schellman, Oregon State University

  2. MC for protoDUNE analysis • What samples are needed and how to find them • https://wiki.dunescience.org/wiki/Production_and_Processing • https://wiki.dunescience.org/wiki/Useful_Production_Links • Requests are in servicenow • https://fermi.service-now.com/nav_to.do?uri=%2Fsys_report_template.do%3Fjvar_report_id%3Dd6ee1b9bdb9203c03aa6fd0e0f96190c%26jvar_selected_tab%3DmyReports%26jvar_list_order_by%3D%26jvar_list_sort_direction%3D%26sysparm_reportquery%3D%26jvar_search_created_by%3D%26jvar_search_table%3D%26jvar_search_report_sys_id%3D%26jvar_report_home_query%3D

  3. Specifying jobs • Need code version • Fcl files • Beam input files • Gets quite complex quite quickly as you have n beam settings and different fcl’s for detector configs. • In the end you can find the output you want by looking for sam metadata:

  4. Jobs use POMS • Can set up a config file that specified # of events, fcl files, versions … • Jobs can have multiple steps! • POMS can then keep track of success and failure, do resubmissions with more memory or time … • Getting a lot easier to set up and will become available for “users” to use for things like tuple creation.

  5. Info you can use to find outputs beam.momentum: -1.0 beam.polarity: -1 DUNE.campaign: MCC11 DUNE.production_status: final DUNE_MC.beam_energy: -1.0 DUNE_MC.detector_type: protoDUNE SP DUNE_MC.electron_lifetime: 3ms DUNE_MC.liquid_flow: no DUNE_MC.space_charge: no DUNE_MC.with_cosmics: 1 MC.liquid_flow: no << duplicate information? MC.space_charge: no MC.with_cosmics: 1                      Runs: 1.0000 (physics) << this should be protoDUNE-sp

  6. finding • samweb list-files "DUNE_MC.detector_type 'protoDUNE SP' and data_tier full-reconstructed and beam.momentum=1" –summary • Is an example but would likely need some other qualifiers

  7. Needs – people to help • Once configs are set up, jobs do need people to keep them going and the current production team is very swamped • Experts can help set up but you don’t have to be Linus Torvalds to keep em going. You can help and impress your friends with the thousands of cores worldwide that are doing your bidding. • Although expert help with scripting and improving the system would also be very welcome. • Can job-sitting count as shifts for the experiment (1 week = 1 shift?)

  8. Issues • Metadata and tracking look like they may need some work • Add the request-id to the metadata so you can see how it is going.

More Related