-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bilby saves the absolute outdir to the result object when a relative path is passed to run_sampler #815
Comments
In GitLab by @git.ligo:sylvia.biscoveanu on Aug 26, 2024, 17:04 It looks like this is intentional: https://git.ligo.org/lscsoft/bilby/-/blob/master/bilby/core/result.py?ref_type=heads#L469 |
In GitLab by @git.ligo:sylvia.biscoveanu on Aug 28, 2024, 20:02
|
In GitLab by @git.ligo:michael.williams on Sep 5, 2024, 14:04 I'm slightly confused by this, if a relative path is given and this code is executed on the remote note, won't the absolute path point to somewhere on that node?
|
In GitLab by @git.ligo:sylvia.biscoveanu on Sep 19, 2024, 01:59 Yes, that is exactly the issue I am running into. I'm running jobs on the OSG, which means that the outdir saved in the result object is some remote node directory to which I cannot write. It's possible that bilby_pipe has a hard-coded work-around to this. |
In GitLab by @git.ligo:sylvia.biscoveanu on Aug 26, 2024, 16:58
Regardless of whether an absolute or relative path is passed to
run_sampler
, bilby saves the absolute path toresult.outdir
. This causes issues when running on condor with OSG + file transfer, as the job running on a remote node is trying to write to a specific location on CIT that doesn't exist from its perspective.The text was updated successfully, but these errors were encountered: