The OASIS Coupler Forum

  HOME

Messages in debug.* files

Up to Bugs and debugs

Posted by Anonymous at October 10 2013

Hi again,

Am I a pain already? If not, here is another question:

I get messages about missing variables in the debug.??.* files, but I'm not sure it's a real problem. The model continues (has other problems later) and the variables seem to be present in the restart files at the models start (lag is >0):

oasis_advance_init Field cplid :           1 TauXOce_
oasis_advance_init lag prism_ncoupler :        2700          21
oasis_advance_run  at        -2700           0  RRST: TauXOce_ TauXOce_
oasis_io_read_avfile:av2_TauXOce_:NetCDF: Variable not found
oasis_io_read_avfile model :           1  proc :           0
oasis_io_read_avfile:av3_TauXOce_:NetCDF: Variable not found
oasis_io_read_avfile model :           1  proc :           0
oasis_io_read_avfile:av4_TauXOce_:NetCDF: Variable not found
oasis_io_read_avfile model :           1  proc :           0
oasis_io_read_avfile:av5_TauXOce_:NetCDF: Variable not found
oasis_io_read_avfile model :           1  proc :           0
oasis_advance_run  at        -2700           0  PACK: TauXOce_ instant
oasis_advance_run  at        -2700           0  SEND: TauXOce_
diags:         TauXOce_    0.00000000000        0.00000000000  0.00000000000
oasis_advance_run  at        -2700           0  WRIT: TauXOce_
oasis_advance_run  at        -2700           0  KINF: TauXOce_           8

I see similar blocks for all coupling fields in the model. Can I ignore the messages and look for other problems?

Best regards,
Uwe.

PS: I really enjoy OASIS3-MCT compared to legacy OASIS3! API is nicer, debugging easier and it's good to get rid of the OASIS processes.
--
Uwe Fladrich

Posted by Anonymous at October 11 2013

Hi Uwe,

This is NOT a problem. I know this message is a pain.
We need to change the message, it is on our to-do list (https://inle.cerfacs.fr/issues/709) .

Thanks, Sophie
Reply to this