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

Adding instructions for the SLES15 Installation #379

Merged
merged 6 commits into from
Jul 8, 2024

Conversation

Dooruk
Copy link
Collaborator

@Dooruk Dooruk commented Jun 28, 2024

Documenting progress 📝

Also notice the change in the ~/bin/cylc file and ~./cylc folder.

Thank you @ashiklom for the SLURM config description!

@Dooruk Dooruk added documentation Improvements or additions to documentation ready for merge labels Jun 28, 2024
@Dooruk Dooruk changed the title Adding instructions for SLES15 Installation Adding instructions for the SLES15 Installation Jun 28, 2024
@Dooruk Dooruk linked an issue Jun 28, 2024 that may be closed by this pull request
Copy link

@DavidSRussell DavidSRussell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are a few things I didn't see mentioned here. To get an experiment to work, I know I had to:

  • Use swell create option -p nccs_discover_sles15
  • Make sure user has execute permission on $HOME/bin/cylc
  • Change existing_jedi_build_directory to /discover/nobackup/projects/gmao/advda/swell/JediBundles/fv3_soca_SLES15/build-intel-release in override.yaml
  • Change existing_jedi_source_directory to /discover/nobackup/projects/gmao/advda/swell/JediBundles/fv3_soca_SLES15 in override.yaml

and I'm guessing I also had to:

  • Change constraint to mil in $HOME/.swell/swell-slurm.yaml
  • Change platform to nccs_discover_sles15 in override.yaml

and I'm guessing $HOME/.cylc/flow/global.cylc is not an executable, so I don't need execute permission on that, right?

@Dooruk
Copy link
Collaborator Author

Dooruk commented Jul 5, 2024

Thank you so much for your feedback! I added more clarifications on different parts:

* Use `swell create` option `-p nccs_discover_sles15`

I added this in the "practical examples" description.

* Make sure user has execute permission on $HOME/bin/cylc

done

* Change `existing_jedi_build_directory` to `/discover/nobackup/projects/gmao/advda/swell/JediBundles/fv3_soca_SLES15/build-intel-release` in override.yaml 
* Change `existing_jedi_source_directory` to `/discover/nobackup/projects/gmao/advda/swell/JediBundles/fv3_soca_SLES15` in override.yaml

See the "practical examples" description. We define some of these default folders/builds under SWELL source codedeployment/platform/{platform} directories so one should first create a default experiment.yaml before accidentally overriding them.

* Change `constraint` to `mil` in $HOME/.swell/swell-slurm.yaml

We added slurm.yaml file for platform specific entries, see the "SLURM configuration" description.

* Change `platform` to `nccs_discover_sles15` in override.yaml

If you run swell create 3dvar -p nccs_discover_sles15 that is automatically taken care of but you are correct.

and I'm guessing $HOME/.cylc/flow/global.cylc is not an executable, so I don't need execute permission on that, right?

correct

@Dooruk Dooruk requested a review from DavidSRussell July 5, 2024 14:49
@Dooruk Dooruk merged commit a0600af into develop Jul 8, 2024
2 checks passed
@Dooruk Dooruk deleted the docs/sles15_installation branch July 8, 2024 21:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation ready for merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

SLES15 Documentation Updates
2 participants