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

specifying output folder for singularity #49

Open
SebastianHollizeck opened this issue Sep 23, 2020 · 3 comments
Open

specifying output folder for singularity #49

SebastianHollizeck opened this issue Sep 23, 2020 · 3 comments

Comments

@SebastianHollizeck
Copy link

Hi,

i would love to use this through singularity in our HPC, but the issue is, that the program writes to the location of the python script, which errors out on the read-only filesystem singularity is based on.

I created a workaround with sandbox mode in singularity, but it would be amazing, if there was an option to specify the output location for the tool. So it can be more widely used.

Cheers,
Sebastian

@AAlhendi1707
Copy link

Same issue here

@pmitev
Copy link

pmitev commented Mar 22, 2022

I have changed line 17 in my container
from
filename = os.path.join(os.path.dirname(os.path.realpath(__file__)), 'phylogicndt.log')
to
filename = os.path.join(os.getcwd(), 'phylogicndt.log')

which writes the logfile in the current directory instead...
I am not sure if this is the only place where the code will write in the installation folder, though...

@bio937
Copy link

bio937 commented Sep 29, 2022

@SebastianHollizeck @AAlhendi1707 @pmitev

I encountered the same issue while trying to run PhylogicNDT inside a singularity container.

After changing that one line of code suggested by @pmitev, now it works when using the --help argument. Previously, it will show: IOError: [Errno 30] Read-only file system: Thank you so much! @pmitev

I first created singularity sandbox and changed that line of code, then converted the sandbox to Singularity Image Format (.sif)

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

4 participants