Opened 17 years ago
Closed 17 years ago
#154 closed bug (Fixed)
spec2d SWAN ifort
Reported by: | jcwarner | Owned by: | arango |
---|---|---|---|
Priority: | major | Milestone: | Release ROMS/TOMS 3.2 |
Component: | Coupling | Version: | 3.2 |
Keywords: | Cc: |
Description
Users reporting having trouble with the coupled ROMS-SWAN code when trying to allow swan to write out a 2D spectra output file. I have been able to duplicate this issue, but it only occurs with the ifort compiler (i am using 9.0.028) and not with pgi (6.1-6). Problem: in swanout1.F, the problem is at line (446 or so)
IVTYPE=CORQ%IVTYP(1)
When the user has a SPEC outfile, the pointer to IVTYP(1) is not defined. Apparently, pgi is ok with this but ifort fails. The var IVTYPE is not needed by the coupler for a SPEC output.
Suggested fix 1) modify swanout1.F, after the call to SWORD, add code to always define IVTYP:
IF (RTYPE(1:2) .EQ. 'SP') THEN
IVTYPE=500
ELSE
IVTYPE=CORQ%IVTYP(1)
END IF
(this change is in my branch, swanout1.F near lines 290-294).
2) in swanout1.F, remove line 446 IVTYPE=CORQ%IVTYP(1)
3)in swan_inlet_test.in add
POINTS 'point1' 5000.0 10000.0 SPECOUT 'point1' SPEC2D 'point1.spc2d' OUTPUT 20000101.000000 1 HR
so that this issue can be tested in future releases. In my branch, this is still file INPUT_inlet_test.
Change History (1)
comment:1 by , 17 years ago
Component: | Nonlinear → Coupling |
---|---|
Resolution: | → Fixed |
Status: | new → closed |
Summary: | spec2d swan ifort → spec2d SWAN ifort |