#275 closed Defect (fixed)
1D stability issues with surface boundary conditions
| Reported by: | momme | Owned by: | ctlod |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | OCE | Version: | v3.0 |
| Severity: | Keywords: | C1D OPA SBC v3.0 | |
| Cc: |
Description
The 1D set-up in the ORCA2 configuration has serious issues with the surface forcing.
Using the clio surface boundary condition the model interrupts after few timesteps because of unreasonable high zonal velocities. Switching to analytical boundary conditions and setting them all to 0 the model seems to run fine, but as soon as some even small value of windstress is applied the problem reoccurs.
As this prpoblem wasn't there in v2 I suppose that this must be a problem with the new SBC interface.
Commit History (1)
| Changeset | Author | Time | ChangeLog |
|---|---|---|---|
| 1222 | ctlod | 2008-10-31T14:55:47+01:00 | add a missing jk indice in a DO jk loop, see ticket: #275 |
Change History (12)
comment:1 in reply to: ↑ description ; follow-up: ↓ 2 Changed 16 years ago by ctlod
- Owner changed from NEMO team to ctlod
- Status changed from new to assigned
comment:2 in reply to: ↑ 1 Changed 15 years ago by ctlod
- Resolution set to fixed
- Status changed from assigned to closed
Replying to ctlod:
Replying to momme:
The 1D set-up in the ORCA2 configuration has serious issues with the surface forcing.
Using the clio surface boundary condition the model interrupts after few timesteps because of unreasonable high zonal velocities. Switching to analytical boundary conditions and setting them all to 0 the model seems to run fine, but as soon as some even small value of windstress is applied the problem reoccurs.
As this prpoblem wasn't there in v2 I suppose that this must be a problem with the new SBC interface.
It seems effectivelly that a problem occurs when using the last release nemo_v3. The 1D configuration
works fine when using the nemo_v2_3 release.
We'll check that and keep you informed.
Christian Ethe found the origin of the problem.
It is indeed a bug located in dynnxt_c1d.F90 module.
The index jk was missing in a DO loop when applying the time step.
Thank you for your contribution.
Claude Talandier
comment:3 Changed 8 years ago by nicolasmartin
- Keywords configurations added; configuration removed
comment:4 Changed 8 years ago by nicolasmartin
- Keywords boundaries added; boundary removed
comment:5 Changed 8 years ago by nicolasmartin
- Keywords C1D added; 1D removed
comment:6 Changed 8 years ago by nicolasmartin
- Keywords nemo_v3* added
comment:7 Changed 8 years ago by nicolasmartin
- Keywords nemo_v3 added; configurations surface removed
comment:8 Changed 8 years ago by nicolasmartin
- Keywords SBC added; boundaries conditions removed
comment:9 Changed 8 years ago by nicolasmartin
- Keywords nemo_v3 removed
comment:10 Changed 6 years ago by nemo
- Keywords release-3.0 added; nemo_v3* removed
comment:11 Changed 2 years ago by nemo
- Keywords OPA r3.0 added; release-3.0 removed
comment:12 Changed 2 years ago by nemo
- Keywords v3.0 added; r3.0 removed
Replying to momme:
It seems effectivelly that a problem occurs when using the last release nemo_v3. The 1D configuration
works fine when using the nemo_v2_3 release.
We'll check that and keep you informed.