Possible bugs found when testing CIF (v2.9, v2.6)

Rapportation of bugs in the COHERENS code. Please, report in detail the problem/bug you found and provide the necessary information to reproduce the problem. This information will be useful to traceback the bug and fix it.

Moderator: pluyten

Post Reply
manguita
Posts: 1
Joined: Mon Jun 26, 2017 10:32 am
Full name: Mancia Anguita

Possible bugs found when testing CIF (v2.9, v2.6)

Post by manguita »

Hi,

I am new to COHERENS. We are very interested in using it.

Testing section 2.4.1.2 (User_Documentation_v2.6.pdf) using v2.9, I have had to include these modifications for avoiding errors:

1) Files river1T.CifModA and river0T.CifModA:

! Grid input
MODFILES = modgrd,1,1,N,R,riverT.modgrd.nc,0,0,0,0,F,F, !changed modgrdN for modgrd.nc

! Open boundary conditions input
MODFILES = 2uvobc,1,1,A,R,riverT.2uvobc1.txt,0,0,0,0,F,F, !changed 2uvobc1A for 2uvobc1.txt

! Initial conditions input (restart file from simulation 0)
MODFILES = inicon,1,1,N,N,riverT.phsfin.nc,0,0,0,0,F,F, !changed phsfinN for phsfin.nc

! Horizontal coordinates
SURFACEGRIDS = 1,1,0,0,1000.,1000.,0.,0.,,,,, !added 5 commas at the end for increasing the number of parameters from 8 to 12 (12 for GridParams defined in datatypes.f90), change also required for v2.6


2) File Usrdef_Model.f90:

modfiles(io_inicon,ics_phys,1)%filename = 'riverT.phsfin'//'.nc' !'.nc' instead of %form (i.e. instead of N)
modfiles(io_fincon,ics_phys,1)%filename = 'riverT.phsfin'//'.nc' !'.nc' instead of %form (i.e. instead of N)


3) Modification by Katrijn in river1T.CifModA (thanks Katrijn):

changed
TSRGPARS = 1,T,F,F,T,2003/01/03;00:00:00:000,3,0,0,1,140,1,1,1,1,1,20,1,0,8640,180
by
TSRGPARS = 1,T,F,T,2003/01/03;00:00:00:000,3,0,0,1,140,1,1,1,1,1,20,1,0,8640,180 ! third parameter 'gridfile (T/F)' is not used



Regards,

Mancia
Katrijn
Posts: 87
Joined: Fri Nov 29, 2013 3:04 pm
Full name: Katrijn Baetens

Re: Possible bugs found when testing CIF (v2.9, v2.6)

Post by Katrijn »

Thank you for sharing Mancia, we are working on it to remove them from our next release!
Post Reply