Repository navigation
ToDO for TSMP on GitHub: remove JUWELS option fro step6 (Bugzilla Bug 62) #62
Description
This issue was created automatically with bugzilla2github
Bugzilla Bug 62
Date: 2020-02-12 18:12:05 +0100
From: Niklas Wagner <n.wagner@fz-juelich.de>
To: Abouzar Ghasemi, <a.ghasemi@fz-juelich.de>
CC: a.ghasemi@fz-juelich.de, n.wagner@fz-juelich.de
Last updated: 2020-02-12 18:22:29 +0100
Comment 104
Date: 2020-02-12 18:12:05 +0100
From: Niklas Wagner <n.wagner@fz-juelich.de>
During the 'QuickStart' (README.md) you build TSMP in step5 for JURECA only:
"./build_tsmp.ksh -v 3.1.0MCT -c clm-cos-pfl -m JURECA -O Intel"
But in step 6 you allow the user to set up the test-case for JURECA and JUWELS:
"To configure TSMP for the EURO-CORDEX test case experiment on JURECA machine (on JUWELS just change -m JURECA to -m JUWELS):
./setup_tsmp.ksh -v 3.1.0MCT -V cordex -m JURECA -I _cordex -O Intel"
Remove the option to set up the test-case for JUWELS and stick to JURECA only, because external user will struggle with this.
Activity
DCaviedesV commentedon Mar 3, 2023
This is still a valid point as far as I can see in the README.md
I agree it is best to only mention JUWELS. JURECA is mostly not available for external users. We can mention somewhere that the examples need to be changed to other machines names accordingly, but remove it from the general presentation.
Thoughts @niklaswr ?
niklaswr commentedon Mar 3, 2023
Agreed.
However, @s-poll is migrating the README to the new GitHub Pages based documentation and updating the README next week anyway. So I think this issue could be linked and resolved with this related PR.
DCaviedesV commentedon Mar 3, 2023
This sounds like a plan then.
kgoergen commentedon Mar 3, 2023
Ideally, the baseline install is for x86_64 using gcc; any specific HPC centre machines are merely an add-on, whether is is JUWELS or JURECA-DC, they are relevant for local users and should be mentioned, for sure, making the guideline relevant also for local users. The different built options (for the current TSMP without cmake) will be mentioned anyway somewhere in the user guide.
s-poll commentedon Mar 24, 2023
The originally raised problem is solved in #173 by using JUWELS consistently. I agree that it might be good to use generic_x86_64 for the getting_started. This discussion could be done in a new issue on the structure and content of the
getting starteddocumentation section.