Changes between Version 15 and Version 16 of user/clem/Heat_Flux_air-ice-ocean_interface

Timestamp:

2016-05-19T20:25:18+02:00 (8 years ago)

Author:

klausred

Comment:

--

user/clem/Heat_Flux_air-ice-ocean_interface

@@ -2 +2 @@
 If the atm sends to the ocean/ice: {{{Qsnow = Cp(snow) * Tsnow}}}, and {{{Qrain = Cp(rain) * Train}}}, and {{{Qevap(ice) = Cp(ice) * Tice}}}, and {{{Qevap(ocean) = Cp(ocean) * Toce}}}, then heat is conserved and the differences between atm. physical constants and ocean/ice physical constants are unimportant.
 If the atm does not provide these fluxes, then we will make a guess and we have to make sure to have the same constants between Atm. models and NEMO. This is not yet the case.
+
+>''Klaus'': shouldn't it read {{{Qsnow = sprecip * Cp(snow) * Tsnow}}}, etc ?
+
+>''Klaus:'' Let's assume we can send these fluxes from IFS to NEMO. Who takes care of the coupling interface in NEMO? It would be stupid if we had one solution for IFS and a different solution for IPSL and yet another one for Arpege. When could such an updated coupling interface be in place?
+
+>''Klaus:'' EC-EARTH uses conservative coupling, e.g. we send the total precipitation (rain+snow) and snow. Could we for consistency have a similar setup for the flux of internal energy, e.g. send the sum of Qrain+Qsnow and Qsnow?