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.
ticket/0829 (diff) – NEMO

Changes between Version 1 and Version 2 of ticket/0829


Ignore:
Timestamp:
2011-05-31T09:55:37+02:00 (13 years ago)
Author:
rblod
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ticket/0829

    v1 v2  
    44[[BR]] 
    55 
    6 '''Author''' : rblod 'Rachid Benshila)  
     6'''Author''' : rblod (Rachid Benshila)  
    77 
    88'''ticket''' : #829 
    99 
    10 '''Branch''' : [https://forge.ipsl.jussieu.fr/nemo/browser/branches/2011/dev_r2769_LOCEAN_dynamic_mem      ev_r2769_LOCEAN_dynamic_mem ]  
     10'''Branch''' : [https://forge.ipsl.jussieu.fr/nemo/browser/branches/2011/dev_r2769_LOCEAN_dynamic_mem      dev_r2769_LOCEAN_dynamic_mem ]  
    1111---- 
    1212 
    1313=== Description === 
    1414 
     15Computing  aspects of dynamic memory implementation are already described there http://forge.ipsl.jussieu.fr/nemo/wiki/2011WP/2011Stream2/DynamicMemory, possible conseuqneces  there https://forge.ipsl.jussieu.fr/nemo/wiki/2011Stream2/DynamicMemory_improvments . This branch deals with the first aspect, ie the practical implementation. [[BR]] 
     16Dynamic memory implementation is clearly a step forward, an current implementation from branch dev_r2586_dynamic_mem; is quiet clean, with careful checks of availability of the work arrays. However: 
     17 * Assignation of work arrays by hand leads to some difficulties considering the number of options and combinations of options available in NEMO 
     18 * In term of memory, the number of work arrays have to be hard-coded to the maximum combination, ie we always use more memory than needed 
    1519 
    1620----