Difference: AtlasDataAnalysis (140 vs. 141)

Revision 1412012-02-13 - 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: 1033 to 1033

At any point you can check that the a given steering file can be read by GlaNtp by using testSteerrv5.exe - found inside your GlaNtp package:

Changed:

<
<

./${GLANTPDIR}/bin/Linux2.6-GCC_4_1/testSteerrv5.exe

>
>

testSteerrv5.exe

Deleted:

<
<

Please note that the

Linux2.6-GCC_4_1

may change depending on your system architecture. It is set during the installation of GlaNtp, and can be checked with the command

echo $BFARCH

Another debugging script checks you have defined the processes correctly:

View topic | History: r161 < r160 < r159 < r158 | More topic actions...