Search found 10 matches

by rock
Wed Dec 15, 2021 7:14 pm
Forum: ROMS Problems
Topic: Cannot run 2D only mode with ROMS3.9 or higher
Replies: 9
Views: 16754

Re: Cannot run 2D only mode with ROMS3.9 or higher

Hi John,
1. Yes, it seems that ifort cannot do "DO i=1,0".
2. ic has an assigned value of 5, but since the do loop does not work (with ifort), isTvar is not assigned in the right way. That causes further problems anywhere using isTvar.
Thank you,
Yan
by rock
Wed Dec 15, 2021 5:26 pm
Forum: ROMS Problems
Topic: Cannot run 2D only mode with ROMS3.9 or higher
Replies: 9
Views: 16754

Re: Cannot run 2D only mode with ROMS3.9 or higher

Hi All, The problem comes from the variable MT defined in mod_param.F. For version 3.8 and earlier, it is assigned as below #if defined IS4DVAR || defined W4DVAR || defined W4DPSAS MT=MAX(NAT,MAXVAL(NT)) #else MT=MAX(2,MAXVAL(NT)) #endif Starting from version 3.9, it is assigned only as MT=MAX(NAT ...
by rock
Tue Dec 14, 2021 8:23 pm
Forum: ROMS Problems
Topic: Cannot run 2D only mode with ROMS3.9 or higher
Replies: 9
Views: 16754

Re: Cannot run 2D only mode with ROMS3.9 or higher

Hi All, I installed ROMS on the other HPC, also compiled with ifort (different version), still shows the same problem. However, it works when compiled with pgi. For the ifort compiles, I just use the original Linux-ifort.mk file, no additional flag is added or changed. Still looking for a solution ...
by rock
Mon Dec 13, 2021 11:46 pm
Forum: ROMS Problems
Topic: Cannot run 2D only mode with ROMS3.9 or higher
Replies: 9
Views: 16754

Re: Cannot run 2D only mode with ROMS3.9 or higher

Hi Hernan,
Thanks for the suggestions. I am sure the roms.in and varinfo.dat are copied or cited from the corresponding version folder. I also tested the SOLITON case, it has the same problem.
Yan
by rock
Mon Dec 13, 2021 9:49 pm
Forum: ROMS Problems
Topic: Cannot run 2D only mode with ROMS3.9 or higher
Replies: 9
Views: 16754

Re: Cannot run 2D only mode with ROMS3.9 or higher

Hi John,
Line 904 is 'isWvel=ic+1' in mod_ncparam.f90
Yan
by rock
Mon Dec 13, 2021 8:13 pm
Forum: ROMS Problems
Topic: Cannot run 2D only mode with ROMS3.9 or higher
Replies: 9
Views: 16754

Cannot run 2D only mode with ROMS3.9 or higher

Hi all, I installed the newest version of ROMS and tried to run an old case of mine. The model runs OK under 3D mode. However, if undefined SOLVE3D, it reports 'segmentation fault' in the error file. Below is one part from the file forrtl: severe (174): SIGSEGV, segmentation fault occurred Image PC ...
by rock
Sat Mar 31, 2018 11:12 am
Forum: ROMS Problems
Topic: Could not read in multiple boundary files correctly
Replies: 2
Views: 2548

Re: Could not read in multiple boundary files correctly

According to the log file, the model loaded in the next boundary file name correctly. But the Tmin, Tmax, and ntime reported from get_cycle.F are still from the first boundary file. I noticed this because my next boundary file should have a longer ntime. Chasing down this, I found the ncid used by ...
by rock
Fri Mar 30, 2018 5:13 pm
Forum: ROMS Problems
Topic: Could not read in multiple boundary files correctly
Replies: 2
Views: 2548

Could not read in multiple boundary files correctly

I updated my ROMS to the newest version recently, with file /Utility/inquiry.F But it could not read in multiple boundary files correctly. Which previously works fine. And the older version has file /Utility/inquire.F The inquiry.F file could not update the ncid to the second boundary.nc file, it ...
by rock
Tue Jan 23, 2018 8:15 pm
Forum: ROMS Bugs
Topic: cannot write out nest grid salinity with dye on
Replies: 0
Views: 2061

cannot write out nest grid salinity with dye on

If using dye with nesting grids, some of the active tracers may not be written out properly, even with the corresponding switches turn on. The bug comes from miss using Ltracer under case(‘Hout(idTvar)’) in read_phypar.F. If turn on dye, the size of Ltracer is larger than NAT*Ngrids. However, when ca ...
by rock
Tue Feb 10, 2015 12:38 pm
Forum: ROMS Bugs
Topic: Bug in wet_dry- the lake_jersey case has the same issue
Replies: 8
Views: 6892

Re: There might be a bug in contact.m

Below are what I found recently,

Line 609 'R.x_rho' should be 'R.x_psi';
line 610 'G(dg).y_rho(:)' should be 'G(dg).y_psi(:)', and 'R.y_rho' should be 'R.y_psi';
line 753~755 'FCr' should be 'FSr'.

Yan