klr324@psu_edu
New Member
I have successfully ported CESM1.0.3 on the systems at Penn State. I am using CESM1.0.3 for specific reasons rather than using the updated versions.I have successfully built and run the X, F, and I compsets without issue. The A, B, C, and D compsets also build successfully, but the model does not complete after submitting the job. In all cases I have tried running in DEBUG mode, with a smaller set of processors, with a single processor, and with running a the debugger dbx to determine the issue. The issue seems to be with MCT.For A, C, and D the model stops after initializing the atmosphere component and produces the following error in the ccsm.log:(seq_mct_drv) : Initialize each component: atm, lnd, ocn, and ice(seq_mct_drv) : Initialize atm component (ccsm log)MCT::m_AttrVect::exportRAttrDP_:: ERROR length of output array outVect less than length of aV. size(outVect)= 32, length of aV= 18048Traceback: |X|MCT::m_AttrVect::exportRAttrDP_000.MCT(MPEU)::die.: from MCT::m_AttrVect::exportRAttrDP_()application called MPI_Abort(MPI_COMM_WORLD, 2) - process 0 ==================================================================================== BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES= EXIT CODE: 2= CLEANING UP REMAINING PROCESSES= YOU CAN IGNORE THE BELOW CLEANUP MESSAGES=================================================================================== For B the model gets through the initialization step of the components, but stops later on and produces the following error in the ccsm.log:
CalcWorkPerBlock: Total blocks: 64 Ice blocks: 64 IceFree blocks: 0 Land blocks: 0MCT::m_Router::initp_: GSMap indices not increasing...Will correctMCT::m_Router::initp_: RGSMap indices not increasing...Will correctMCT::m_Router::initp_: RGSMap indices not increasing...Will correctMCT::m_Router::initp_: GSMap indices not increasing...Will correctMCT::m_Router::initp_: RGSMap indices not increasing...Will correctMCT::m_Router::initp_: GSMap indices not increasing...Will correctMCT::m_Router::initp_: GSMap indices not increasing...Will correctMCT::m_Router::initp_: RGSMap indices not increasing...Will correctMCT::m_SparseMatrixPlus:: FATAL--length of vector y different from row count of sMat.Length of y = 11600 Number of rows in sMat = 122880000.MCT(MPEU)::die.: from MCT::m_SparseMatrixPlus::initDistributed_()MCT::m_SparseMatrixPlus:: FATAL--length of vector y different from row count of sMat.Length of y = 11600 Number of rows in sMat = 122880038.MCT(MPEU)::die.: from MCT::m_SparseMatrixPlus::initDistributed_() Thanks in advance for any help provided,Kelsey
CalcWorkPerBlock: Total blocks: 64 Ice blocks: 64 IceFree blocks: 0 Land blocks: 0MCT::m_Router::initp_: GSMap indices not increasing...Will correctMCT::m_Router::initp_: RGSMap indices not increasing...Will correctMCT::m_Router::initp_: RGSMap indices not increasing...Will correctMCT::m_Router::initp_: GSMap indices not increasing...Will correctMCT::m_Router::initp_: RGSMap indices not increasing...Will correctMCT::m_Router::initp_: GSMap indices not increasing...Will correctMCT::m_Router::initp_: GSMap indices not increasing...Will correctMCT::m_Router::initp_: RGSMap indices not increasing...Will correctMCT::m_SparseMatrixPlus:: FATAL--length of vector y different from row count of sMat.Length of y = 11600 Number of rows in sMat = 122880000.MCT(MPEU)::die.: from MCT::m_SparseMatrixPlus::initDistributed_()MCT::m_SparseMatrixPlus:: FATAL--length of vector y different from row count of sMat.Length of y = 11600 Number of rows in sMat = 122880038.MCT(MPEU)::die.: from MCT::m_SparseMatrixPlus::initDistributed_() Thanks in advance for any help provided,Kelsey