1 / 15

GAE CMS Analysis (Example)

This workshop outline details the procedures for GAE analysis and ORCA job preparation and submission. It covers installation of required software, preparation of analysis code, job submission to the Grid Scheduler (Sphinx), and monitoring job progress. Participants will learn to describe jobs using Chimera DAX, manage dependencies, and utilize various job description languages. Key topics include using Sphinx for distributed job management, collecting results with ROOT visualization, and version control with CAVES.

jed
Télécharger la présentation

GAE CMS Analysis (Example)

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. GAE CMS Analysis(Example) Michael Thomas (thomas@hep.caltech.edu) (on behalf of the GAE group) Korea Workshop May 2005

  2. Outline Prepare Code Collect Results GAE Analysis Submit Monitor Korea Workshop May 2005

  3. Prepare ORCA Job • Install xcmsi to prepare for local CMS software installation • http://cmsdoc.cern.ch/cms/oo/repos_standalone/download/download.sh • Install ORCA using xcmsi • ./xcmsi.pl • Select packages to install • Write and compile the ORCA application • cd to ORCA workspace • Look at ExRunEvent.cpp in ORCA/src/Workspace as an example • More info on using ORCA: http://cmsdoc.cern.ch/orca/ Korea Workshop May 2005

  4. Submit Job • Describe job in Job Description Language (Chimera DAX) • Submit job to Grid Scheduler (Sphinx) • Sphinx submits job and subtasks to remote sites • Use Sphinx job id to monitor job Korea Workshop May 2005

  5. Describe Job in JDL • Chimera DAX: http://www.griphyn.org/chimera/dax-1.6.xsd • Other Job Description Languages being investigated • JDL contains • Input and output logical filenames • Tasks (commands) to be executed • Dependency between Tasks represented as a DAG • Pointer to application data (ORCA shared libraries, .orcarc) Korea Workshop May 2005

  6. Submit Job to Scheduler • Use client tool to submit to Sphinx • Web Service interface provides flexibility for clients • Sphinx client application • CRAB • Web Browser • Sphinx returns a Grid Job Id Korea Workshop May 2005

  7. Sphinx manages job submission • Sphinx locates available resources based on policy information • Cpu • Input data • Network resources • Submit job to remote site via BOSS Korea Workshop May 2005

  8. Monitor Progress • Lifelines give immediate feedback on all job status • BOSS Job Monitoring • MonALISA Monitoring Korea Workshop May 2005

  9. Job Lifeline Korea Workshop May 2005

  10. BOSS Job Monitoring Korea Workshop May 2005

  11. MonALISA Job Monitoring • Correlate Lifelines with remote system status Korea Workshop May 2005

  12. Collect Results • When job is finished, use Logical File Result and Dataset Catalog to obtain result data • CAVES used for version control on ROOT session • Allows sharing analysis code between users and groups • ROOT display for visualization of results Korea Workshop May 2005

  13. CAVES code management Korea Workshop May 2005

  14. View Results Pz,Px,Py plot of Higgs -> WW Korea Workshop May 2005

  15. View Results Korea Workshop May 2005

More Related