pvelissariou1
commented
1 year ago @Ufuk Turuncoglu @.***> Yes, this is the idea to have CDEPS handle everything. Can CDEPS read the input data (data + mesh) and do the process downloading->interpolating on the fly? What pre-processing steps are required from us (if any) before involving CDEPS?
Panagiotis Velissariou, Ph.D., P.E. UCAR Scientist National Ocean and Atmospheric Administration National Ocean Service Office of Coast Survey CSDL/CMMB Physical Scientist - Project Lead cell: (205) 227-9141 email: @.***
On Tue, Feb 21, 2023 at 11:43 AM Ufuk Turunçoğlu @.***> wrote:
@pvelissariou1 https://github.com/pvelissariou1 Okay. That is great. If I could create mesh file for the original data file then CDEPS will handle rest.
— Reply to this email directly, view it on GitHub https://github.com/noaa-ocs-modeling/CoastalApp/issues/156#issuecomment-1438870407, or unsubscribe https://github.com/notifications/unsubscribe-auth/APC7TP7HVFVXEJM7YN5TEPTWYT5CFANCNFSM6AAAAAAULPOB2Y . You are receiving this because you were mentioned.Message ID: @.***>
uturuncoglu
Ufuk Turuncoglu to Saeed, me, Daniel | to Saeed, me, Daniel to Saeed, me, Daniel
Ufuk Turuncoglu Jan 27, 2023, 1:16 PM (3 days ago) to Saeed, me, Daniel
Hi All,
I am following steps in
https://github.com/noaa-ocs-modeling/CoastalApp-testsuite
to run the tests. I am getting following error when I try to compile the model on Cheyenne. It seems that we have module files under modulefiles/ directory.
./build.sh --compiler intel --platform cheyenne --component "atmesh pahm adcirc ww3" -y envmodules_intel.cheyenne :: This environment is either not configured or not supported Exiting ...
Anyway, I just want to let you know. If you have no idea why it is not working I could try to fix it but I just want o ask you first. I also tried with gnu and it is not working too. Any idea? I could also try on Orion if you want.
Regards,
—ufuk
Ufuk Turuncoglu Jan 27, 2023, 1:17 PM (3 days ago) to Saeed, me, Daniel
Do i also need to follow the steps in compile-NEMS.x.txt (under CoastalApp directory)?
—ufuk
Panagiotis Velissariou - NOAA Affiliate panagiotis.velissariou@noaa.gov Jan 27, 2023, 1:29 PM (3 days ago) to Ufuk, Saeed, Daniel
Ufuk hi,
I haven't configured CoastalApp for "cheyenne" because I don't have access to this platform. What you can do is go into CoastalApp/modulefiles, copy the hera modulefiles to cheyenne and modify them according to cheyenne's module configuration. I think it will be better if we could have a chat (google meet) to discuss details. Are you free today?
Takis
Panagiotis Velissariou, Ph.D., P.E. UCAR Scientist National Ocean and Atmospheric Administration National Ocean Service Office of Coast Survey CSDL/CMMB Physical Scientist - Project Lead cell: (205) 227-9141 email: panagiotis.velissariou@noaa.gov
Ufuk Turuncoglu Jan 27, 2023, 1:36 PM (3 days ago) to me, Saeed, Daniel
Hi,
I have just comment you the section in the module file (for Cheyenne, Intel) that causes issue. Now I am trying to build and see how it goes. If that won’t work I’ll try your suggestion and use Hera one as a base. I’ll let you know if I need help about it and then we could have a chat. Is there any other platform that is tested regularly such as Orion?
Thanks for your help,
—ufuk
Ufuk Turuncoglu Jan 27, 2023, 1:38 PM (3 days ago) to me, Saeed, Daniel
BTW, which Here module is the best one for Intel compiler. I could see multiple under module files/ directory. Thanks.
—ufuk
On Jan 27, 2023, at 12:29 PM, Panagiotis Velissariou - NOAA Affiliate [panagiotis.velissariou@noaa.gov](mailto:panagiotis.velissariou@noaa.gov) wrote:
Panagiotis Velissariou - NOAA Affiliate panagiotis.velissariou@noaa.gov Jan 27, 2023, 1:49 PM (3 days ago) to Ufuk
envmodules_intel.hera is the file currently used. Basically the code in all modulefiles is the same, only the modules that are loaded are different between platforms. Could you please load the module manually and send me what NETCDF and HDF environment variables are set?
Takis
Panagiotis Velissariou, Ph.D., P.E. UCAR Scientist National Ocean and Atmospheric Administration National Ocean Service Office of Coast Survey CSDL/CMMB Physical Scientist - Project Lead cell: (205) 227-9141 email: panagiotis.velissariou@noaa.gov
Ufuk Turuncoglu Jan 27, 2023, 3:11 PM (3 days ago) to me
Hi,
I did following,
cc = mpicc cxx = mpicxx
To
if [[ -z "${CC}" ]]; then cc = mpicc else cc = ${CC} fi if [[ -z "${CXX}" ]]; then cxx = mpicxx else cxx = ${CXX} fi
Since the variables can be provided by the environment variables.
module purge module load cmake/3.22.0 module load ncarenv/1.3 module load intel/2022.1 module load mpt/2.25 module load ncarcompilers/0.5.0 module use /glade/work/epicufsrt/GMTB/tools/intel/2022.1/hpc-stack-v1.2.0_6eb6/modulefiles/stack module load hpc/1.2.0 module load hpc-intel/2022.1 module load hpc-mpt/2.25 export CC=mpicc export PCC=mpicc export CXX=mpicxx export PCXX=mpicxx export FC=mpif90 module load zlib/1.2.11 module load hdf5/1.10.6 module load netcdf/4.7.4 module load pio/2.5.7 module load esmf/8.3.0b09
When I run the script using following command,
./build.sh --compiler intel --platform cheyenne --component "atmesh pahm adcirc ww3" --tp parmetis -y
I am getting following error,
make[1]: Leaving directory '/glade/scratch/turuncu/COASTAL_APP/CoastalApp-testsuite/CoastalApp/thirdparty_open/parmetis/metis/build/Linux-x86_64' Makefile:11: *** missing separator. Stop. ERROR:: compileMetis (main): called from: functions_build the configuration of the ParMETIS library source failed tried to run the make command as: make config CC=mpicc CXX=mpicxx cc=mpicc cxx=mpicxx CFLAGS= CONFIG_FLAGS1=-DCMAKE_C_FLAGS='"-DIDXTYPEWIDTH=32 -DREALTYPEWIDTH=32"' gklib_path=/glade/scratch/turuncu/COASTAL_APP/CoastalApp-testsuite/CoastalApp/thirdparty_open/parmetis/metis/GKlib metis_path=/glade/scratch/turuncu/COASTAL_APP/CoastalApp-testsuite/CoastalApp/thirdparty_open/parmetis/metis prefix=/glade/scratch/turuncu/COASTAL_APP/CoastalApp-testsuite/CoastalApp/thirdparty_open/parmetis/del Exiting now …
I am still investigating. I’ll update you when I could compile the model then maybe you might want to push those changes to the main repository or I could create a branch and we could have a PR later.
—ufuk
Panagiotis Velissariou - NOAA Affiliate panagiotis.velissariou@noaa.gov Jan 27, 2023, 3:38 PM (3 days ago) to Ufuk
You don't need to modify any of these in the Makefile. All these are set by the build script. Check the file scripts/functions_build where there is a function compileMetis that defines all these variables and configures metis/parmetis properly. It should work in your case, if not please let me know the errors you are getting.
Takis
Panagiotis Velissariou, Ph.D., P.E. UCAR Scientist National Ocean and Atmospheric Administration National Ocean Service Office of Coast Survey CSDL/CMMB Physical Scientist - Project Lead cell: (205) 227-9141 email: panagiotis.velissariou@noaa.gov
Ufuk Turuncoglu Jan 29, 2023, 11:47 PM (12 hours ago) to me
Hi,
I past that issue but I am having another error as following,
-- Configuration on "cheyenne" waits verification. -- Found NetCDF: /glade/work/epicufsrt/GMTB/tools/intel/2022.1/hpc-stack-v1.2.0_6eb6/intel-2022.1/mpt-2.25/netcdf/4.7.4/include (found version "4.7.4") found components: C Fortran -- FindNetCDF defines targets: -- - NetCDF_VERSION [4.7.4] -- - NetCDF_PARALLEL [TRUE] -- - NetCDF_C_CONFIG_EXECUTABLE [/glade/work/epicufsrt/GMTB/tools/intel/2022.1/hpc-stack-v1.2.0_6eb6/intel-2022.1/mpt-2.25/netcdf/4.7.4/bin/nc-config] -- - NetCDF::NetCDF_C [STATIC] [Root: /glade/work/epicufsrt/GMTB/tools/intel/2022.1/hpc-stack-v1.2.0_6eb6/intel-2022.1/mpt-2.25/netcdf/4.7.4] Lib: /glade/work/epicufsrt/GMTB/tools/intel/2022.1/hpc-stack-v1.2.0_6eb6/intel-2022.1/mpt-2.25/netcdf/4.7.4/lib/libnetcdf.a -- - NetCDF_Fortran_CONFIG_EXECUTABLE [/glade/work/epicufsrt/GMTB/tools/intel/2022.1/hpc-stack-v1.2.0_6eb6/intel-2022.1/mpt-2.25/netcdf/4.7.4/bin/nf-config] -- - NetCDF::NetCDF_Fortran [STATIC] [Root: /glade/work/epicufsrt/GMTB/tools/intel/2022.1/hpc-stack-v1.2.0_6eb6/intel-2022.1/mpt-2.25/netcdf/4.7.4] Lib: /glade/work/epicufsrt/GMTB/tools/intel/2022.1/hpc-stack-v1.2.0_6eb6/intel-2022.1/mpt-2.25/netcdf/4.7.4/lib/libnetcdff.a CMake Error at cmake/check_netcdf.cmake:143 (message): The NetCDF library specified is not compatible with the specified compilers.It will not be enabled. Specify a different path or disable NetCDF.Ensure that you specify the same compilers to build PAHM as were used to build the NetCDF library.
Call Stack (most recent call first): CMakeLists.txt:238 (include)
-- Configuring incomplete, errors occurred!
and then
pahm_mod.F90(15): error #7002: Error in opening the compiled module file. Check INCLUDE paths. [PAHM_MESH] USE PaHM_Mesh ------^ pahm_mod.F90(107): error #6404: This name does not have a type, and must have an explicit type. [NP] theData%numNd = np --------------------^ pahm_mod.F90(108): error #6404: This name does not have a type, and must have an explicit type. [NE] theData%numEl = ne --------------------^ pahm_mod.F90(122): error #6404: This name does not have a type, and must have an explicit type. [SLAM] theData%ndCoords((iCnt - 1) nDims + 1) = slam(iCnt) -------------------------------------------------^ pahm_mod.F90(123): error #6404: This name does not have a type, and must have an explicit type. [SFEA] theData%ndCoords((iCnt - 1) nDims + 2) = sfea(iCnt) -------------------------------------------------^ pahm_mod.F90(130): error #6404: This name does not have a type, and must have an explicit type. [NM] theData%elConnect((iCnt - 1) * numFaceEl + 1) = nm(iCnt, 1) ------------------------------------------------------^ pahm_mod.F90(136): error #6404: This name does not have a type, and must have an explicit type. [DP] theData%bathymetry = dp -------------------------^ compilation aborted for pahm_mod.F90 (code 1)
It seems that those parameters (i.e., np) is defined in PAHM/src/mesh.F90 and it needs to be compiled before pahm_mod.F90. Maybe it is because if netcdf issue, not sure.
At this point I put following to modulefiles/envmodules_intel.cheyenne (trying to use exact modules used for UFS),
module load cmake/3.22.0 module load ncarenv/1.3 module load intel/2022.1 module load mpt/2.25 module load ncarcompilers/0.5.0 module use /glade/work/epicufsrt/GMTB/tools/intel/2022.1/hpc-stack-v1.2.0_6eb6/modulefiles/stack module load hpc/1.2.0 module load hpc-intel/2022.1 module load hpc-mpt/2.25 export CC=mpicc export PCC=mpicc export CXX=mpicxx export PCXX=mpicxx export FC=mpif90 export F90=mpif90 export PFC=mpif90 export PF90=mpif90 module load zlib/1.2.11 module load hdf5/1.10.6 module load netcdf/4.7.4 module load pio/2.5.7 module load esmf/8.3.0b09
So, maybe there are some restriction in CostallApp side in terms of module versions. In my case, I am using exact modules and netcdf needs to be consistent with compiler. Maybe there is something in PHMS side. I’ll try to find the source. In the meantime, if you have any suggestion just let me know.
Thanks,
—ufuk
Panagiotis Velissariou - NOAA Affiliate panagiotis.velissariou@noaa.gov 9:00 AM (3 hours ago) to Ufuk
Hi Ufuk,
I have fixed these issues, there was a conflict with the schism model. Let me update the github repo and I'll let you know.
Takis
Panagiotis Velissariou, Ph.D., P.E. UCAR Scientist National Ocean and Atmospheric Administration National Ocean Service Office of Coast Survey CSDL/CMMB Physical Scientist - Project Lead cell: (205) 227-9141 email: panagiotis.velissariou@noaa.gov
Panagiotis Velissariou - NOAA Affiliate panagiotis.velissariou@noaa.gov 10:15 AM (2 hours ago) to Ufuk
Hi,
Please clone the develop-updates branch for the time being: git clone --recurse-submodules https://github.com/noaa-ocs-modeling/CoastalApp.git -b develop-updates
With this branch and your module file, it should compile on cheyenne. Please let me know.
Takis
Panagiotis Velissariou, Ph.D., P.E. UCAR Scientist National Ocean and Atmospheric Administration National Ocean Service Office of Coast Survey CSDL/CMMB Physical Scientist - Project Lead cell: (205) 227-9141 email: panagiotis.velissariou@noaa.gov
Ufuk Turuncoglu 10:43 AM (1 hour ago) Thanks for the quick fix. I’ll try and let you know.
Ufuk Turuncoglu 10:58 AM (1 hour ago) to me
Hi Again,
I am still getting same error with your branch,
-- - NetCDF::NetCDF_Fortran [STATIC] [Root: /glade/work/epicufsrt/GMTB/tools/intel/2022.1/hpc-stack-v1.2.0_6eb6/intel-2022.1/mpt-2.25/netcdf/4.7.4] Lib: /glade/work/epicufsrt/GMTB/tools/intel/2022.1/hpc-stack-v1.2.0_6eb6/intel-2022.1/mpt-2.25/netcdf/4.7.4/lib/libnetcdff.a CMake Error at cmake/check_netcdf.cmake:143 (message): The NetCDF library specified is not compatible with the specified compilers.It will not be enabled. Specify a different path or disable NetCDF.Ensure that you specify the same compilers to build PAHM as were used to build the NetCDF library.
Call Stack (most recent call first): CMakeLists.txt:238 (include)
-- Configuring incomplete, errors occurred! See also "/glade/scratch/turuncu/COASTAL_APP/CoastalApp-testsuite/CoastalApp/PAHM/build/CMakeFiles/CMakeOutput.log". Couldn't run "make" due to "cmake" errors. make[1]: Entering directory '/glade/scratch/turuncu/COASTAL_APP/CoastalApp-testsuite/CoastalApp/PAHM/nuopc'
mpif90 -c -g -traceback -fp-model precise -fPIC -O2 -fPIC -assume realloc_lhs -m64 -mcmodel=small -pthread -threads -qopenmp -I/glade/work/epicufsrt/GMTB/tools/intel/2022.1/hpc-stack-v1.2.0_6eb6/intel-2022.1/mpt-2.25/esmf/8.3.0b09/mod -I/glade/work/epicufsrt/GMTB/tools/intel/2022.1/hpc-stack-v1.2.0_6eb6/intel-2022.1/mpt-2.25/esmf/8.3.0b09/include -I/glade/work/epicufsrt/GMTB/tools/intel/2022.1/hpc-stack-v1.2.0_6eb6/intel-2022.1/mpt-2.25/netcdf/4.7.4/include -DESMF_NO_INTEGER_1_BYTE -DESMF_NO_INTEGER_2_BYTE -DESMF_VERSION_STRING_GIT='v8.3.0b09' -DESMF_MOAB=1 -DESMF_LAPACK=1 -DESMF_LAPACK_INTERNAL=1 -DESMF_NO_ACC_SOFTWARE_STACK=1 -DESMF_NETCDF=1 -DESMF_YAMLCPP=1 -DESMF_YAML=1 -DESMF_PIO=1 -DESMF_MPIIO -DESMF_NO_OPENACC -DESMF_BOPT_O -DESMF_TESTCOMPTUNNEL -DSx86_64_small=1 -DESMF_OS_Linux=1 -DESMF_COMM=mpt -DESMF_DIR=/glade/work/jongkim/stacks/hash/hpc-stack-esmf/pkg/v8.3.0b09 -I/glade/work/epicufsrt/GMTB/tools/intel/2022.1/hpc-stack-v1.2.0_6eb6/intel-2022.1/mpt-2.25/netcdf/4.7.4/include -I. -I/glade/scratch/turuncu/COASTAL_APP/CoastalApp-testsuite/CoastalApp/PAHM_INSTALL -I/glade/scratch/turuncu/COASTAL_APP/CoastalApp-testsuite/CoastalApp/PAHM_INSTALL/include -L/glade/work/epicufsrt/GMTB/tools/intel/2022.1/hpc-stack-v1.2.0_6eb6/intel-2022.1/mpt-2.25/netcdf/4.7.4/lib -L. -L/glade/scratch/turuncu/COASTAL_APP/CoastalApp-testsuite/CoastalApp/PAHM_INSTALL -L/glade/scratch/turuncu/COASTAL_APP/CoastalApp-testsuite/CoastalApp/PAHM_INSTALL/lib -DWITHPETLISTS_on -DESMF_VERSION_MAJOR=8 pahm_mod.F90 pahm_mod.F90(15): error #7002: Error in opening the compiled module file. Check INCLUDE paths. [PAHM_MESH] USE PaHM_Mesh ------^ pahm_mod.F90(107): error #6404: This name does not have a type, and must have an explicit type. [NP] theData%numNd = np --------------------^ pahm_mod.F90(108): error #6404: This name does not have a type, and must have an explicit type. [NE] theData%numEl = ne --------------------^ pahm_mod.F90(122): error #6404: This name does not have a type, and must have an explicit type. [SLAM] theData%ndCoords((iCnt - 1) nDims + 1) = slam(iCnt) -------------------------------------------------^ pahm_mod.F90(123): error #6404: This name does not have a type, and must have an explicit type. [SFEA] theData%ndCoords((iCnt - 1) nDims + 2) = sfea(iCnt) -------------------------------------------------^ pahm_mod.F90(130): error #6404: This name does not have a type, and must have an explicit type. [NM] theData%elConnect((iCnt - 1) * numFaceEl + 1) = nm(iCnt, 1) ------------------------------------------------------^ pahm_mod.F90(136): error #6404: This name does not have a type, and must have an explicit type. [DP] theData%bathymetry = dp -------------------------^ compilation aborted for pahm_mod.F90 (code 1) Makefile:48: recipe for target 'pahm_mod.o' failed make[1]: [pahm_mod.o] Error 1 make[1]: Leaving directory '/glade/scratch/turuncu/COASTAL_APP/CoastalApp-testsuite/CoastalApp/PAHM/nuopc' /glade/scratch/turuncu/COASTAL_APP/CoastalApp-testsuite/CoastalApp/NEMS/src/incmake/component_PAHM.mk:30: recipe for target '/glade/scratch/turuncu/COASTAL_APP/CoastalApp-testsuite/CoastalApp/PAHM_INSTALL/pahm.mk' failed make: [/glade/scratch/turuncu/COASTAL_APP/CoastalApp-testsuite/CoastalApp/PAHM_INSTALL/pahm.mk] Error 2
—ufuk
Panagiotis Velissariou - NOAA Affiliate panagiotis.velissariou@noaa.gov 11:56 AM (26 minutes ago) to Ufuk
Hi,
Unfortunately CoastalApp does not work with the hpc-stack static libraries. Can you use the OS supplied libraries for NetCDF/HDF5 and ESMF so all dependencies are resolved? Let me check on hera to see what compiles in CoastalApp using hpc-stack. For sure ADCIRC can not be compiled using hpc-stack. It is in the to-do list to add the hpc-stack functionality in CoastalApp.
Takis
Panagiotis Velissariou, Ph.D., P.E. UCAR Scientist National Ocean and Atmospheric Administration National Ocean Service Office of Coast Survey CSDL/CMMB Physical Scientist - Project Lead cell: (205) 227-9141 email: panagiotis.velissariou@noaa.gov
Ufuk Turuncoglu 12:00 PM (21 minutes ago) to me
Thanks for your help. Okay. I could try with others frowned by the system. In any case we need to fix this issue to make components work under UFS since they are using theses modules. If you could make it work under Hera just let me know. One more question, I think set of libraries are used by CostallApp that could be part of hpc-stack. Could you list them for me? I know parmetis is one of them, which I think you don’t need to compile every time with the app itself and could be part of the hpc-stack (or spack-stack in the near future). Right?
—ufuk
Panagiotis Velissariou - NOAA Affiliate 12:15 PM (7 minutes ago) to Ufuk
ParMetis can not be part of hpc-stack due to licensing issues. We had this discussion with NCEP and it was decided that ParMetis can not be part of the official NOAA modeling infrastructure due to its license. This is the reason I have the ParMetis functionality in CoastalApp. Now, WW3 is moving away from ParMetis (I don't know when this will be done) and SCHISM has the capability to use an externally compiled ParMetis or NOT.
As long as you compiled ParMetis once in CoastalApp (it is installed in CoastalApp/THIRDPARTY_INSTALL) you can rerun the build.sh scripts as: PARMETISHOME=FULL_PATH_TO_CoastalApp/THIRDPARTY_INSTALL ./build.sh "your options" (without the --tp parmetis option) and CoastalApp will pick-up the installed ParMetis. Just make sure that all libraries, including ParMetis, are compiled using the same compilers and mpi libraries.
Takis
Panagiotis Velissariou, Ph.D., P.E. UCAR Scientist National Ocean and Atmospheric Administration National Ocean Service Office of Coast Survey CSDL/CMMB Physical Scientist - Project Lead cell: (205) 227-9141 email: panagiotis.velissariou@noaa.gov
Ufuk Turuncoglu 12:14 PM (7 minutes ago) to me
I also tried to do this to see why netcdf is failing. I write the INFO variables from Cmake build (add message(INFO ${NetCDF3_LOG}) to PAHM/cmake/check_netcdf.cmake) and it seems that it is failing like following,
Change Dir: /glade/scratch/turuncu/COASTAL_APP/CoastalApp-testsuite/CoastalApp/PAHM/build/CMakeFiles/CMakeTmp
Run Build Command(s):/usr/bin/gmake -f Makefile cmTC_95f2d/fast && gmake[1]: Entering directory '/glade/scratch/turuncu/COASTAL_APP/CoastalApp-testsuite/CoastalApp/PAHM/build/CMakeFiles/CMakeTmp' /usr/bin/gmake -f CMakeFiles/cmTC_95f2d.dir/build.make CMakeFiles/cmTC_95f2d.dir/build gmake[2]: Entering directory '/glade/scratch/turuncu/COASTAL_APP/CoastalApp-testsuite/CoastalApp/PAHM/build/CMakeFiles/CMakeTmp' Building Fortran object CMakeFiles/cmTC_95f2d.dir/netcdf3check.f90.o /glade/u/apps/ch/opt/ncarcompilers/0.5.0/intel/2022.1/mpi/mpif90 -I/glade/work/epicufsrt/GMTB/tools/intel/2022.1/hpc-stack-v1.2.0_6eb6/intel-2022.1/mpt-2.25/netcdf/4.7.4/include -extend-source 132 -heap-arrays 0 -fno-alias -sox -qno-opt-dynamic-align -O2 -debug minimal -nowarn -fp-model source -assume byterecl -mcmodel=medium -c /glade/scratch/turuncu/COASTAL_APP/CoastalApp-testsuite/CoastalApp/PAHM/build/CMakeFiles/netcdf3check.f90 -o CMakeFiles/cmTC_95f2d.dir/netcdf3check.f90.o gmake[2]: No rule to make target '/glade/work/epicufsrt/GMTB/tools/intel/2022.1/hpc-stack-v1.2.0_6eb6/intel-2022.1/mpt-2.25/netcdf/4.7.4/lib /glade/work/epicufsrt/GMTB/tools/intel/2022.1/hpc-stack-v1.2.0_6eb6/intel-2022.1/mpt-2.25/hdf5/1.10.6/lib -lhdf5_hl -lhdf5 /glade/work/epicufsrt/GMTB/tools/intel/2022.1/hpc-stack-v1.2.0_6eb6/intel-2022.1/zlib/1.2.11/lib -lz -ldl -lm -lnetcdf -lm', needed by 'cmTC_95f2d'. Stop. gmake[2]: Leaving directory '/glade/scratch/turuncu/COASTAL_APP/CoastalApp-testsuite/CoastalApp/PAHM/build/CMakeFiles/CMakeTmp' Makefile:127: recipe for target 'cmTC_95f2d/fast' failed gmake[1]: [cmTC_95f2d/fast] Error 2 gmake[1]: Leaving directory '/glade/scratch/turuncu/COASTAL_APP/CoastalApp-testsuite/CoastalApp/PAHM/build/CMakeFiles/CMakeTmp'
Then, I copy the code that test netcdf3 and run the command manually.
/glade/u/apps/ch/opt/ncarcompilers/0.5.0/intel/2022.1/mpi/mpif90 -I/glade/work/epicufsrt/GMTB/tools/intel/2022.1/hpc-stack-v1.2.0_6eb6/intel-2022.1/mpt-2.25/netcdf/4.7.4/include -extend-source 132 -heap-arrays 0 -fno-alias -sox -qno-opt-dynamic-align -O2 -debug minimal -nowarn -fp-model source -assume byterecl -mcmodel=medium -c netcdf3check.f90
and it compiled code without any issue. It is also same netcdf4 one.So, I am not sure why this is not working under CMake build. I think it is not related with the hpc-stack modules. Anyway, I’ll try the find the source of the issue.
—ufuk
Ufuk Turuncoglu 12:20 PM (2 minutes ago) to me
Hi,
Okay. It is good to know the background about the parmetis. This will help when we start to move the components to UFS. Thanks.
—ufuk