-
Notifications
You must be signed in to change notification settings - Fork 54
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
rose suite-run
needs to know project name; $PROJECT
#2238
Comments
rose suite-run
needs to know project name ($PROJECT)rose suite-run
needs to know project name; $PROJECT
@jonnyhtw - you can export the variable in a terminal before starting the GUI, and then run the suite from the GUI. However, this is slightly painful. |
For the Rose team:
This gets exported before starting up cylc, but after symlinking the run directory. Could the variable export just be done first? |
OK. I'll have a look at the logic to see if this is possible or not. (I can't see why not at the moment, but there may be subtle things that can cause issues.) |
Thanks Matt |
Hi Jonny, We have made some changes in the upcoming versions of Rose and Cylc (Rose 2 and Cylc 8):
This page gives a quick overview of the change: cylc 8.0b2 docs Closing this issue here as it is now outdated (but temporally leaving open #2372 which I think is a duplicate). Feel free to re-raise for Cylc 8 / Rose 2 if the new systems don't solve the problem.
|
Hey Oliver, Thanks for this; sounds all good to me. Yes, I believe #2372 is related to duplicate functionalty. All the best, Jonny |
Hi there
We have a new HPC system and our Cylc suite output data now goes here...
/some/base/location/$PROJECT/$USER
... whereas it used to go here...
/some/base/location/$USER
.Some users have multiple projects and hence defining
$PROJECT
in their~/.profile
(for example) doesn't make a lot of sense.A temporary solution would be to define
$PROJECT
in the terminal from whichrose suite-run
is launched but presumably this will preclude using the Rose GUI for launching suites from?Any advise gratefully received!
Thanks
Jonny
The text was updated successfully, but these errors were encountered: