Changes between Version 9 and Version 10 of ticket/1658/General


Ignore:
Timestamp:
2016-06-09T16:22:05+02:00 (4 years ago)
Author:
frrh
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • ticket/1658/General

    v9 v10  
    101101   OK so this fails to run - We need to enable l_oasis_obgc in the suite to ensure arrays are allocated to send/receive coupling variables. Doing that we then gat a reconfiguration failure as we need to include fields 0,197 in the UM start dump. Add this in the "Configure ancils and initialise dump files" section and initialise to zero. That gets through the reconfiguration again. But do we have a source for the incoming DMS beyond the recieved field. I'm not sure we do.... That's probably fine for now, for testing purposes, but where does it need to go ultimately?   
    102102  
    103    Well that now runs OK. (Remember the atmosphere is merely recieveing the DMS field, it's not using it aywhere... that's for the code owner to figure out.) Checking the DMS coupling field using EXPOUT we see that at TS=1 we have uniform zero and non zero values evolve at subsequent coupling exchanges. However, looking at the incoming field to the atmos we see a column of an apparent steep gradient in the field below India. This is the point at which the orca grid begins and ends - i.e. this looks like a wrap around issue.  
     103   Well that now runs OK. (Remember the atmosphere is merely recieveing the DMS field, it's not using it aywhere... that's for the code owner to figure out.) Checking the DMS coupling field using EXPOUT we see that at TS=1 we have uniform zero and non zero values evolve at subsequent coupling exchanges. However, looking at the incoming field to the atmos we see a column of an apparent steep gradient in the field below India. This is the point at which the orca grid begins and ends - i.e. this looks like a wrap around issue with the MEDUSA DMS field.  
    104104