geoschem / HEMCO

The Harmonized Emissions Component (HEMCO), developed by the GEOS-Chem Support Team.
https://hemco.readthedocs.io
Other
15 stars 32 forks source link

[QUESTION]How to translate the code in geoschem.run from SLURM to PBS #166

Closed jiaying002 closed 1 year ago

jiaying002 commented 1 year ago

My server uses PBS schedular, while the code provided (geoschem.run) was for SLURM. I tried translating the code from SLURM to PBS, but I failed. I cannot find all the code I need from google, and the one I found is still doubtful. It would be best if someone could guide me on where to find the translated version.

yantosca commented 1 year ago

Thanks for writing @jiaying002. Have you looked at this page? It is a pretty good description: https://www.marquette.edu/high-performance-computing/pbs-to-slurm.php

For SLURM we use e.g. #SBATCH -c 8 to request 8 cores. You can replace that with #PBS -l nodes=1:ppn=8, which will request 8 cores on 1 node.

Finally, in the PBS batch script, you'll have to change

export OMP_NUM_THREADS=$SLURM_CPUS_PER_TASK

to

export OMP_NUM_THREADS=8  # or however many cores you are using.
yantosca commented 1 year ago

Also tagging @Jourdan-He

lizziel commented 1 year ago

Hi @jiaying002, you could also take a look at the template run script for GCHP and adapt it for GEOS-Chem Classic. It includes PBS as one of the schedulers. See file here.

jiaying002 commented 1 year ago

Thank u!

jiaying002 commented 1 year ago

Hi, sorry for reopening this case. I tried to change the SLURM to PBS and here is the geoschem.run file I modified. geoschem.run.txt Then, I got an error like this: image I am wondering is there anything wrong with my code?

jiaying002 commented 1 year ago

Sorry for bothering you again. I have been struggling for days. Would you please give me some clues? @yantosca @lizziel

yantosca commented 1 year ago

@jiaying002: We are not as familiar with PBS as our cluster uses SLURM. Is there anyone at your institution who handles IT support?

stale[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. If there are no updates within 7 days it will be closed. You can add the "never stale" tag to prevent the Stale bot from closing this issue.

yantosca commented 1 year ago

Closing out this issue