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

Running on Titan with "sub-projects" #1398

Closed
mrnorman opened this issue Apr 21, 2017 · 2 comments
Closed

Running on Titan with "sub-projects" #1398

mrnorman opened this issue Apr 21, 2017 · 2 comments

Comments

@mrnorman
Copy link
Contributor

mrnorman commented Apr 21, 2017

I'm trying to run a case on Titan with a project called "csc190acme" (a sub-project of csc190), and it's failing.

The problem is that I need the case.run to use the queue option "-A csc190acme" while having the rest of ACME use the folder "/lustre/atlas/scratch/imn/csc190". If I set the PROJECT variable in env_batch.xml to csc190, then when I do ./case.submit, I get:

Submitting job script qsub -q debug -l walltime=01:00:00 -A csc190 case.run
ERROR: Command: 'qsub -q debug -l walltime=01:00:00 -A csc190 case.run ' failed with error ''

Yet, when I set PROJECT to csc190acme, I get:

ERROR: Could not make directory '/lustre/atlas/scratch/imn/csc190acme/FC5AV1C-L_ne16_mmf/run', error: [Errno 13] Permission denied: '/lustre/atlas/scratch/imn/csc190acme'

In the past, I was able to handle this by just changing the run script to have the full project name.

We need a means of specifying an appendage to the project so that ACME simultaneously uses the base project name for the folder and uses the full project name for the queue system.

@jedwards4b
Copy link
Contributor

I think that if you use the correct project code and the --output-root option to create_newcase you can get the configuration you are looking for.

@rljacob
Copy link
Member

rljacob commented Apr 22, 2017

This is a duplicate of #1332 but Jim's suggestion should work.

@rljacob rljacob closed this as completed Apr 22, 2017
jgfouca pushed a commit that referenced this issue Jun 2, 2017
This variable used to be set and was removed on 2017-03-16, because Intel v17 was failing when it was set. When it is not set, throughput with Edison's Intel v15 suffers.

Addresses #1387
[BFB]
jgfouca pushed a commit that referenced this issue Feb 23, 2018
This variable used to be set and was removed on 2017-03-16, because Intel v17 was failing when it was set. When it is not set, throughput with Edison's Intel v15 suffers.

Addresses #1387
[BFB]
jgfouca pushed a commit that referenced this issue Mar 13, 2018
This variable used to be set and was removed on 2017-03-16, because Intel v17 was failing when it was set. When it is not set, throughput with Edison's Intel v15 suffers.

Addresses #1387
[BFB]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants