Running BayesWaveBurst with condor For this example, the top level script is condor_setup.sh. It takes a single argument - the gps time of your trigger. ./condor_setup.sh 1076894532.3 But, all the action happens in doit.sh. So, before you run condor_setup.sh open up doit.sh in your favorite editor, and edit the bayesWave command and frame type as needed. I think that's it! To check on your jobs while they are running, you can run: condor_q USERNAME You can also check the global state of condor with the same command: condor_q You can also monitor your jobs by monitoring the condor log, output, and error logs that appear in the output directory, e.g. tail -f <path-to-your-job>/condorOut.txt
Forked from
lscsoft / bayeswave
1747 commits behind, 478 commits ahead of the upstream repository.
Francesco Pannarale
authored
git-svn-id: https://svn.ligo.caltech.edu/svn/bayeswave/trunk@339 c56465c9-8126-4a4f-9d7d-ac845eff4865
Code owners
Assign users and groups as approvers for specific file changes. Learn more.