Difference: AtlasDataAnalysis (113 vs. 114)

Revision 1142011-09-30 - AlistairGemmell

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
<-- p { margin-bottom: 0.21cm; }h1 { margin-bottom: 0.21cm; }h1.western { font-family: "Liberation Serif",serif; }h1.cjk { font-family: "DejaVu Sans"; }h1.ctl { font-family: "DejaVu Sans"; }h2 { margin-bottom: 0.21cm; }h4 { margin-bottom: 0.21cm; }h5 { margin-bottom: 0.21cm; }h3 { margin-bottom: 0.21cm; }h3.western { font-family: "Liberation Serif",serif; }h3.cjk { font-family: "DejaVu Sans"; }h3.ctl { font-family: "DejaVu Sans"; }pre.cjk { font-family: "DejaVu Sans",monospace; }a:link { } -->
Line: 196 to 196
 
  • The BASEBATCHDIR is now set automatically to the working directory when the script is executed.

Getting a copy of GlaNtp

Changed:
<
<
  • Set yourself up for access into SVN (e.g.

    svn proxy init

  • Create the directory where you want to set up your copy, and copy in the setup script:

>
>
  • Set yourself up for access into SVN

    svn proxy init

  • Create the directory where you want to set up your copy, and copy in the setup script:

 mkdir /home/ahgemmell/GlaNtp cd /home/ahgemmell/GlaNtp cp /home/stdenis/GlaNtpScript.sh .
Changed:
<
<
  • To avoid any potential problems with previously set up aliases etc, clear them all (you will need to do this during the running of the code, so you might as well copy it into your directory):

cp /home/stdenis/atlas/testGlaNtp/cleanpath3.sh
source cleanpath3.sh
>
>
  • You then need to set up your environment ready for the validation. This is done with the setup_glantp.sh script, which is available within the NNFitter package. I am aware of the tautology of getting a script from the package so you can get the package, but that's the way it is. Just download this one file and go from there - you can delete it later when you've got the whole thing. You run the script (which is also used for DebuggingTheCode) with

    source setup_glantp.sh
 
  • Make a directory to hold the code itself:

    mkdir GlaNtpPackage

Changed:
<
<
  • GlaNtpScript.sh not only checks out and compiles the code, it also then goes and validates it. You need to define the input for this:

export GLANTP_DATA=/data/cdf01/stdenis/GlaNtpData
>
>
  • GlaNtpScript.sh not only checks out and compiles the code, it also then goes and validates it. setup_glantp.sh sets up the environment variables so the validation data can be found.

 
  • You now run the script, specifying whether you want a specific tag (e.g. 00-00-10), or just from the head of the trunk (h) so you're more free to play around with it. It's always a good idea to check out a specific tag, so that whatever you do to the head, you can still run over a valid release.

./GlaNtpScript.sh SVN 00-00-10
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback