The Pion Formfactor Experiment

FPI2 CVS INSTRUCTIONS

Dear All,

In the following I listed instructions on how to use fpi2 CVS. I suppose you have already set up your replay engine using normal CVS tools. So what I said is only specific for our fpi2 branch.

If you have questions concerning the follow, please email me. (xu@jlab.org)

In the future you may have suggestions or modifications to cvs fpi2 branch. If that is the case, email me. I will make commitment to cvs fpi2 if I think it is really specific to pion form factor meamurements.

(1) Why fpi2 branch?

Although the general reconstruction part is common for every users, there should be some files in replay engine that should be specific for different physics groups. It would be convenient for each physics group to share such frequently touched files and to have a good starting point without taking too much time.

Using CVS of fpi2 branches is a good and easy way to let every people in fpi group to have the same verion of fpi2 analysis.

(2) GeneraL Contents of CVS fpi2?

Up to now, I feel that the following files in ENGINE directory are frequently touched files that could be specific to our fpi group:

c_keep_results.f c_ntuple_init.f c_ntuple_keep.f c_physics.f h_ntuple_init.f h_ntuple_keep.f s_ntuple_init.f s_ntuple_keep.f

The major changements are in c_physics.f. All the changes are from Jochen Volmer, and adapted by me to fit new version of replay engine.

Of course in order to let it run properly, we should also make changements in INCLUDE directory the files

coin_data_structures.cmn

So I have listed all the freqently touched files for ordinary users of replay engine.

In addition to the above changes, I also made some changes about the input files like (in replay directory)

pion.database pion.hist pion.test REPLAY.PARM

And some files in /replay/DBASE, /replay/MAPS, /replay/PARAM,

All these changements are made just in order to let some input values (thresholds, detector status etc.) make sense for Oct97's data (which was the data JOchen Volmer used), and also make the output files (like hbook files) interesting for our fpi purpose.

Of course, when new data comes, I will update these files again, and inform you.

All my modification in these files starts from comments like

c xucc added begin and end at comments like c xucc added end

(3) How to make good use of CVS fpi2 branch?

(a) For technical reason, please put Analyzer directory in a parralel place as replay directory if you have not done this.

(b) go to replay directory, and do the following ONLY ONCE:

cvs update -r fpi2 pion.database cvs update -r fpi2 pion.hist cvs update -r fpi2 pion.test cvs update -r fpi2 DBASE cvs update -r fpi2 HIST cvs update -r fpi2 MAPS cvs update -r fpi2 PARAM cvs update -r fpi2 REPLAY.PARM

(c) go to Analyzer/ENGINE directory, and do the following ONLY ONCE:

cvs update -r fpi2 c_keep_results.f cvs update -r fpi2 c_ntuple_init.f cvs update -r fpi2 c_ntuple_keep.f cvs update -r fpi2 c_physics.f cvs update -r fpi2 h_ntuple_init.f cvs update -r fpi2 h_ntuple_keep.f cvs update -r fpi2 s_ntuple_init.f cvs update -r fpi2 s_ntuple_keep.f

(d) go to Analyzer/INCLUDE directory, and do the following only ONCE

cvs update -r fpi2 coin_data_structures.cmn

(e) After doing this, you will be able to run the engine.

And in the futures, if you want to update everything (that is, update the above frequently touched files according to fpi2 branch, and other parts according to nromal cvs), just type

cvs update

In replay directory and in Analyzer directory.

This site is maintained by Xu CHuncheng