You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the general rule for the docs should be: Don't scare people into thinking this is too complex
As a reader with an above average attention span (there there people that are better than me but more that are worse) I would recommend to hide any complexity of EESSI in the documentation and basically have 3 main entry points:
Using EESSI by persona
1.1 Sysadmin (person with root): install packages and source the stuff in /etc/profiles.d
1.2. User: ask sysadmin to install packages and source yourself and/or put it in your profile
Want to know more (background info, policies, slurm clusters, etc ..... most things that people never read. Those also should be de-prioritized in the mkdocs-material searches so not confuse people
I find this quote explains it all:
"What if there was a way to avoid having to install a broad range of scientific software from scratch on every HPC cluster or cloud instance you use or maintain, without compromising on performance?"
The concept of easystack yaml files is probably a good idea but an entirely new concept to very infrequent users like me (just read about it today) . Is there not a way to autogenerate a yaml file in eb with default settings if i want to just submit a single easyconfig?
The text was updated successfully, but these errors were encountered:
I think the general rule for the docs should be: Don't scare people into thinking this is too complex
As a reader with an above average attention span (there there people that are better than me but more that are worse) I would recommend to hide any complexity of EESSI in the documentation and basically have 3 main entry points:
Using EESSI by persona
1.1 Sysadmin (person with root): install packages and source the stuff in /etc/profiles.d
1.2. User: ask sysadmin to install packages and source yourself and/or put it in your profile
contributing to EESSI : https://www.eessi.io/docs/adding_software/opening_pr/
Want to know more (background info, policies, slurm clusters, etc ..... most things that people never read. Those also should be de-prioritized in the mkdocs-material searches so not confuse people
I find this quote explains it all:
"What if there was a way to avoid having to install a broad range of scientific software from scratch on every HPC cluster or cloud instance you use or maintain, without compromising on performance?"
The concept of easystack yaml files is probably a good idea but an entirely new concept to very infrequent users like me (just read about it today) . Is there not a way to autogenerate a yaml file in eb with default settings if i want to just submit a single easyconfig?
The text was updated successfully, but these errors were encountered: