Search found 27 matches
- Thu Nov 01, 2018 7:45 pm
- Forum: ROMS Usage
- Topic: How to generate contact netcdf?
- Replies: 7
- Views: 10560
Re: How to generate contact netcdf?
I have figured out my problem and successfully created the contact.nc. Moving on to run the model and test my grid setting!
- Thu Nov 01, 2018 3:05 pm
- Forum: ROMS Usage
- Topic: How to generate contact netcdf?
- Replies: 7
- Views: 10560
Re: How to generate contact netcdf?
I have created a child grid using the method that I had been using, which works fine for old version ROMS and COAWST. But the new model needs contact.nc. So initially, I tried this name = 'contact.nc'; c_contact(name,true,2) grd = {'parent_grd.nc','child_grd.nc'}; [S,G]=contact(grd,name); My error ...
- Thu Nov 01, 2018 2:54 pm
- Forum: ROMS Usage
- Topic: How to generate contact netcdf?
- Replies: 7
- Views: 10560
Re: How to generate contact netcdf?
Psi points? Do you mean lon_psi, lat_psi, mask_psi, x_psi, y_psi? My parent grid has all of these...
Thank you all for your prompt response!!! I really appreciate it!
Thank you all for your prompt response!!! I really appreciate it!
- Thu Nov 01, 2018 2:50 pm
- Forum: ROMS Usage
- Topic: How to generate contact netcdf?
- Replies: 7
- Views: 10560
Re: How to generate contact netcdf?
I used the exact same code: F=coarse2fine(Ginp,Gout,Gfactor,163,190,217,240); Ginp is my parent grid and Gout is my output child grid. This is my error message: Error using netcdflib The NetCDF library encountered an error during execution of 'getVaraDouble' function - 'Index exceeds dimension bound ...
- Wed Oct 31, 2018 6:49 pm
- Forum: ROMS Usage
- Topic: How to generate contact netcdf?
- Replies: 7
- Views: 10560
How to generate contact netcdf?
Hi, I have a model grid from years ago. And I need to generate a child grid and the corresponding contact netcdf file. The problem is the old model grid that I have is not created from the rutgers/grid tools. So when I use coarse2fine.m, it is not working. Can someone show me how to deal with this ...
- Wed Jun 06, 2018 12:11 am
- Forum: ROMS Bugs
- Topic: Abnormal temperature along the boundary
- Replies: 7
- Views: 5927
Re: Abnormal temperature along the boundary
I am running a pure tidal simulation. So the only input forcing that I am giving is the tide.nc in different tidal components. Everything else is using a default analytical solution from ROMS. In this case, where should I go to fix the temperature? Do you think it is the temperature that causes ...
- Tue Jun 05, 2018 11:23 pm
- Forum: ROMS Bugs
- Topic: Abnormal temperature along the boundary
- Replies: 7
- Views: 5927
Re: Abnormal temperature along the boundary
These are my open boundary conditions. LBC(isFsur) == Cha Cha Cha Cha ! free-surface LBC(isUbar) == Fla Fla Fla Fla ! 2D U-momentum LBC(isVbar) == Fla Fla Fla Fla ! 2D V-momentum LBC(isUvel) == Gra Gra Gra Gra ! 3D U-momentum LBC(isVvel) == Gra Gra Gra Gra ! 3D V-momentum LBC(isMtke) == Gra Gra Gra ...
- Tue Jun 05, 2018 11:07 pm
- Forum: ROMS Bugs
- Topic: Abnormal temperature along the boundary
- Replies: 7
- Views: 5927
Re: Abnormal temperature along the boundary
Hi Kate, Thank you for your prompt response! I was using LtracerSrc = T T, if this is what you mean by "must have tracers set". But I got abnormal temperature, current speed along an open east boundary, which is nowhere near the river discharge location. And I started to get this abnormal thing ...
- Tue Jun 05, 2018 10:28 pm
- Forum: ROMS Bugs
- Topic: Abnormal temperature along the boundary
- Replies: 7
- Views: 5927
Abnormal temperature along the boundary
Hi, I am running a tidal simulation with river discharge. On the day 30th, the model starts to show abnormal current speed, negative temperature along the east boundary. I don't expect to have any variation in temperature. I prefer it to be a constant. So I have changed the LtracerSrc == F T . Then ...
- Fri Feb 23, 2018 3:24 am
- Forum: ROMS Discussion
- Topic: Got an Error when compiling coawst.bash
- Replies: 6
- Views: 6472
Re: Got an Error when compiling coawst.bash
Hi Kate, Thanks again for the quick response! :) I really appreciate it! I have tried to re-compile MCT using ./configure and make install . I got this error when I ran make install . make[1]: Entering directory `/gpfs/pace1/project/pnjord1/txu68/COAWST_V33/Lib/MCT/mpeu' icc -c -DFORTRAN_UNDERSCORE ...
- Fri Feb 23, 2018 12:22 am
- Forum: ROMS Discussion
- Topic: Got an Error when compiling coawst.bash
- Replies: 6
- Views: 6472
Re: Got an Error when compiling coawst.bash
Hi Kate,
Thank you for your quick response!!!
I did make clean, but I still have the same error.
Are you suggesting that I delete m_mctworld.mod in the MCT include folder?
Best,
Amy
Thank you for your quick response!!!
I did make clean, but I still have the same error.
Are you suggesting that I delete m_mctworld.mod in the MCT include folder?
Best,
Amy
- Thu Feb 22, 2018 11:29 pm
- Forum: ROMS Discussion
- Topic: Got an Error when compiling coawst.bash
- Replies: 6
- Views: 6472
Got an Error when compiling coawst.bash
Hello, Thank you in advance. I am trying to compile coawst.bash using ifort and openmpi. This is the error I got cd /nv/hnjord1/txu68/scratch/ONR/HF_22m_north_coupled/bin/Build; /usr/local/pacerepov1/openmpi/1.8/intel-15.0/bin/mpif90 -c -heap-arrays -fp-model precise -ip -O3 -assume byterecl -I/nv ...
- Thu Feb 22, 2018 8:42 pm
- Forum: ROMS Discussion
- Topic: Is there a limit for the number of processors for model?
- Replies: 0
- Views: 1743
Is there a limit for the number of processors for model?
Hello All, I am running a Coupled ROMS and SWAN model through the COAWST system. Recently I have noticed that there seems to be a limit for how many processors to be used in SWAN. In my past experience, SWAN could be slower compared with ROMS. So I need more processors for SWAN. But the problem is I ...
- Tue Jan 23, 2018 4:39 am
- Forum: ROMS Discussion
- Topic: Boundary Flipped Problem
- Replies: 1
- Views: 1465
Boundary Flipped Problem
Hello, I am running a ROMS-SWAN coupled model using COAWST. Something very weird happened when I ran a new case today. When I loaded and plotted h from a history file, I found out that for some reason, the left side boundary depth has been flipped with the right side boundary depth. In my case, the ...
- Wed Oct 25, 2017 4:54 pm
- Forum: ROMS Discussion
- Topic: ROMS tidal forcing with water elevation ONLY
- Replies: 8
- Views: 9749
Re: ROMS tidal forcing with water elevation ONLY
Hello, I am working on a similar case, such that the real bathymetry is forced by tides only. I can get tidal constituents from ADCIRC and TPXO. I have activated #define SSH_TIDES #define UV_TIDES #define ANA_M2OBC #define ANA_FSOBC #define RAMP_TIDES I use ROMS and let the model run for 32 days ...
- Wed Mar 29, 2017 7:07 pm
- Forum: ROMS Usage
- Topic: Model blow-up with refined grid
- Replies: 1
- Views: 7628
Re: Model blow-up with refined grid
An update to this problem. I changed the model setting back to an old version of COAWST, the version does not require a contact file. And the cpp option for nesting is #define REFINED_GRID. The code I used to generate a nest grid is create_nested_grid.m instead of coarse2fine.m. With the child grid ...
- Wed Mar 29, 2017 5:31 am
- Forum: ROMS Usage
- Topic: Model blow-up with refined grid
- Replies: 1
- Views: 7628
Model blow-up with refined grid
Hello, I have tried to incorporate a nested grid in a complicated estuary region. The model works fine without a nested grid. And I tried to generate the nested grid file by using coarse2fine.m and generate the contact point information by contact.m. However, with the nested grid setting, the model ...
- Thu Mar 23, 2017 9:37 pm
- Forum: ROMS Usage
- Topic: DOGBONE in COAWST
- Replies: 1
- Views: 7702
DOGBONE in COAWST
Hello, I am trying to test the DOGBONE Refined Case in the COAWST system. The head file is #define ROMS_MODEL #define NESTING #define UV_ADV #define UV_QDRAG #define ANA_SMFLUX #define MASKING #ifdef SOLVE3D # define DJ_GRADPS # define SALINITY # define ANA_STFLUX # define ANA_SSFLUX # define ANA ...
- Fri Mar 10, 2017 4:40 pm
- Forum: ROMS Usage
- Topic: Model blow-up after adding river discharge
- Replies: 7
- Views: 9101
Re: Model blow-up after adding river discharge
In ocean.in, NAT = 2 I don't have any other tracers. You said they all needed to be specified in the inflow. I don't know how to set the values in ana_psource, except changing LtracerSrc = T T T T in ocean.in. I have looked up the blow up, but I don't see anything wield in salinity or temperature or ...
- Fri Mar 10, 2017 3:50 pm
- Forum: ROMS Usage
- Topic: Model blow-up after adding river discharge
- Replies: 7
- Views: 9101
Re: Model blow-up after adding river discharge
I have changed the Qshape to DO k=1,N(ng) DO is=1,Nsrc(ng) i=SOURCES(ng)%Isrc(is) j=SOURCES(ng)%Jsrc(is) IF (((IstrT.le.i).and.(i.le.IendT)).and. & & ((JstrT.le.j).and.(j.le.JendT))) THEN IF (ubar(i,j,knew).ne.0.0_r8) THEN cff=ABS(u(i,j,k,nnew)/ubar(i,j,knew)) ELSE cff=1.0_r8 END IF SOURCES(ng ...
- Fri Mar 10, 2017 2:45 pm
- Forum: ROMS Usage
- Topic: Model blow-up after adding river discharge
- Replies: 7
- Views: 9101
Re: Model blow-up after adding river discharge
Hello Kate,
Thanks for the quick response. I really appreciate it.
Do you suggest I should change to
or
For the Qshape, I am simply using the example from riverplume1 in the ana_psource. What do you mean that it may not be stable?
Amy
Thanks for the quick response. I really appreciate it.
Do you suggest I should change to
Code: Select all
LtracerSrc = T T
Code: Select all
LtracerSrc = T T T T
Amy
- Fri Mar 10, 2017 6:09 am
- Forum: ROMS Usage
- Topic: Model blow-up after adding river discharge
- Replies: 7
- Views: 9101
Model blow-up after adding river discharge
Hello, I am using ROMS to simulate tidal flow in a coastal region containing a long and curved river. The grid also includes wetlands, so I have turned on WET_DRY. This setting runs smoothly to the end. Now I want to add a point source to the upstream to account for the river discharge. I have ...
- Tue Jan 24, 2017 5:08 pm
- Forum: ROMS Sediment
- Topic: Activate the SSW_BBL but the current magnitudes too small!
- Replies: 1
- Views: 7869
Activate the SSW_BBL but the current magnitudes too small!
Hello, I am running a ROMS+SWAN coupled model on an idealized sloping bathymetry. By using UV_QDRAG, the current magnitudes are within the good range. But in order to account for the wave and current interaction, I have activated the SSW_BBL and SSW_CALC_ZNOT cpp options. Now the current magnitudes ...
- Tue Jan 24, 2017 2:44 am
- Forum: ROMS Sediment
- Topic: Bed load transport all zeros!
- Replies: 1
- Views: 7491
Bed load transport all zeros!
Hello, I have ran a ROMS and SWAN coupled model for an idealized case with sediment module. The model bathymetry is a simple sloping bottom with idealized bars. I have defined the BEDLOAD_SOULSBY cpp option. But the outputs I got for bed load transport are all zeros. Some relevant settings are ...
- Sat Dec 19, 2015 10:24 pm
- Forum: ROMS Discussion
- Topic: Coupling test: swan output cannot combine?
- Replies: 1
- Views: 1715
Coupling test: swan output cannot combine?
Hello, I am running the SWAN and ROMS coupling model with a plane beach using inlet_test.h. It ran smoothly until the end. I got the error message as, 0: Subscript out of range for array oqi (swanparll.f90: 3934) subscript=3, lower bound=32767, upper bound=-1407940773, dimension=1 In swanparll.f90 ...
- Thu Nov 19, 2015 4:15 pm
- Forum: ROMS Usage
- Topic: INLET TEST: Why are initial wave directions 81 deg?
- Replies: 2
- Views: 3558
Re: INLET TEST: Why are initial wave directions 81 deg?
Hello John, Thank you for your help. In my project, I actually need E-W periodic boundaries. I know this can be tricky. So after I ran the INLET_TEST case, I replaced the bathymetry to a plane beach without changing any other parameters. That is to say, the east and west boundaries were set to be ...
- Thu Nov 19, 2015 2:30 am
- Forum: ROMS Usage
- Topic: INLET TEST: Why are initial wave directions 81 deg?
- Replies: 2
- Views: 3558
INLET TEST: Why are initial wave directions 81 deg?
Hello, I have successfully compiled and run the INLET_TEST case using the 2015 COAWST system. But when I looked at the output of Dwave, it seems to me that the initial wave directions along the boundaries except the north boundary are always 81 degrees. This problem doesn't exist in the 2010 COAWST ...