How to generate MC events on Rivanna?
- Login to Rivanna
- Create a folder under your name on /project/ptgroup/
- There are various script to generate
- Copy the relevant code-directory from /project/ptgroup/Akbar (please see the screenshot below for the file location and the content inside a folder called "DY_Target_script")
Note: you don't need to copy the "scratch" folder from "/project/ptgroup/Akbar" location. You will need to create an empty "scratch" folder in your "DY_Target_script"'s location for example. [Please Confirm] You need not create it since it is auto-created in "jobscript.sh".Here is a simple way of copying a folder ("DY_Target_script" for example) except "scratch";
cd /project/ptgroup/YourFolder
rsync -av --exclude scratch /project/ptgroup/Akbar/DY_Target_script .
The code has following settings
Variable value 1 (default) value 2 value 3 value 4 Vertex Origin Target Dump - After modifying the script, then submit your job using the following command.
$ ./jobscript.sh <Output_folder_name> <No_of_jobs> <No_of_events_per_job>
$ ./jobscript.sh DY_Target_1M 100 10000 (Here we need o generate ~1M events to have about 200-300 accepted events. - Using "squeue -u cee9hc", you can check the status of your jobs (or use the "Active Jobs" tab on your UVA OpenOnDemand web page).
- Once the job is finished, then you can find your output folder in "/scratch/<your_UVA_id>/MC (Note: if you don't have a folder called "MC" on /scratch/<user_name> then create one by "mkdir MC" at /scratch/user_name location).
- Navigate to "/project/ptgroup/" and then implement the following command (this script by-default will skip bad-files/corrupted-files/etc.)
$ ./merge_mc_prod.sh /scratch/<your_MC_output_file_location>
This will create a folder inside /project/ptgrpup/spinquest/MC_merge_files" with the same name as your MC_output_folder - Copy the "merged_trackQA_v2.root" file from the folder that you've newly generated by ./merge_mc_prod.sh and move it to "/project/ptgroup/spinquest/MC_storage" location.
- Use the label.C file in the "/project/ptgroup/spinquest/MC_storage" to add summary description of your MC .root file.
MC events generation log-book
| Date | Process | Vertex Location | Number of Total events generated | Number of accepted events | <> |
|---|---|---|---|---|---|
Unsorted Info
Kenichi and anyone write down some possibly-useful info here (rather than e-mail). The info may be moved to a proper section when made use of.
- Better configurations for J/psi and psi' are available in the E1039-Collaboration/e1039-analysis repository. Zulkaida could make use of them in "/project/ptgroup/Akbar/*/Fun4Sim.C".
- https://github.com/E1039-Collaboration/e1039-analysis/blob/master/SimChainDev/phpythia8_Jpsi.cfg ... It produces J/psi and other charmonia (including psi'), where the rate of psi' is much lower than the current configuration.
- https://github.com/E1039-Collaboration/e1039-analysis/blob/master/SimChainDev/phpythia8_psip.cfg ... It produces only psi', not J/psi.
- Note: Even when using new configurations, you should still select the particle of your interest (i.e. J/psi or psi') by its truth mass in `histo.C`. It is because a random pair (like mu+ from pi+ and mu- from pi-) could be produced from the beam remnant.
- reco_vz
- reco_vz is the reconstructed position of track (not dimuon) at the target position (i.e. z = -300 cm). Therefore "reco_vz" is always -300 cm
- The meaning of "reco_vz" is defined in "AnaTrkQA". Actually the present naming is misleading.
- When dimuon events are produced in the dump, each track should make the closest approach to the z-axis in the dump region. But "reco_vz" is not the position of the closest approach but the position of the track at z = -300 cm by definition. "reco_vx" and "reco_vy" are not peaked at 0 cm.
- Others??