Making Hippy alignment dir and running an alignement

cmsenv in a CMSSW_10_5_2_pre1 area


run the command:

makeHippyCampaign.py foldername --subfolder (will be the directory uncder mainhippy dir) --merge-topic hroskes:hippy-scripts

This takes a while and makes a folder /afs/cern.ch/cms/CAF/CMSALCA/ALCA_TRACKERALIGN2/HipPy/foldername, which contains your CMSSW release and folders called Jobs/ and run/. Jobs/ is where the jobs eventually happen. run/ is where all the scripts are.

Then go to

/afs/cern.ch/cms/CAF/CMSALCA/ALCA_TRACKERALIGN2/HipPy/

Here it has created a directory : subfolder/foldername
That has a CMSSW area, a run dir and a Jobs area

cd CMSSW/src

cmsenv

git cms-init

git cms-addpkg Alignment/HIPAlignmentAlgorithm

cd Alignment/HIPAlignmentAlgorithm/scripts

rm submitJobs_py

rm submitAndWatchHippy.sh

wget https://github.com/cms-sw/cmssw/blob/master/Alignment/HIPAlignmentAlgorithm/scripts/submitJobs_py

wget https://raw.githubusercontent.com/cms-sw/cmssw/master/Alignment/HIPAlignmentAlgorithm/scripts/submitAndWatchHippy.sh

chmod +x submitJobs_py

chmod +x submitAndWatchHippy.sh

cd .../../

scram b

Then change the configuration scripts to point to the data set , IOV and alignables that are needed :

Inside run/ there are a few things:
DataFiles - here you have to set up a txt file with a list of data files to run on. To get the list, you can run this script.
writedatasetfile.py -d /.../.../ALCARECO --first-run ... --last-run ... --hippy myfilelist.txt -j neventsperjob -m maxevents

For collisions, neventsperjob=10000 typically makes each iteration take about 20 minutes. I suggest starting with that and then checking how many jobs there will be (by doing wc -l myfilelist.txt). If it's too many you can either increase neventsperjob or set maxevents.

Then you can get rid of the COSMICS and CDCs line in data_example.lst and set the minbias line to point to your txt file.

IOV - you want a file that points to the first run of your dataset

Configurations - the only thing you have to touch here is the "common" file. Here you set the global tag, the conditions to override (templates, maybe starting alignment), and the alignables. To align at ladder level, uncomment the lines "TrackerP1PXBLadder,111111" and "TrackerP1PXECBlade,111111". The 111111 refer to x y z theta_x theta_y theta_z. It's probably better to turn off z in FPIX, so change it to 110111.

You can also change minimumNumberOfHits if you want. That's about all we normally change.

Then, in the main folder, the last thing to change is submit_template.sh. You just have to edit the variables that start out commented.
hpnumber is the ID number of the alignment. It refers to the name of the folder in /afs/cern.ch/cms/CAF/CMSALCA/ALCA_TRACKERALIGN2/HipPy/alignments. You can just increment the last number by 1.
common, lstfile, IOVfile - these are the names of the files you set up
alignmentname - this is the name of a folder in Jobs where it gets run
niterations - typically we do 10
Then the script requires you to git commit what you've done. It's a little git repository with all these scripts.






After cd into the run dir

voms-proxy-init

cp /afs/cern.ch/user/h/hroskes/work/public/forCarol/startscreen

screen -r

navigate back to the HiPY directory

after that you can do

./submit_template.sh (or however you named your excecutable)

Edit | Attach | Watch | Print version | History: r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r1 - 2019-06-12 - SavvasKyriacou
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Sandbox 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.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback