Running the MuCTPI simulation on digitized data

This is just a quick introduction on how to run the MuCTPI simulation on an already digitized file. This is mostly only relevant for the ongoing overlap studies, but it might come in handy for other purposes as well.


The input file has to be a digitized file, in which the output of the MuCTPI simulation is saved. This might sound confusing, but the simulation can only be re-run, if it was run the time the digitized file was created. (This is because the output of the MuCTPI is transformed back into the input object of the simulation.)

The newest tag at the time of writing is TrigT1Muctpi-00-01-00. This is indeed the first tag where this new possibility was introduced. It has to be checked out and compiled.

I've developed and tested the simulation with release 11.0.0, but again, there should be no reason why it couldn't be used with any release after 10.0.0.

Running the simulation

The following two jobO files can be used to run the MuCTPI simulation with digitized input: and

As usual, the simple setup options are in

Also the jobO file of the simulation (TrigT1Muctpi/share/ has to be edited. The following properties have to be set for the L1Muctpi algorithm:

  • InputSource: It can take 3 different values currently.
    • DIGITIZATION: This is the default mode. The simulation reads the input from the RPC and TGC simulation.
    • AOD: The simulation is run on MUON_ROI objects. More about this mode in the topic devoted to this. (Not written yet.)
    • RDO: This is the mode that has to be selected in order to run on digitized files.
  • RDOOutputLocID: The location to put the new output MuCTPI_RDO object to. As the default value is MUCTPI_RDO, this should be set to something else to avoid the clash between the old and new MuCTPI_RDO objects. Still it should be a meaningful value, as we'll want to read this object back for analysis later on.
  • RoIOutputLocID and CTPOutputLocID: These are only here to avoid the clash between the objects already present in the digitized file and the objects created when runnign the MuCTPI simulation again. They can be set to any meaningless value, they won't be saved anyway. (And there is quite small chance that one would set the same ~15 character long values as the default ones.)

And of course additionally the properties for the overlap handling should be set correctly. (That's the whole point of re-running the MuCTPI simulation after all.)

The job can be run in the usual way with something like #> -s 2>&1 | tee muctpi.log under bash.

Analyzing the output of the simulation

The same jobOption files can be used as in AnalyzingDigOutput, with a slight change. I modified the ReadMuCTPI_RDO algorithm (latest tag required...), so now the location of the MuCTPI_RDO object can be specified. If it is not, then the default value of MUCTPI_RDO is used, which means the original output object will be read. The property can be set on the jobO file with: ReadMuCTPI_RDO.RDOLocID = "value_specified_earlier".

Just for completeness here are the two files I used for reading the MuCTPI output: and

-- AttilaKrasznahorkay - 09 Nov 2005

Topic attachments
I Attachment History Action Size Date Who Comment
Python source code filepy r1 manage 0.7 K 2005-11-09 - 15:26 AttilaKrasznahorkaySecondary jobO for running the sim
Python source code filepy r1 manage 3.2 K 2005-11-09 - 15:27 AttilaKrasznahorkaySecondary jobO for running the sim
Python source code filepy r1 manage 5.0 K 2005-11-09 - 15:25 AttilaKrasznahorkaySecondary jobO for reading the output of the sim
Python source code filepy r1 manage 0.7 K 2005-11-09 - 15:24 AttilaKrasznahorkaySecondary jobO for reading the output of the sim
Edit | Attach | Watch | Print version | History: r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r1 - 2005-11-09 - AttilaKrasznahorkaySecondary
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Main All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback