Changes between Version 20 and Version 21 of Working Groups/TOP/TOP-User Quick Guide


Ignore:
Timestamp:
2018-01-17T12:24:12+01:00 (3 years ago)
Author:
lovato
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Working Groups/TOP/TOP-User Quick Guide

    v20 v21  
    299299{{{ 
    300300bld::tool::fppkeys  key_zdftke key_dynspg_ts key_iomput key_mpp_mpi key_top 
    301 src::MYBGC::initialization           <MYBGCPATH>/initialization 
    302 src::MYBGC::pelagic         <MYBGCPATH>/pelagic 
    303 src::MYBGC::benthic             <MYBGCPATH>/benthic 
     301src::MYBGC::initialization         <MYBGCPATH>/initialization 
     302src::MYBGC::pelagic                <MYBGCPATH>/pelagic 
     303src::MYBGC::benthic                <MYBGCPATH>/benthic 
    304304 
    305305bld::pp::MYBGC      1 
    306 bld::tool::fppflags::MYBGC %FPPFLAGS 
    307 bld::tool::fppkeys  %bld::tool::fppkeys MYBGC_MACROS 
     306bld::tool::fppflags::MYBGC   %FPPFLAGS 
     307bld::tool::fppkeys           %bld::tool::fppkeys MYBGC_MACROS 
    308308}}} 
    309309 
     
    325325This will enable a more portable compilation structure for all MYBGC related configurations. 
    326326 
    327 Finally, the coupling interface contained in nemo_coupling cannot be added using the FCM syntax, as the same files already exists in NEMO and they are overridden only with the readdressing of MY_SRC contents to avoid compilation conflicts due to duplicate routines. 
     327'''Important''': the coupling interface contained in nemo_coupling cannot be added using the FCM syntax, as the same files already exists in NEMO and they are overridden only with the readdressing of MY_SRC contents to avoid compilation conflicts due to duplicate routines. 
    328328 
    329329All modifications illustrated above, can be easily implemented using shell or python scripting to edit the NEMO configuration cpp.fcm file and to create the BGC model specific FCM compilation file with code paths.