# New URL for NEMO forge! http://forge.nemo-ocean.eu

Since March 2022 along with NEMO 4.2 release, the code development moved to a self-hosted GitLab.
This present forge is now archived and remained online for history.
[BDY] Boundary Forcing files – Message List – Discussion – NEMO

# Skilled (#3) - [BDY] Boundary Forcing files (#55) - Message List

[BDY] Boundary Forcing files
solved

I am trying to run regional configuration with 3 open boundaries ("key_bdy") and 3 corresponding netcdf forcing files. When I try to run with the files included in my namelist, I get the following error in ocean.output:

iom_open ~

I've checked as many of the possible culprits as I could think of (typos, dimension sizes etc.) so any ideas would be appreciated.

The namelist and ocean.output files are attached.

• Message #185

Hi Mark, a t a first look, I think you should simply remove the ".nc" from the file names of bn_tem and bn_sal from the first instance of nambdy_dta, as you did for the other files.

See example below

....
bn_v3d  =    'amm12_bdyV_u3d' ,         24        , 'vomecrty' ,     .true.     , .false. ,  'daily'  ,    ''    ,   ''     , ''
bn_tem  =    'bdyd_t'         ,         -1        , 'votemper' ,     .true.     , .true. ,  'yearly'  ,    ''    ,   ''     , ''
bn_sal  =    'bdyd_s'         ,         -1        , 'vosaline' ,     .true.     , .true. ,  'yearly'  ,    ''    ,   ''     , ''
! for lim3
....
/

• Message #186

Hi Lovato, thanks very much for your response. I'm not sure how that ".nc" got there (probably a last desperate attempt!) but this is not the problem as I get the same error with or without the extension. Any other ideas would be much appreciated!

Best, Mark

• Message #197

Mark subject as resolved without further updates.