Mismatch in nesting data in a subregion of the Gulf of Mexico

26 views
Skip to first unread message

Santiago Reynoso

unread,
Nov 26, 2022, 11:34:32 AM11/26/22
to HYCOM.org Forum
Hello all,

I am performing a 0.02 resolution run in a subregion of the Gulf of Mexico using binary files of a previous 0.04 resolution run in the Gulf of Mexico performed by me. And I am getting this error message:

  now initializing baro nesting fields ...
rdbaro_in: nest/archv.2018_274_00 ( 43008.00000)

bl_dpth
error in rdbaro_in - expected u_btrop



    timer statistics, processor    8 out of   12
   -----------------------------------------------

   xcaget   calls =      298   time =    0.00122   time/call =    0.00000410
   xcaput   calls =      681   time =    0.05939   time/call =    0.00008722
   xcsum    calls =        2   time =    0.00015   time/call =    0.00007594
   xcmaxr   calls =     1957   time =    0.17830   time/call =    0.00009111
   xctilr   calls =       69   time =    0.01875   time/call =    0.00027168
   zaio**   calls =     1683   time =    0.01468   time/call =    0.00000872
   zaiord   calls =      681   time =    1.18970   time/call =    0.00174699
   zaiowr   calls =      298   time =    0.18146   time/call =    0.00060894
   zaioIO   calls =      979   time =    0.00000   time/call =    0.00000000
   xc****   calls =        1   time =    0.51563   time/call =    0.51563215
   total    calls =        1   time =    2.34001   time/call =    2.34000993

I think the error is due to the differences in the structure of the binary files that I obtain from the previous run and the binary files of the consortium.

I attach an arcvh*.b file and the archs.input file of the subregion that I am using in this case.  

Could you give me any hint about how this should be done? I'm using the 2.3.01 version of the model.

Thanks in advance.
Santiago.
archv.2018_214_00.b
archs.input

Alan Wallcraft

unread,
Nov 27, 2022, 2:24:52 PM11/27/22
to HYCOM.org Forum, santiago.re...@gmail.com
I have updated forfun.F90 on GitHub to skip the oneta files that were causing your problem.

Alan.

Santiago Reynoso

unread,
Nov 29, 2022, 1:09:19 PM11/29/22
to HYCOM.org Forum, alan.wa...@hycom.org, Santiago Reynoso
Thank you Alan, your solution worked perfectly.

Best regards,

Santiago.
Reply all
Reply to author
Forward
0 new messages