Custom Query (964 matches)
Results (841 - 843 of 964)
| Ticket | Owner | Reporter | Resolution | Summary |
|---|---|---|---|---|
| #148 | Done | Added check for activated advection flags | ||
| Description |
I added a sanity check in the advection options for momentum and tracers in checkdefs.F. The model now will stop if the user defines more than one horizontal and vertical advection for momentum or tracers. Because of the way that advection is coded, the order of these options is important in the predictor and corrector algorithms. If you specify more than one option you will get a different behavior. Many thanks to John Wilkin for pointing out this potential problem. Recall, that ROMS writes a lot of information to standard output. The users should pay a lot attention to the information that is written. |
|||
| #151 | Invalid | zero depth trouble | ||
| Description |
With the wet-dry option, it is more likely that someone will attempt to run with a depth of zero somewhere in the grid. The model doesn't put up with that, even if it is inside the land mask. I'm attaching one option for a patch. |
|||
| #152 | Fixed | Wet/dry masks not initialized | ||
| Description |
On the very first time through step2d, all the mask_wet arrays are still zero from the initialization to IniVal. This results in all of the ubar velocities ending up in the ELSE on line 2377 and getting set to zero (since they are multiplied by the zero umask_wet). The masks could be set in ini_fields before zeta gets modified. |
|||
