Working forward chapters 11-15 #32
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I'd hope to get some thoughts/feedback and modification suggestions especially to the part I've written about modules/software on LUMI. I'm currently working with tutorials about LUMI-O, and will add this work-in-progress possibly later today. |
rkronberg
reviewed
Jul 30, 2024
| @@ -0,0 +1,35 @@ | |||
| # Terminal and Web interface | |||
|
|
|||
| (Should this page be combined with the 'prerequisities' page?) | |||
rkronberg
reviewed
Jul 30, 2024
| - Familiarize yourself with personal and project-specific disk areas and their quotas on the LUMI supercomputer. | ||
| - Learn how to share your files, such as software installations and data, to other members of your LUMI project. | ||
| - Get to try out the disk area for I/O intensive workflows, i.e. frequent read and write operations | ||
|
|
||
| 💬 Each user of LUMI supercomputer has access to different disk areas (or directories) for managing their data. Each disk area has its own specific purpose. | ||
|
|
||
| 💬 Active data files needed for computational simulations and analyses should be stored and shared in directories under `/scratch`. For I/O heavy operations use `/flash` instead, which is a high performance variant of /scratch. Any software installations and binaries should be shared under the `/projappl` directory. | ||
| 💬 Active data files needed for computational simulations and analyses should be stored and shared in directories under `/scratch`. For I/O heavy operations use `/flash` instead, which is a high performance variant of /scratch. Any software installations and binaries should be shared under the `/project` directory. |
There was a problem hiding this comment.
Worthwhile mentioning NVMe on LUMI-D?
|
Converted this back to draft state. Going to separate the parts to different separate pull requests, for it to be easier to work on them |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm still working with these parts, so it's very much a draft at this point.