Changes between Version 14 and Version 15 of ticket/0846

Timestamp:

2011-10-23T16:10:38+02:00 (13 years ago)

Author:

momme

Comment:

--

ticket/0846

@@ -372 +372 @@
 ========= Marcello's comments  ========= Christian's comment is remarking the importance of FCM as "the tool" to incorporate other models into the system with little modification of the source code. I definitely agree with this point. The way we handle the coupling with the BFM now is to have a directory called nemo within the BFM tree that contains all needed routines. In our case, This directory is exactly what should go into MY_SRC. Extending on this method, the solution would be to totally substitute the main calling routines (trcstp and trctrp) with modified copies that will be maintained by each group in the tree of the biological model. In that case, I think we should be able to fit into the MY_TRC layout easily. As far as I can understand, FCM should consider the content opf MY_SRC directory in place of the files with the same names in the WORK directory. My only concern is whether FCM can eventually put the content of an external directory into MY_SRC, without the need to do it manually.
 
-=== Momme's comments on FCM use and my_trc interface ===
+========= Momme's comments on FCM use and my_trc interface  =========
 '''How to compile external "trc" code with NEMO using FCM, modifying only the fcm file of the local configuration.''' (Leaving the repository code untouched.)
 
@@ -443 +443 @@
 ! \/ #endif
 }}}
-''Side Note'': don't know if that's already flagged somewhere: I couldn't compile the original test case ORCA2_LIM using the last NEMO release, tag 3.3, it has key_lim2 defined, but limrhg is needed by limdyn_2, but only available in SRC_LIM3!
 
 === Status ===