Ocean Modeling Discussion

All right, it blows up again. Now it's not the issue of this.
I have got errors in ROMS 3.9. Maybe I should use the ROMS 3.8 first in order to find my problems and do my research. I don't want to spend more time on model debugging. Maybe I would bug them to Hadfield after I know the real reason.

Ok, thank you very much. Now I can know the difference between them.

Ok, I got it. Thank you very much!

Thank you very much, you are right. It looks like you have max_bio set to 10000. Does that make sense for the units you are using? You can change it if 10000 is a valid number for your BGC model. I probably added the check for COSINE, but then kept it for COBALT. For COBALT, typical units are more l...

I ask this question because of the biological modules. When I read the biological module code in ROMS, there is usually some notes like this in the end. It then updates all of the biological values behind these notes. !----------------------------------------------------------------------- ! Update ...

During my application establishment, I open the "OFFLINE_BIOLOGY" option and compile them, which gives me a wrong error and aborts during my compiling. After checking out the main3d_offline.F file in ROMS 3.9, I found there is some code missed. When I add this code, it can compile successf...

Hi. I'm running a realistic application using ROMS coupled with biological modules. I can run the physical parts without any biological modules successfully. It gets blow up when I open any biological modules, such as nemuro, fennel or bio_UMAINE. It blows up because of the large biological value. W...

I'm pretty grateful for your help!
It's the problem about the cycle length of the time.

ocean_time:cycle_length = 365. ;

After deleting this attribute of variable ocean_time in my climatology file, it can run successfully.

CLMNAME == /public/home/rengz/roms/Apps/Lagrangian/input/ECS_clm_2016.nc In my climatology file, the time variable is as follows: double ocean_time(ocean_time) ; ocean_time:long_name = "time since intialization" ; ocean_time:units = "days since 1970-01-01 00:00:00" ; ocean_time:...

I have solved this problem already. The NaN value of PE (potential energy) and KE(kinetic energy) is really tricky. It's the problem with the CFL criteria. In my application, the DT is the 60s. The spatial resolution is about 2.5km in the coastal region and 8km in the open ocean. The timestep is too...

Hello, In my application, I can run it successfully without nudging anything just like this: LsshCLM == F ! sea-surface height Lm2CLM == F ! 2D momentum Lm3CLM == F ! 3D momentum LtracerCLM == F F ! temperature, salinity, inert LnudgeM2CLM == F ! 2D momentum LnudgeM3CLM == F ! 3D momentum LnudgeTCLM...

I have changed both Pair and Qair, the reason is that the scalar factor is different in ROMS 3.9 and ROMS 3.8. I have changed them. Now I can run for about one day. However, it blows up after 2280 timesteps because of the NaN value. 2280 2016-04-11 14:00:00.00 NaN NaN NaN NaN (000,000,00) 0.000000E+...

And if you are mixing and matching float routines from myroms.org with Kate's then I'm not sure if that's a problem. I don't mixing the code in ROMS 3.8 and 3.9. I'm running the application just under ROMS 3.9. First, don't all the system errors at the start worry you? And in the middle of the star...

You log file indicates the problems with reading initial conditions are all at line 208 and 285 of initial.f90. So, see what ROMS is trying to read at that line. In my ROMS 3.9 source code, there are some source code in the initial.f90 195 !==========================================================...

I have tried this application in ROMS 3.8, which is downloaded from www.myroms.org . It also blows up after the first timestep. I open the debug mode to see what happened. It tells me that there is something about my input NetCDF file——both input and output file. Could you please help me find out th...

Hi, everyone. I'm running the Lagrangian floats in my application under ROMS 3.9. I can compile them successfully. When I run it, there are some abnormal stops which I can't find out the reasons. Even if I open the debug mode, there is nothing to tell me the reasons. mpirun -np 4 ./LAGRANGIAN_deb .....