Skip to content
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

Setting the locations for *.o and *.e files with Torque PBS and submit_file #82

Closed
Ox5f3759df opened this issue Nov 25, 2017 · 2 comments

Comments

@Ox5f3759df
Copy link

For torque systems and use of fyrd's submit_file method is it possible to specify where the .o and .e file gets placed?

I'm running my pbs script like such:

q = fyrd.Queue()
pid = submit_file(str(scriptlocation))
q.wait(pid)

The .o and .e files are being placed in PYTHONPATH location where I'm running the script as opposed to the scriptlocation

@MikeDacre
Copy link
Owner

Hm, I am not sure why that is happening, the default location is supposed to be the current working directory, and the code doesn't search the PYTHONPATH for anything, so something else must be happening, I am not sure what...

Where are they being placed exactly? Are they being placed alongside the code install directory?

You could try cloning the dev branch and installing from there, I have made a lot of changes in dev, it is possible that it isn't an issue there.

As a workaround, you can explicitly set the scriptpath keyword, or the runpath, by default runpath is used for scriptpath if both are not set.

For more information on the available keywords, you can read the docs here: http://fyrd.readthedocs.io/en/latest/keywords.html

@Ox5f3759df
Copy link
Author

Yeah it was being placed alongside the code install directory.

I'll look into the scriptpath and runpath keywords at a later stage depending on how much I use fyrd, for now I've explicitly put the -e and -o directories within my pbs script as a workaround.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants