Closed duncan-brown closed 8 years ago
@stevereyes01 please can you check that the instructions are up to date? I think all the relevant changes above have been made.
The instructions at: http://ligo-cbc.github.io/pycbc/latest/html/workflow/pycbc_make_coinc_search_workflow.html#running-on-the-open-science-grid
Are currently up to date and carry most of the information here. I'm running a test workflow to make sure we can run on OSG and the local cluster using the same pycbc_submit_dax. If these tests all succeed we can modify the instructions to the most modern settings (no perl-ing).
Once I get this to work I'll make sure everything works stably on pycbc 1.5.X.
Closing and opening a new ticket since most of this has been fixed. Will open a new ticket when @stevereyes01 tests against 1.5.x
So far, @lppekows has been hand-building an mixed executables ini file that points to some of the executables from the code.pycbc.phy.syr.edu server and some from his home directory. See e.g.
This has the code that runs on OSG downloadable from the server (at the moment this is just
pycbc_inspiral
since that's the only job we run on OSG) and all the other codes coming from${which:pycbc_average_psd}
. This also relies on the user making sure thatPATH
is set correctly before planning the workflow. I mounted the software repo as/opt/pycbc-software
so it should be possible to set up an ini file that has e.g.Really, this means adding an extra step to the build bundle instructions to create an second
executables.ini
file calledosg_executables.ini
for each release. This also needs to contain the linesto tell pegasus that
pycbc_inspiral
is not installed locally.If this is done, the instructions can just say to point to
osg_executables.ini
from the http server for a given release, and the instructions about setting the PATH can be delete.This is an XrootD URL and a file URL that is valid on Stampede.
Since these paths don't actually change, I think it makes sense to just check the C02 cache file into GitLab. Then change the instruction to tell the user to download the cache file from GitLab and use it instead.
as that is taken care of by using the new
osg_executables.ini
. However, make sure the build instructions say to add the correct lines to the ini file.because this should be controlled by the admin of the submitting site in the condor configuration.
to say to use the cache file downloaded from GitLab.
to contain URLs for the cache files.
hostname -f
a note and explain that this is setting--remote-staging-server
.as that is now set by default in https://github.com/ligo-cbc/pycbc/blob/master/bin/pycbc_submit_dax
as they are now set by default in https://github.com/ligo-cbc/pycbc/blob/master/pycbc/workflow/pegasus_files/pegasus-properties.conf
to set up the PFN fall-back mechanism until issue https://github.com/ligo-cbc/pycbc/issues/756 is fixed.
when doing
pycbc_submit_dax
to the OSG site in
output/site-catalog.xml
until https://github.com/ligo-cbc/pycbc/issues/757 is fixed.