New URL for NEMO forge!   http://forge.nemo-ocean.eu

Since March 2022 along with NEMO 4.2 release, the code development moved to a self-hosted GitLab.
This present forge is now archived and remained online for history.
2018WP/SharedActions/Status_dev_merge_2017_branch (diff) – NEMO

Changes between Version 27 and Version 28 of 2018WP/SharedActions/Status_dev_merge_2017_branch


Ignore:
Timestamp:
2018-02-21T16:44:16+01:00 (6 years ago)
Author:
davestorkey
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • 2018WP/SharedActions/Status_dev_merge_2017_branch

    v27 v28  
    1515I'm getting occasional failures with a segmentation fault in icb_ground in eORCA1 and eORCA025 built from the latest dev_merge_2017 branch (after several months of integration). I think icb_ground is acting as an error trap for NaN values produced in ice_dyn_rhg_evp. I will try to trace it back further next week. (Dave Storkey). 
    1616 
    17 '''Update 21 Feb:''' This looks like some kind of instability which doesn't get picked up by the checks in stp_ctl. There is very thick ice (~100m) at a single point which I think results in a divide-by-zero in sbc_isf_div. It looks different to the instability in the the 300 timestep ORCA2LIM3PIS_ST run in SETTE, which doesn't show any abnormally thick ice.  
     17'''Update 21 Feb:''' This looks like some kind of instability which doesn't get picked up by the checks in stp_ctl. There is very thick ice (~100m) and a negative top-level thickness (e3t) at a single point which I think results in a divide-by-zero in sbc_isf_div. It looks different to the instability in the the 300 timestep ORCA2LIM3PIS_ST run in SETTE, which doesn't show any abnormally thick ice.  
    1818 
    1919== 12 February 2018 : ORCA2_LIM3_PISCES with icebergs is not reproducible