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

rose suite-run needs to know project name; $PROJECT #2238

Closed
jonnyhtw opened this issue Oct 1, 2018 · 6 comments
Closed

rose suite-run needs to know project name; $PROJECT #2238

jonnyhtw opened this issue Oct 1, 2018 · 6 comments

Comments

@jonnyhtw
Copy link

jonnyhtw commented Oct 1, 2018

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 which rose suite-run is launched but presumably this will preclude using the Rose GUI for launching suites from?

Any advise gratefully received!

Thanks

Jonny

@jonnyhtw jonnyhtw changed the title rose suite-run needs to know project name ($PROJECT) rose suite-run needs to know project name; $PROJECT Oct 1, 2018
@hjoliver
Copy link
Contributor

hjoliver commented Oct 1, 2018

@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.

@hjoliver
Copy link
Contributor

hjoliver commented Oct 1, 2018

For the Rose team:

# rose-suite.conf
[env]
PROJECT=foo

This gets exported before starting up cylc, but after symlinking the run directory.

Could the variable export just be done first?

@matthewrmshin
Copy link
Member

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.)

@matthewrmshin matthewrmshin self-assigned this Oct 1, 2018
@matthewrmshin matthewrmshin modified the milestones: next-release, soon Oct 1, 2018
@jonnyhtw
Copy link
Author

jonnyhtw commented Oct 1, 2018

Thanks Matt

@oliver-sanders
Copy link
Member

oliver-sanders commented Aug 9, 2021

Hi Jonny,

We have made some changes in the upcoming versions of Rose and Cylc (Rose 2 and Cylc 8):

  • rose suite-run is no more.
  • cylc install is now used to install workflows.
  • The Cylc [install][symlink dirs] config is now used to link the run dir (or bits of it) to specified location(s).
  • [install][symlink dirs] can be configured at the site or user level but not the workflow level.
  • (although a CLI override exists if you want to change it on a case by case basis).

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.

For Cylc 8 / Rose 2 bugs and feature requests:

  • For questions, discussions or if you are unsure feel free to drop in on Discourse.
  • If it relates to Cylc functionality (e.g. cylc install) please report to https://github.com/cylc/cylc-flow/
  • If it relates to Cylc / Rose interaction (e.g. rose-suite.conf) please report to https://github.com/cylc/cylc-rose/
  • If it relates to Rose functionality (e.g. rose app-run) please report it here.

@jonnyhtw
Copy link
Author

jonnyhtw commented Aug 9, 2021

Hi Jonny,

We have made some changes in the upcoming versions of Rose and Cylc (Rose 2 and Cylc 8):

  • rose suite-run is no more.
  • cylc install is now used to install workflows.
  • The Cylc [install][symlink dirs] config is now used to link the run dir (or bits of it) to specified location(s).
  • [install][symlink dirs] can be configured at the site or user level but not the workflow level.
  • (although a CLI override exists if you want to change it on a case by case basis).

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.

For Cylc 8 / Rose 2 bugs and feature requests:

  • For questions, discussions or if you are unsure feel free to drop in on Discourse.
  • If it relates to Cylc functionality (e.g. cylc install) please report to https://github.com/cylc/cylc-flow/
  • If it relates to Cylc / Rose interaction (e.g. rose-suite.conf) please report to https://github.com/cylc/cylc-rose/
  • If it relates to Rose functionality (e.g. rose app-run) please report it here.

Hey Oliver,

Thanks for this; sounds all good to me. Yes, I believe #2372 is related to duplicate functionalty.

All the best,

Jonny

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

5 participants