Inlet_test and MCT coupler

Report or discuss software problems and other woes

Moderators: arango, robertson

Post Reply
Message
Author
DranixYu_YJM
Posts: 1
Joined: Mon Apr 09, 2018 4:35 pm
Location: Zhejiang Ocean University

Inlet_test and MCT coupler

#1 Post by DranixYu_YJM » Fri Nov 30, 2018 9:44 am

HI, I need to build coupling between ROMS and SWAN. And so I have been compiling INLET_TEST of ROMS with MCT. However, the errors occurred when I executed the command "./build.bash" in my own directory. The errors as follows:

cd /THL7/home/zjoujqy/Projects/coupling/Build_roms; /THL7/software/mvapich2-2.2-intel2016u3/bin/mpif90 -c -fp-model precise -ip -O3 -I/THL7/home/zjoujqy/MCT/include roms_import.f90
cd /THL7/home/zjoujqy/Projects/coupling/Build_roms; /THL7/software/mvapich2-2.2-intel2016u3/bin/mpif90 -c -fp-model precise -ip -O3 -I/THL7/home/zjoujqy/MCT/include coupler.f90
coupler.f90(18): error #7002: Error in opening the compiled module file. Check INCLUDE paths. [M_MCTWORLD]
USE m_MCTWorld, ONLY : MCTWorld_init => init
----------^
coupler.f90(47): error #7002: Error in opening the compiled module file. Check INCLUDE paths. [M_TRANSFER]
USE m_Transfer, ONLY: MCT_Send => send
----------^
coupler.f90(70): error #7002: Error in opening the compiled module file. Check INCLUDE paths. [M_MATATTRVECTMUL]
USE m_MatAttrVectMul, ONLY : MCT_MatVecMul => sMatAvMult
----------^
coupler.f90(23): error #7002: Error in opening the compiled module file. Check INCLUDE paths. [M_GLOBALSEGMAP]
USE m_GlobalSegMap, ONLY : GlobalSegMap
----------^
coupler.f90(31): error #7002: Error in opening the compiled module file. Check INCLUDE paths. [M_ATTRVECT]
USE m_AttrVect, ONLY : AttrVect
----------^
coupler.f90(41): error #7002: Error in opening the compiled module file. Check INCLUDE paths. [M_ROUTER]
USE m_Router, ONLY : Router
----------^
coupler.f90(52): error #7002: Error in opening the compiled module file. Check INCLUDE paths. [M_SPARSEMATRIX]
USE m_SparseMatrix, ONLY : SparseMatrix
----------^
coupler.f90(60): error #7002: Error in opening the compiled module file. Check INCLUDE paths. [M_SPARSEMATRIXPLUS]
USE m_SparseMatrixPlus, ONLY : SparseMatrixPlus
----------^
coupler.f90(81): error #6457: This derived type name has not been declared. [ATTRVECT]
TYPE(AttrVect) :: wav2ocn_AV ! AttrVect variables
-----------^
coupler.f90(82): error #6457: This derived type name has not been declared. [ATTRVECT]
TYPE(AttrVect) :: ocn2wav_AV
-----------^
coupler.f90(83): error #6457: This derived type name has not been declared. [ROUTER]
TYPE(Router) :: ROMStoSWAN ! Router variables
-----------^
coupler.f90(84): error #6457: This derived type name has not been declared. [GLOBALSEGMAP]
TYPE(GlobalSegMap) :: GSMapROMS ! GloabalSegMap variables
-----------^
coupler.f90(18): error #6581: Unresolved rename. [MCTWORLD_INIT]
USE m_MCTWorld, ONLY : MCTWorld_init => init
-----------------------------^
coupler.f90(19): error #6581: Unresolved rename. [MCTWORLD_CLEAN]
USE m_MCTWorld, ONLY : MCTWorld_clean => clean
-----------------------------^
coupler.f90(23): error #6580: Name in only-list does not exist. [GLOBALSEGMAP]
USE m_GlobalSegMap, ONLY : GlobalSegMap
---------------------------------^
coupler.f90(24): error #6581: Unresolved rename. [GLOBALSEGMAP_INIT]
USE m_GlobalSegMap, ONLY : GlobalSegMap_init => init
---------------------------------^
coupler.f90(25): error #6581: Unresolved rename. [GLOBALSEGMAP_LSIZE]
USE m_GlobalSegMap, ONLY : GlobalSegMap_lsize => lsize
---------------------------------^
coupler.f90(26): error #6581: Unresolved rename. [GLOBALSEGMAP_CLEAN]
USE m_GlobalSegMap, ONLY : GlobalSegMap_clean => clean
---------------------------------^
coupler.f90(27): error #6581: Unresolved rename. [GLOBALSEGMAP_ORDPNTS]
USE m_GlobalSegMap, ONLY : GlobalSegMap_Ordpnts => OrderedPoints
---------------------------------^
coupler.f90(31): error #6580: Name in only-list does not exist. [ATTRVECT]
USE m_AttrVect, ONLY : AttrVect
-----------------------------^
coupler.f90(32): error #6581: Unresolved rename. [ATTRVECT_INIT]
USE m_AttrVect, ONLY : AttrVect_init => init
-----------------------------^
coupler.f90(33): error #6581: Unresolved rename. [ATTRVECT_ZERO]
USE m_AttrVect, ONLY : AttrVect_zero => zero
-----------------------------^
coupler.f90(34): error #6581: Unresolved rename. [ATTRVECT_LSIZE]
USE m_AttrVect, ONLY : AttrVect_lsize => lsize
-----------------------------^
coupler.f90(35): error #6581: Unresolved rename. [ATTRVECT_CLEAN]
USE m_AttrVect, ONLY : AttrVect_clean => clean
-----------------------------^
coupler.f90(36): error #6581: Unresolved rename. [ATTRVECT_IMPORTRATTR]
USE m_AttrVect, ONLY : AttrVect_importRAttr => importRAttr
-----------------------------^
coupler.f90(37): error #6581: Unresolved rename. [ATTRVECT_EXPORTRATTR]
USE m_AttrVect, ONLY : AttrVect_exportRAttr => exportRAttr
-----------------------------^
coupler.f90(41): error #6580: Name in only-list does not exist. [ROUTER]
USE m_Router, ONLY : Router
---------------------------^
coupler.f90(42): error #6581: Unresolved rename. [ROUTER_INIT]
USE m_Router, ONLY : Router_init => init
---------------------------^
coupler.f90(43): error #6581: Unresolved rename. [ROUTER_CLEAN]
USE m_Router, ONLY : Router_clean => clean
---------------------------^
coupler.f90(47): error #6581: Unresolved rename. [MCT_SEND]
USE m_Transfer, ONLY: MCT_Send => send
----------------------------^
coupler.f90(675): catastrophic error: Too many errors, exiting
compilation aborted for coupler.f90 (code 1)
make: *** [/THL7/home/zjoujqy/Projects/coupling/Build_roms/coupler.o] Error 1

I think it could be due to the problem of my MCT installation. And there could be some libraries or files to fail being founded. But now I'm wondering how I should do.
Attachments
build.bash
This is my build.bash file to try to build INLET_TEST application of ROMS
(18.38 KiB) Downloaded 45 times

jcwarner
Posts: 816
Joined: Wed Dec 31, 2003 6:16 pm
Location: USGS, USA

Re: Inlet_test and MCT coupler

#2 Post by jcwarner » Sat Dec 01, 2018 2:16 am

looks like the compiler can not find your mct libraries. I have some explanation to build MCT in the coawst manual. Then you need to set MCT_INCDIR and MCT_LIBDIR, as described in the manual. give that a try and see if it helps.
-j

Post Reply