Eric's instructions
To set up DOE grid cert on another machine when you already have the key:
Go to the LIGO Data Grid page, scroll down and find the most recent instructions for "Mac LSC DataGrid Client" (or whatever platform you are using).
Here are the most recent mac instructions as of May 28, 2012.
In order to follow these instructions, I had to remove this directory: /opt/ldg, which required that I log in as root:
sudo passwd root
su
I finished the rest of the instructions from my regular account.
When I was done, I put the following commands in my .bashrc file:
proxy () { grid-proxy-init ; }
grid=ldas-grid.ligo.caltech.edu
grid () { gsissh -YC $grid ; }
NOTE: you have to connect with gsissh.
Also: scp is replaced with gsiscp.
using SVN and CVS
obtain albert.einstein credentials (ask Vuk or Eric)
register an evo account
example startup.m file
strain sensitivity plots: noise_curves
running a coherence analysis: readme_coh.txt
FAQ
Is there anything special I need to know to run on ligo-wa or ligo-la?
Yes: if you are going to condor submit something, make sure *not* to source your matlab setup script upon logging in or it will confuse condor and commands like condor_submit won't work.
However, you still need to include the setup script in your condor.sh file.
I just downloaded a bunch of code from the svn repositories and now matlab is complaining about an "undefined function." How do I fix this?
1. you get an error about a undefined function called aaabbb.m
2. cd to where you keep your source code and type
find . -name aaabbb.m -print
3. Is anything returned? If so, then put the appropriate addpath
in your startup.m file in order to point to this code.
4. If nothing is returned, then probably you don't have the
required software and you need to download it from somewhere.
5. Relaunch matlab. Type "which aaabbb". If matlab is pointing
to the new code, it will say so.
running stochastic.m
running with time-shifted data:
doShift1 true
ShiftTime1 1
Max time shift may be <2 s due to frame buffer size; I get nonsense for 2.1 s.
duty cycle: S6 duty cycle plots
software injections:
doMonteCarlo true
numTrials 1
simOmegaRef 1
signalType const
Frames
verify a frame file: /opt/lscsoft/ldas-tools/bin/framecpp_verify --verbose
frame user guide: pdf
checking leap seconds:
> The easiest way is to use framecpp_dump_objects --silent-data
> and look at the FrameH structure. The two elements you will want to look
> at are the fields:
>
> GTimeS: This will be the GPS Start time of the frame in seconds.
> ULeapS: This will be the number of leap seconds.
>
> Using the two values, you should be able to tell if the ULeapS is valid.
Back to Resources