Running WW3/ROMS and WW3 alone Sandy Case: issues

I have two issues,

1) **Can't run standalone WW3 with NOPA:** Trying to run the WW3-only Sandy test case. I pick 'NOPA' instead of 'COAWST' in the switch file. When compiling, it says it couldn't read 'NOPA'.

> Exporting WWATCH3_ENV=/home/lfp33/coawst2/trunk/WW3/model/bin/wwatch3.env^M
> sort_switch: could not process all switches [ NOPA ] abort.^M

In switch_sandy I have:
`F90 NOGRB NOPA SCRIP SCRIPNC NC4 TRKNC DIST MPI PR3 UQ FLX0 LN1 ST4 STAB0 NL1 BT4 DB1 MLIM TR0 BS0 IC2 IS2 REF1 IG1 XX0 WNT2 WNX1 RWND CRT1 CRX1 TIDE O0 O1 O2 O2a O2b O2c O3 O4 O5 O6 O7`

2) **Coupled ROMS/SWAN crashes before running; points to input conversion error**

For the coupled Sandy ROMS/WW3, I have

`F90 NOGRB COAWST SCRIP SCRIPNC NC4 TRKNC DIST MPI PR3 UQ FLX0 LN1 ST4 STAB0 NL1 BT4 DB1 MLIM TR0 BS0 IC2 IS2 REF1 IG1 XX0 WNT2 WNX1 RWND CRT1 CRX1 TIDE O0 O1 O2 O2a O2b O2c O3 O4 O5 O6 O7`

I compile and get a coawstM. Then I run

- ww3_grid
- ww3_strt,
- ww3_prep

to get some WW3 pre-processing files. ROMS tiling 2x2. Node allocation: 4 ocean, 4 waves = 8 total. The wave input file is ww3_grid.inp. In ww3_shel.inp I have:

> $ -------------------------------------------------------------------- $
> $ WAVEWATCH III shell input file $
> $ -------------------------------------------------------------------- $
> $ Define input to be used with F/T/C flag for use or nor or coupling and
> $ T/F flag for definition as a homogeneous field.
> $
> $ Include ice and mud parameters only if IC1/2/3/4 used :
> C F Water levels
> C F Currents
> T F Winds

The weights scrip is: scrip_sandy_nowavenest.nc

The err.xxx file says
`forrtl: severe (64): input conversion error, unit 10` /sandy_ww3/WW3/./ww3_shel.inp

When I run coupling_sandy.in, the log file starts but then gets stuck (see below). What could be happening? is the resource allocation too little? I ran the ROMS_WW3 inlet case with 2 cpus and it worked.

end of log file:

> Process Information:
>
> Node # 0 (pid= 181361) is active.
> Node # 1 (pid= 181362) is active.
> Node # 2 (pid= 181363) is active.
> Node # 3 (pid= 181364) is active.
>
>

Start by reviewing the switch_sandy configuration and the WW3 entry points ww3_grid, ww3_strt, and ww3_prep. Then inspect ww3_shel.inp, coupling_sandy.in, and the reported err.xxx output to reproduce both the standalone and coupled runs. Done means identifying the configuration or input errors and documenting a reproducible fix for each case.

Written by the indexing model from the issue text.