Difference between revisions of "Event display tutorial"

From Atlas Wiki
Jump to navigation Jump to search
 
(9 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
== Installing Atlantis ==
 
== Installing Atlantis ==
  
- Download the latest version of atlantis at: http://atlantis.web.cern.ch/atlantis/atlantis_10.0.0-20050408.zip.
+
* Download the latest version of atlantis at: http://atlantis.web.cern.ch/atlantis/atlantis_10.0.0-20050408.zip.
  
- Unzip atlantis
+
* Unzip atlantis
 +
<font color = red >
 +
<pre>unzip atlantis_10.0.0-20050408.zip</pre>
 +
</font>
  
unzip atlantis_10.0.0-20050408.zip
+
* Done!
  
- Done!
+
== Running Atlantis ==
 +
 
 +
* After the previous step you can now run atlantis by typing:
 +
<font color = red >
 +
<pre>
 +
java -jar atlantis/atlantis.jar
 +
</pre>
 +
</font>
 +
* <b>Or</b> if you would like to look at event displays reconstructed with <b>ATLFAST</b> type:
 +
<font color = red >
 +
<pre>java -jar atlantis/atlantis.jar Fast</pre>
 +
</font>
 +
* Atlantis versions require JAVA version 1.4 or higher to run.
 +
 
 +
* Atlantis will start-up with an example event display file with which you can play around a bit. You can select another event display by going to "File" followed by "Read event" in the Atlantis GUI window. Atlantis event displays are stored in the form of a .xml file. The next section will explain how to create your own event display files using JiveXML
  
== Running Atlantis ==
+
== Creating event display files with JiveXML ==
  
- After the previous step you can now run atlantis by typing:
+
* Make sure you have the [[atlas_1002_setup|atlas 10.0.2 software environment]] set-up and initialized
  
java -jar atlantis/atlantis.jar
+
* Obtain an AFS token at cern: <font color = red >klog <cern_userid>@cern.ch </font>and type your CERN AFS password at the prompt.
 +
 +
* Check-out and compile the latest version of JiveXML
 +
<font color = red >
 +
<pre>
 +
cmt co -r JiveXML-00-03-65 graphics/JiveXML
 +
cd graphics/JiveXML/JiveXML-00-03-65/cmt
 +
gmake
 +
</pre>
 +
</font>
 +
* Now I can tell you two ways to make some event display files!
  
- <b>Or</b> if you want like to look at event displays reconstructed with <b>ATLFAST</b> type:
+
* <b>ATLFAST</b> Let's take as an example the [[Generating_Higgs_To_4_Muons_at_NIKHEF|Generating_Higgs_To_4_Muons_at_NIKHEF]] tutorial! To create displays for these events just add the following lines in the code of <font color = blue >joboptions_HiggsGeneration.py</font> that was given in the tutorial.
 +
<font color = blue >
 +
<pre>
 +
include( "JiveXML/JiveXMLAtlfast_jobOptionFragment.py" )
 +
EventData2XML = Algorithm( "EventData2XML" )
 +
EventData2XML.FileNamePrefix = "HiggsTo4Muons_FAST"
 +
</pre>
 +
</font>
  
java -jar atlantis/atlantis.jar Fast
+
* And then run it as usual:
  
- Atlantis versions require JAVA version 1.4 or higher to run.
+
<font color = red >
 +
<pre>
 +
athena.py joboptions_HiggsGeneration.py
 +
</pre>
 +
</font>
  
- Atlantis will start-up with an example event display file with which you can play around a bit. You can select another event display by going to "File" followed by "Read event" in the Atlantis GUI window. Atlantis event displays are stored in the form of a .xml file. The next section will explain how to create your own event display files using JiveXML
+
* For each event that you reconstruct JiveXML will create a file .xml that will look like: <font color = blue >HiggsTo4Muons_FAST_0_00000.xml </font>(first event), <font color = blue >HiggsTo4Muons_FAST_0_00001.xml</font> (second event) etc. This files can now be opened in Atlantis (running in Fast mode!) as was explained previously.
  
== Creating event display files with JiveXML ==
+
* <b>Full reconstruction with RecExCommon:</b> If you are using RecExCommon for full reconstruction just add the following line in <font color = blue >myTopOptions.py</font> to create a JiveXML-file for each event you reconstruct
 +
<font color = blue >
 +
<pre>
 +
doJiveXML=True
 +
</pre>
 +
</font>
 +
* Still haven't figured how to set the FileNamePrefix of the files you generate this way. So now your files will have the default prefix and will look something like <font color = blue >JiveXML_0_00000.xml</font> ...

Latest revision as of 17:47, 15 June 2005

Installing Atlantis

  • Unzip atlantis

unzip atlantis_10.0.0-20050408.zip

  • Done!

Running Atlantis

  • After the previous step you can now run atlantis by typing:

java -jar atlantis/atlantis.jar

  • Or if you would like to look at event displays reconstructed with ATLFAST type:

java -jar atlantis/atlantis.jar Fast

  • Atlantis versions require JAVA version 1.4 or higher to run.
  • Atlantis will start-up with an example event display file with which you can play around a bit. You can select another event display by going to "File" followed by "Read event" in the Atlantis GUI window. Atlantis event displays are stored in the form of a .xml file. The next section will explain how to create your own event display files using JiveXML

Creating event display files with JiveXML

  • Obtain an AFS token at cern: klog <cern_userid>@cern.ch and type your CERN AFS password at the prompt.
  • Check-out and compile the latest version of JiveXML

cmt co -r JiveXML-00-03-65 graphics/JiveXML
cd graphics/JiveXML/JiveXML-00-03-65/cmt
gmake

  • Now I can tell you two ways to make some event display files!
  • ATLFAST Let's take as an example the Generating_Higgs_To_4_Muons_at_NIKHEF tutorial! To create displays for these events just add the following lines in the code of joboptions_HiggsGeneration.py that was given in the tutorial.

include( "JiveXML/JiveXMLAtlfast_jobOptionFragment.py" )
EventData2XML = Algorithm( "EventData2XML" )
EventData2XML.FileNamePrefix = "HiggsTo4Muons_FAST"

  • And then run it as usual:

athena.py joboptions_HiggsGeneration.py

  • For each event that you reconstruct JiveXML will create a file .xml that will look like: HiggsTo4Muons_FAST_0_00000.xml (first event), HiggsTo4Muons_FAST_0_00001.xml (second event) etc. This files can now be opened in Atlantis (running in Fast mode!) as was explained previously.
  • Full reconstruction with RecExCommon: If you are using RecExCommon for full reconstruction just add the following line in myTopOptions.py to create a JiveXML-file for each event you reconstruct

doJiveXML=True

  • Still haven't figured how to set the FileNamePrefix of the files you generate this way. So now your files will have the default prefix and will look something like JiveXML_0_00000.xml ...