Project

General

Profile

Swizzle » History » Version 16

Michael Kirby, 05/11/2015 04:32 PM

1 16 Michael Kirby
h1. Instructions for setting up to swizzle.
2 1 Eric Church
3 1 Eric Church
When you swizzle -- that is, convert from the DAQ binary to ART ROOT data format -- you want to read the binary data with the guaranteed-same code with which you wrote it. That is the reason for the existence in the first place of uboonedaq_datatypes. It's its own ups package against which we set up and build for both the DAQ running and the swizzling. 
4 1 Eric Church
5 1 Eric Church
6 12 Eric Church
If all you want is to run with a LArSoft -- particularly, the uboonecode build -- that was built against this version of uboonedaq_datatypes you can do that as described in this section. We have installed this version for v5_00_01. So, set up on @ubdaq-prod-xyz.fnal.gov@ as follows. Do not set up as if you were going to do DAQ readout or run control or develop uboonedaq_datatypes.
7 11 Eric Church
8 12 Eric Church
Everything on this page should work under the interchange qe6:prof <---> qe6:debug. 
9 1 Eric Church
 
10 1 Eric Church
@source /uboone/larsoft/setups
11 1 Eric Church
export PRODUCTS=$PRODUCTS:/uboone
12 11 Eric Church
setup uboonedaq_datatypes v5_00_01 -qe6:prof      
13 11 Eric Church
setup uboonecode v03_04_00 -qe6:prof                    
14 1 Eric Church
setup mrb; setup git; setup gitflow
15 1 Eric Church
export MRB_PROJECT=larsoft@
16 9 Eric Church
Go run your @lar -c job.fcl@ script. 
17 1 Eric Church
18 3 Eric Church
You may stop here if you care nothing about maintaining/installing or how the sausage is made. 
19 1 Eric Church
20 2 Eric Church
h1. There is one important technical issue here for running LArSoft on the DAQ.
21 1 Eric Church
22 6 Eric Church
That is, LArSoft runs gcc4.9.1 and boost 1.59, and the DAQ uses gcc4.7, boost1.55. We begin by making a vx_yy_zz version of uboonedaq_datatypes with these new qualifiers. Go to the quickstart page for uboonedaq_datatypes at the top of the DAQ wiki and jump to the bottom of those instructionns to see how we do that, if interested.
23 1 Eric Church
24 2 Eric Church
h1. Next, we need LArSoft installed on the LArTF cluster.
25 2 Eric Church
26 6 Eric Church
The DAQ does not want to move up versions of LArSoft -- maybe ever -- but certainly not often. ups makes this doable, however, if it does become necessary. ubdaq-prod-evb:/uboone/larsoft currently holds v03_04_00 and a few older versions of installed LArSoft. e.g., LArSoft v02_05_01 is there -- the version that MicroBooNE's MCC5 used.
27 6 Eric Church
28 1 Eric Church
Installing LArSoft is conveniently handled by going to the FNAL scisoft server and downloading the pullProducts*.txt file to some local area on your machine at LArTF. Then, as root, run the script to install the binaries to /uboone/larsoft. (No need to build from source, since we're on SLF6.) pullProducts will know to update to a new vx_yy_zz directory, if indeed you're keen to do this. @chmod -R products.products /uboone/larsoft.@
29 2 Eric Church
30 1 Eric Church
h1. Developing in LArSoft with the ubdaq-prod- installation.
31 1 Eric Church
32 16 Michael Kirby
--------------start of edits from Kirby -------------------
33 1 Eric Church
34 16 Michael Kirby
The uboonedaq_datatypes is now installed on both the online cluster and in the /grid/fermiapp/products/uboone/ area and so we are not limited to development on the online cluster. As well, the offline area has moved from /uboone/larsoft/ to /uboone_offline/ area. That area has had larsoft v04_05_00 and v04_06_00 installed as of May 11, 2015. You can see the manifest of the larsoft installs by looking at MANIFEST files in /uboone_offline/.  Starting with v04_08_00, we are hoping that uboonecode will have a dependency against uboonedaq_datatypes built into it so that it will be configured correctly without doing so by hand.
35 16 Michael Kirby
36 16 Michael Kirby
For now though, to develop against the uboonedaq_datatypes that are in installed online and offline, If we want to develop LArSoft, we must, in the usual way, form a release area on ubdaq-prod-evb at /home/user/larsoft. Setup as at the top of this page. Then do a @mrb newDev v04_05_00 -T prof.slf6.v04_05_00@, as usual. In srcs pull the code and importantly, *switch to the branch that knows how to build against uboonedaq_datatypes. Do:* @mrb g -b feature/ubdaq uboonecode; mrg g -b feature/davidc1_daqheader lardata@
37 16 Michael Kirby
38 16 Michael Kirby
There are modifications that need to be made within these packages:
39 16 Michael Kirby
40 16 Michael Kirby
#change the lardata/ups/product_deps to have these version
41 16 Michael Kirby
parent  lardata v04_04_00
42 16 Michael Kirby
defaultqual     e7
43 16 Michael Kirby
#
44 16 Michael Kirby
fcldir product_dir job
45 16 Michael Kirby
#
46 16 Michael Kirby
product         version
47 16 Michael Kirby
larcore         v04_04_00
48 16 Michael Kirby
nutools         v1_09_01
49 16 Michael Kirby
gcc             v4_9_2
50 16 Michael Kirby
51 16 Michael Kirby
cetbuildtools   v4_04_02        -       only_for_build
52 16 Michael Kirby
end_product_list
53 16 Michael Kirby
54 16 Michael Kirby
55 16 Michael Kirby
# e7  - with gcc 4.9.1 and -std=c++1y
56 16 Michael Kirby
qualifier       larcore         nutools         gcc     notes
57 16 Michael Kirby
e7:debug        e7:debug        e7:debug        -nq-
58 16 Michael Kirby
e7:opt          e7:opt          e7:opt          -nq-
59 16 Michael Kirby
e7:prof         e7:prof         e7:prof         -nq-
60 16 Michael Kirby
end_qualifier_list
61 16 Michael Kirby
62 16 Michael Kirby
#uboonecode/ups/product_deps changes in 
63 16 Michael Kirby
parent uboonecode v04_05_00
64 16 Michael Kirby
defaultqual e7
65 16 Michael Kirby
66 16 Michael Kirby
#change the uboonecode/ups/products_deps to have this dependency
67 16 Michael Kirby
product          version
68 16 Michael Kirby
larsoft         v04_05_00
69 16 Michael Kirby
ubutil          v01_16_00
70 16 Michael Kirby
postgresql      v9_1_15
71 16 Michael Kirby
gcc        v4_9_2
72 16 Michael Kirby
uboonedaq_datatypes v5_00_01 #and the matching qualifiers below
73 16 Michael Kirby
74 16 Michael Kirby
cetbuildtools    v4_04_02    -    only_for_build
75 16 Michael Kirby
76 16 Michael Kirby
#uboonecode/CMakeList.txt and lardata/CMakeList.txt modify to be -std=c++1y
77 16 Michael Kirby
cet_set_compiler_flags( DIAGS CAUTIOUS
78 16 Michael Kirby
  WERROR
79 16 Michael Kirby
  NO_UNDEFINED
80 16 Michael Kirby
  EXTRA_FLAGS -pedantic -Wno-unused-local-typedefs -std=c++1y
81 16 Michael Kirby
)
82 16 Michael Kirby
83 16 Michael Kirby
---------end kirby edits ---------------
84 16 Michael Kirby
85 16 Michael Kirby
The issue now is getting the uboonecode repository's @uboonecode/uboone/RawData/utils/LArRawInput*@ files to compile/link against our uboonedaq_datatypes and not the data structures that are hand-copied there. That unsavory manner is how uboonecode's develop branch works currently.
86 11 Eric Church
87 15 Eric Church
If we want to develop LArSoft, we must, in the usual way, form a release area on ubdaq-prod-evb at /home/user/larsoft. Setup as at the top of this page. Then do a @mrb newDev vxx_yy_zz -T prof.slf6.vxx_yy_zz@, as usual. In srcs pull the code and importantly, *switch to the branch that knows how to build against uboonedaq_datatypes. Do:* @mrb g uboonecode; git checkout feature/ubdaq@. At some point maybe we will merge this branch into uboonecode's develop. However, doing that commits us to having uboonedaq_datatypes installed for all of LArSoft. It requires a push to /grid/fermiapp/products and a push to cvmfs, and as yet, we aren't ready to commit to that. Also, it can be argued swizzling and thus the dependence on uboonedaq_datatypes should be confined to the ubdaq-prod machines. For now, we work in feature/ubdaq. 
88 5 Eric Church
89 10 Eric Church
(The above setup @uboonecode v03_04_00 -qe6:prof@ gets you the installed build that originates from feature/ubdaq, as described here, so if you don't need to add anything to this branch there's no reason to have done the git pull and git checkout feature/ubdaq.)