Changeset 3856
- Timestamp:
- Jul 17, 2025, 6:17:01 PM (6 months ago)
- Location:
- trunk/LMDZ.MARS
- Files:
-
- 1 added
- 2 edited
-
changelog.txt (modified) (1 diff)
-
deftank/adastra/README (modified) (2 diffs)
-
deftank/adastra/run_year1 (added)
Legend:
- Unmodified
- Added
- Removed
-
trunk/LMDZ.MARS/changelog.txt
r3855 r3856 4924 4924 == 17/07/2025 == JBC 4925 4925 "initracer.F" is transformed into "initracer_mod.F90" (explicit module interface + Fortran 90 format). 4926 4927 == 17/07/2025 == JBC 4928 Addition of the "run_year1" file to launch jobs "year by year" instead of "month by month" for Adastra in the deftank folder. -
trunk/LMDZ.MARS/deftank/adastra/README
r3817 r3856 1 1 >> EXAMPLES FOR ADASTRA CLUSTER 2 Month by month: 2 3 Job "run_month1" runs a simulation for month #1 and then possibly launches 3 4 a job "run_month2" which runs a simulation for month #2 which then possibly 4 5 launches a job "run_month3" etc. 6 7 Year by year: 8 Job "run_year1" runs a simulation for year #1 and then possibly launches 9 a job "run_year2" which runs a simulation for year #2 which then possibly 10 launches a job "run_year3" etc. 5 11 6 12 >> Note that you might need to change in script "run0" the line … … 8 14 >> to match your case 9 15 10 >> You might also need to adapt "run_month1" if you run with less than 19216 >> You might also need to adapt "run_month1"/"run_year1" if you run with less than 192 11 17 cores (ie. 24 MPI times 8 OpenMP). 12 18 >> If using 192 cores then you should aslo have the companion script 13 19 adastra_cpu_binding.sh 14 >> alongside "run_month1" 20 >> alongside "run_month1" or "run_year1"
Note: See TracChangeset
for help on using the changeset viewer.
