Closed platipodium closed 2 years ago
This occurs inside SCHISM from the call schism_step(it)
in schism_esmf_cap
I do have similar error when using your ESMF build. But when I try to use my own ESMF 8_2_0 build (openmpi), this error is gone. However, another error came out when finalizing ESMF. See following:
20220606 141923.960 INFO PET00 schism_001 ran. 20220606 141923.977 INFO PET00 schism_001 finalizing ... 20220606 141923.977 ERROR PET00 ESMF_StateAPI.cppF90:2565 ESMF_StateGet Not found - no ESMF_Field found named: wind_x-velocity_in_10m_height 20220606 141923.977 ERROR PET00 schism_esmf_cap.F90:1111 Finalize Not found - SCHISM subroutine call returned error 20220606 141923.977 INFO PET00 Finalizing ESMF
The latter error
20220606 141923.977 ERROR PET00 schism_esmf_cap.F90:1111 Finalize Not found - SCHISM subroutine call returned error
is now taken care of by commit df9d76d and prior.
@danishyo (1) how do we proceed with the error in my build? (2) can you go past this point with your build?
The latter error
20220606 141923.977 ERROR PET00 schism_esmf_cap.F90:1111 Finalize Not found - SCHISM subroutine call returned error
is now taken care of by commit df9d76d and prior.
@danishyo (1) how do we proceed with the error in my build? (2) can you go past this point with your build?
Thanks! I re-test the code with my build, and now it pass with minor warning messages in PETs file.
20220606 173622.178 WARNING PET01 ESMF_StateRemove Scalar itemName argument is deprecated. Use itemNameList instead.
For (1), I don't have a good solution. I notice your build is based on 8.3beta with debug mode. Will this setting combine with beta version cause the effects?
The warning should be gone now with commit 69f2bb1
Beta versions should not cause the problem. I will try on other systems, as well. Please confirm that the results are correct from your test simulations.
Thanks! I can get the correct result from 69f2bb1, but same warning messages still exist in PETs (which is OK for me). ESMF 8.2.0 & 8.3.0 both works and deliver correct result without any problem. I also notice, if debug option is on in ESMF build (ESMF_BOPT=g), same IDRY_E error will come back.
this was a simple index error using j
instead of I
. Fixed in c6d0faf
@danishyo Can you reproduce this with openmpmi device in our current test setup? https://pad.gwdg.de/KCGp_zhZR1af8ArudGljPw