Project

General

Profile

Wiki » History » Version 28

Eric Church, 05/28/2013 10:29 AM

1 23 Herbert Greenlee
{{toc}}
2 23 Herbert Greenlee
3 17 Eric Church
h1. Welcome to the MicroBooNE offline software project. 
4 17 Eric Church
5 18 Eric Church
For now there's no pubic build. You must download the uBooNE code to your usual LArSoft test release area and build there. When we have lots more code we'll consider a nightly build and more administration.
6 16 Eric Church
7 6 Eric Church
8 13 Eric Church
Here are the instructions to use the uBooNE offline svn repository.
9 27 Wesley Ketchum
*  Contact a manager (like Wes, wketchum@fnal.gov) to get added to the developer list if you are not already on it.
10 14 Eric Church
*  Go setup yourself up to work with LArSoft as instructed at https://cdcvs.fnal.gov/redmine/projects/larsoftsvn/wiki.
11 1 Eric Church
*  If you don't already have one, make yourself a test release in the usual way, @newrel -t development dirname; cd dirname; srt_setup -a;@.
12 27 Wesley Ketchum
13 27 Wesley Ketchum
Now, if you only need a part of the repository, you could do something like this...
14 28 Eric Church
*  Go in @dirname@ say @svn co svn+ssh://p-ubooneoffline@cdcvs.fnal.gov/cvs/projects/ubooneoffline/trunk/GENIEextractor@, for example. 
15 5 Eric Church
*  @cd include@; and say @ln -s ../GENIEextractor/ .@ (don't forget the dot) and then cd back to the top dirname.
16 1 Eric Church
*  @gmake GENIEextractor.all@, and construct your fcl file and run @lar -c myjobscript.fcl@ as usual.
17 1 Eric Church
*  Be sure and @svn ci -m "helpful comment" svn+ssh://p-ubooneoffline@cdcvs.fnal.gov/cvs/projects/ubooneoffline/trunk GENIEextractor@ and @svn update svn+ssh://p-ubooneoffline@cdcvs.fnal.gov/cvs/projects/ubooneoffline/trunk@ frequently.
18 27 Wesley Ketchum
*  You can export (bash) setenv (csh) CVSROOT to svn+ssh://p-ubooneoffline@cdcvs.fnal.gov/cvs/projects/ubooneoffline/ or svn+ssh://p-larsoftsvn@cdcvs.fnal.gov/cvs/projects/larsoftsvn/trunk/ as you work with each repository and thus not need to spell it out each time, if you find that to be less unwieldy.
19 1 Eric Church
20 27 Wesley Ketchum
Alternatively, if you want to set up a directory for you to put in and share lots of stuff, we recommend doing this:
21 27 Wesley Ketchum
*  Go in to your test release (@dirname@) and do @svn co svn+ssh://p-ubooneoffline@cdcvs.fnal.gov/cvs/projects/ubooneoffline@
22 27 Wesley Ketchum
*  Add a directory for yourself in the @users@ area. If your username is @bluebeard@, do: @cd ubooneoffline; svn mkdir users/bluebeard; svn update@
23 27 Wesley Ketchum
*  Now, put your pirate treasure in your directory! To put it in the repository, do:  @svn add pirate_treasure; svn commit -m 'arrrr!' pirate_treasure@
24 27 Wesley Ketchum
*  Put your code here!
25 23 Herbert Greenlee
26 23 Herbert Greenlee
h1. MicroBooNE UPS Products
27 23 Herbert Greenlee
28 23 Herbert Greenlee
* [[Overview of MicroBooNE UPS Products]]
29 24 Herbert Greenlee
* [[Batch Tools]]