ROMS and SWAN

[mathieu]

I post the message here since there is no ROMS and SWAN forum.
The file coupling_inlet_test.in give the impression that one can choose which variables are sent from roms to swan. That illusion is dispelled by the code section in waves_coupler.F:

Code: Select all

COMPDA(INDX,JWLV2)=TEMPMCT(IP,2)
COMPDA(INDX,JVX2)=TEMPMCT(IP,3)
COMPDA(INDX,JVY2)=TEMPMCT(IP,4)
COMPDA(INDX,JFRC2)=REAL(TEMPMCT(IP,5))

with the second dimension of TEMPMCT equal to the number of variables exported. Thus if less than 5 variables are exported (i.e. ubar, vbar, zeta, bath and ZO) then there is a segmentation fault. Maybe this requirements should be made more explicit.

[jcwarner]

For the roms-swan coupling the format of the coupling is different than originally designed. And i am sure it will change as new features are added. As a guideline, use the INLET_TEST as an example. I recommend that users select all the required fields to be exchanged, as shown in that test case. I just downloaded the trunk and the inlet_test app works.