-
Notifications
You must be signed in to change notification settings - Fork 18
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
bugfix cluster_queue in SGE with queue='' as new default #393
Conversation
This commit does not set queue='' as default. We needed a way to override this, so I invented "NONE" as a special keyword to specify that no queue should be provided. With this commit, there is no way to override the hardcoded default so as to specify no queue. |
Although there is a hard-coded default That was changed from The
The best way to override this is with a
There is also a |
So at the moment we all have
Because we need to force no queue specification for submission to our cluster to work. Are you saying that if we set
That this will overwrite the |
Yes. In fact, if your
I think you can get rid of it after pulling these two PRs. |
As far as I can see, this is being set by adding something to the default ini file. Thus, as far as I can tell, it looks like it would only apply to either the standard pipelines, or to new pipelines developed from the new default pipeline.ini, but not to old pipelines. Also, will every one at CGAT now need a ~/.cgat file, specifying "all.q"? |
Yes, it is defined in the default ini file. Production pipelines will use that configuration, I am not sure about obsolete ones. I have reconfigured the job scheduler in CGAT so |
Perhaps it might be worth taking the hard coded "all.q" out of Parameters.py? |
Indeed, changing the hard-coded value from |
After refactoring the default value for
queue
in the defaultpipeline.ini
in #390 the SGE submission did not work properly.This pull request solves that issue.