Difference between revisions of "TCS"
From Hall A Wiki
(→code) |
(→code) |
||
| Line 100: | Line 100: | ||
** The virtual machine only has terminal, Xwindow is not working, so use "ctr+F*" to swtich between terminals. both user "zwzhao" and root has passwrod "111111", | ** The virtual machine only has terminal, Xwindow is not working, so use "ctr+F*" to swtich between terminals. both user "zwzhao" and root has passwrod "111111", | ||
** The code is under /home/zwzhao/grape-dilpeton_v1.1k ( I had to modify its makefile to compile it) | ** The code is under /home/zwzhao/grape-dilpeton_v1.1k ( I had to modify its makefile to compile it) | ||
| − | ** My work dir is at /home/zwzhao/grape_work where you can see some examples, Read the code website and its "README" file to understand how its input parameters defined in "grape.cards" and how to run it. Basically, create a new dir, create a new "grape.cards" file, run /home/zwzhao/grape-dilpeton_v1.1k/src/integ (take a long time like 10 hours), then run /home/zwzhao/grape-dilpeton_v1.1k/src/spring, then an ntuple "grp.rz" is produced. You can convert grp.rz to a root file by h2root, then | + | ** My work dir is at /home/zwzhao/grape_work where you can see some examples, Read the code website and its "README" file to understand how its input parameters defined in "grape.cards" and how to run it. Basically, create a new dir, create a new "grape.cards" file, run /home/zwzhao/grape-dilpeton_v1.1k/src/integ (take a long time like 10 hours), then run /home/zwzhao/grape-dilpeton_v1.1k/src/spring, then an ntuple "grp.rz" is produced. You can convert grp.rz to a root file by h2root, then analysis it by https://jlabsvn.jlab.org/svnroot/solid/evgen/BH |
** Currently known problem: 1. occasionally, integ wouldn't end because grid calculation can't coverge for certain configuration. 2. spring seems have a fixed random seed, so every time it generator the same file. 3. spring will crash when events go more than 2.9M due to unknown reason. | ** Currently known problem: 1. occasionally, integ wouldn't end because grid calculation can't coverge for certain configuration. 2. spring seems have a fixed random seed, so every time it generator the same file. 3. spring will crash when events go more than 2.9M due to unknown reason. | ||
Revision as of 18:22, 2 February 2015
Contents
Introduction
TCS (timelike Compton Scattering)
email list
ee@jlab.org
register at https://mailman.jlab.org/mailman/listinfo/ee
meeting
Theory
https://www.dropbox.com/sh/lw7iyajs277odsp/AABaR0OM0oxEvuP80xnqoetda?dl=0
reference
mixed things
https://www.dropbox.com/sh/v1zd54vx5xhfrjb/AAAmSMb4AhUQNBz0jGE4E6AUa?dl=0
talk
Jakub Wagner, "Timelike Compton Scattering" Friday November 14th 2014, CLAS Coll Meeting [1]
J. Wagner "Timelike Compton Scattering with Transversely Polarized Targets" NPS Collaboration Meeting (JLab, 11/19/14) [2]
more https://www.dropbox.com/sh/5cidea0kdfcomy7/AADcLPiQS2cuDbN3nZwzQZgUa?dl=0
past experiments
future experiment
CLAS12_TCS (unpolarized)
- TCS (E12-12-001) at CLAS12, approved 120 days, rated A-, Submission at PAC 39
SoLID_TCS (unpolarized)
talk
2013/03 SoLID Collbration meeting update by Zhiwen Zhao pptxpdf
proposal
draft in updating https://userweb.jlab.org/~turonski/tcs/proposals/solid/tcs_solid_proposal.pdf
working directory (any one can read and write) https://userweb.jlab.org/~turonski/tcs/proposals/solid/
doc
- J/Psi (E12-12-006) at SoLID, approved 60 days, rated A-, Submission at PAC 39
simulation result
SoLID_TCS_result done in April 2013
Plots are png and eps
simulation binning explained in SoLID_TCS_bin.txt
simulation binning with R' error can be used for plot, SoLID_TCS_Q2bin.txt and SoLID_TCS_etabin.txt
R_bins.txt, LO and NLO calculation from Jakub Wagner
R_bins.tar.gz for GPD model calculation from Vadim Guzey with details explained in R_bins.tar.gz_email
CLAS12 TCS (linearly polarized)
code
- genTCS
- grape-dilepton
- http://research.kek.jp/people/tabe/grape
- BH from electron on proton, used by the experiments at DESY/HERA
- similar result comparing to LPAIR, see here
- It was written in early 2000 and depends on an older version of cernlib.
- To repeat its exact environment, I built a redhat7 virtual machine to run it. download the compressed the file here and decompress it using program 7z. You need free vmplayer [3] on linux or windows to run the virtual machine. On Mac, download the tool [4] and convert "ovftool name.vmx name.ova", then use virtualbox [5] to import the ova file run the virtual machine
- The virtual machine only has terminal, Xwindow is not working, so use "ctr+F*" to swtich between terminals. both user "zwzhao" and root has passwrod "111111",
- The code is under /home/zwzhao/grape-dilpeton_v1.1k ( I had to modify its makefile to compile it)
- My work dir is at /home/zwzhao/grape_work where you can see some examples, Read the code website and its "README" file to understand how its input parameters defined in "grape.cards" and how to run it. Basically, create a new dir, create a new "grape.cards" file, run /home/zwzhao/grape-dilpeton_v1.1k/src/integ (take a long time like 10 hours), then run /home/zwzhao/grape-dilpeton_v1.1k/src/spring, then an ntuple "grp.rz" is produced. You can convert grp.rz to a root file by h2root, then analysis it by https://jlabsvn.jlab.org/svnroot/solid/evgen/BH
- Currently known problem: 1. occasionally, integ wouldn't end because grid calculation can't coverge for certain configuration. 2. spring seems have a fixed random seed, so every time it generator the same file. 3. spring will crash when events go more than 2.9M due to unknown reason.
- LPAIR
- used by the experiments at DESY/HERA
- Compton2.0
- BH from photoproduction, used by ZEUS
- GiBUU
- gibuu.hepforge.org
(It may work on neutron also) GiBUU does a good job with real photons on a proton (or heavier) target. It doesn't handle electroproduction as nicely (at least not the last time I asked the Giessen group). It is fairly straight forward to generate events, and there USED to be good examples of input jobcards on the website, but they have been removed recently while they upgrade. I'd think the best route is to email them directly to get the code and also ask for the example jobcards.
