Changes between Version 11 and Version 12 of user/flavoni/report_simona

Timestamp:

2009-05-26T13:06:38+02:00 (15 years ago)

Author:

flavoni

Comment:

--

user/flavoni/report_simona

@@ -16 +16 @@
 
 changed files : 
-  monitoring01_opa9_ORCA2.cfg [[BR]]
+  monitoring01_opa9_ORCA2.cfg  [[BR]]
   monitoring01_lim2_ORCA2.cfg [[BR]]
-  monitoring.job  
+( in which, coherently whit I want to do I put same variables of timeseries that I put in opa9.card )  [[BR]]
+  monitoring.job   [[BR]]
+( in which I can't use ${FER_ATLAS} path, but I put monitoring01_opa9.cfg and monitoring01_lim2.cfg in directory of submission of the job )  [[BR]]
 
 and 
-  opa9.card  [[BR]] 
+  opa9.card [[BR]] 
   lim2.card [[BR]]
+( in which I put timeseries of variable that I want to monitoring 
+*******************************************************************************
+( NOTA : also because if I want to use monitoring.job by default I can't, because in monitoring.job there is an "exit if timeseries does not exists", so I'm obliged to have same timeseries if I want to use monitoring!)
+*******************************************************************************
+)  [[BR]]
 
 ( NOTA : tested with libiGCM tag version libIGCM_v1_2, revision 50. [[BR]]
@@ -67 +74 @@
 
 After a meeting of engenieers and researcher to point out direction for IPCC we decided that "NEMO forced" has to have same output data, monitoring and atlas of coupled. So I add same variables of coupled used in monitoring and in ZNL atlas.
-( NOTA : also because if I want to use monitoring by default; monitoring01... (CONTROLLARE!!!!!!!!)
- I can't, because in monitoring.job there is an "exit if timeseries does not exists", so I'm obliged to have same timeseries if I want to use monitoring!)
+( NOTA : also because if I want to use monitoring.job by default I can't, because in monitoring.job there is an "exit if timeseries does not exists", so I'm obliged to have same timeseries if I want to use monitoring!)
 
 5. "new diaptr"