Changes between Version 50 and Version 51 of Branches/Driver_Improvements

Timestamp:

2016-06-09T18:59:50+02:00 (8 years ago)

Author:

aducharne

Comment:

--

Branches/Driver_Improvements

@@ -186 +186 @@
 Note : During these test it was noted that the option "TIME_SKIP" in the run.def does not work correctly. It should not used.
 
-> '''AD (09/06/2016)''': for me, the "cell methods" that are used above are not all consistent with the documentation of the forcings. See http://www.eu-watch.org/gfx_content/documents/README-WFDEI%20(v2016).pdf for WFD and WFDEI. For the fluxes, the above analysis seems incorrect for WFD; and for GSWP, has mean(center) or mean(end) been used ? A personal synthesis is available here.
+> '''AD (09/06/2016)''': for me, the "cell methods" that are used above are not all consistent with the documentation of the forcings. See http://www.eu-watch.org/gfx_content/documents/README-WFDEI%20(v2016).pdf for WFD and WFDEI. For the fluxes, the above analysis seems incorrect for WFD; and for GSWP, has mean(center) or mean(end) been used ? A personal synthesis is available on https://forge.ipsl.jussieu.fr/orchidee/attachment/wiki/Branches/Driver_Improvements/forcing_driver.xls.
 >
 > '''Note also that dim2driver needs a forcing that has its first record at 0 UTC, in addition to instanteaneous "scalars" and fluxes as mean(end), to work correctly'''. This is why dim2driver has a weird diurnal cycle with WFDEI on https://forge.ipsl.jussieu.fr/orchidee/wiki/Branches/Driver_Improvements/ForcingVariable. The original WFDEI starts at 3UTC, and with dim2driver, you need to use WFDEIv1, in which a lag of 3 hours has been introduced by Ben Poulter and Fabienne Maignan. But I suppose that Jan has used dim2driver with the original WFDEI forcing, which would explain WFDEI is not well phased in the tests of Jan.