New URL for NEMO forge!

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.
#2730 (Confusing coupling order - oasis send) – NEMO

Opened 3 years ago

Last modified 3 years ago

#2730 assigned Defect

Confusing coupling order - oasis send

Reported by: jcastill Owned by: systeam
Priority: low Milestone:
Component: TOP Version: v4.0.*
Severity: minor Keywords: coupling
Cc: timgrahan



In the file sbccp.F90, each field that can be exchanged via coupling has its own index. The order in which the fields are received via coupling is the same as fields index, but this is not true for the sent fields, as the order is hard coded in the routine sbc_cpl_snd. This can cause some confusion for users, which can easily create a deadlock condition, in particular in cases where several models are coupled to NEMO.


The index order of the oasis sent fields should be the same as the order in which the fields are coupled to increase clarity.


The index order and the coupling order should be rearranged so that fields being sent to the same model component are grouped together to avoid potential deadlocks and to increase clarity and usability. The proposed order is: atmosphere, atmosphere ice, waves, wave ice. The addition of new coupling fields should take this order into account.

Commit History (0)

(No commits)

Change History (1)

comment:1 Changed 3 years ago by nemo

  • Owner set to systeam
  • Status changed from new to assigned
Note: See TracTickets for help on using tickets.