cmake build failure under few scenarios
Opened this issue · 3 comments
Describe the bug
Under few scenarios cmake build system fails.
- Missing dependency - METIS and ParMETIS libraries build from git repository require in addition GKlib.
- Unable to locate file -
mod_oasis.mod
cannot be located when runningFindOASOS.cmake
- Switch error -
OASIS
only allowsFLX0
(i.e., source termsST3
orST4
). Enhance build system to allow any combination of source terms when coupling with OASIS. - Switch error - switches for sea-state dependent air-sea fluxes
FLD1
andFLD2
require source termsST3
orST4
. Proposed solution is to move the namelist parameterALPHA0
(minimum charnock coefficient) to namelistFLD1
andFLD2
respectively.
@stefanzieger regarding missing dependency for METIS and PARMETIS, please follow instruction from the following link https://github.com/erdc/WW3/wiki/FAQs%E2%80%90page#how-to-install-Metis-and-Parmetis. We still use PARMETIS 4.3.0 and the recent version from its authoritative repo is not supported by WW3. Alternatively, you can use SCOTCH https://github.com/erdc/WW3/wiki/FAQs%E2%80%90page#how-to-install-scotch
@aliabdolali Thank you for highlighting instructions on how to use SCOTCH library. Reverting back to v7.0.3 worked for me. In v7.0.5 they changed the prefix for fortran libraries from "SCOTCH_" to "SCOTCHF". In WW3 this will cause a linker error in yowpdlibmain.F90: call SCOTCH_ParMETIS_V3_PartGeomKway
. SCOTCH documentation is not quite clear on how to set the fortran prefix. See 3.3 (Re)naming library objects. Something that will become an issue in future release.
@aliabdolali Thank you for highlighting instructions on how to use SCOTCH library. Reverting back to v7.0.3 worked for me. In v7.0.5 they changed the prefix for fortran libraries from "SCOTCH_" to "SCOTCHF". In WW3 this will cause a linker error in
yowpdlibmain.F90: call SCOTCH_ParMETIS_V3_PartGeomKway
. SCOTCH documentation is not quite clear on how to set the fortran prefix. See 3.3 (Re)naming library objects. Something that will become an issue in future release.
Happy to help. thanks @stefanzieger for pointing changes in new versions of SCOTCH.