How to manage and compare AbdulRazzakGhan parameterisation and BetancourtNenes #171
Replies: 3 comments 2 replies
-
Thank you so much for the effort to clear this up! I think I understand, at least partly. I have already moved around on the BN code so that it can be called by an activate_modal_BN subroutine. I just haven't been able to untangle all of the code in activate_modal(_ARG). |
Beta Was this translation helpful? Give feedback.
-
My suggestion out of this: If default BN use pdf updraft than the effective updraft should be found by integrating the distribution.(Not quite trivial but equations do exist) |
Beta Was this translation helpful? Give feedback.
-
ARG is single updraft |
Beta Was this translation helpful? Give feedback.
-
I have at last gone back to the activation code and think (hope?) that I understand the assumptions and structure now.
Why is it so difficult to compare and combine the two different parameterisations:
The activation parameterisation has two steps to it. It calculates the fraction that is activated, but in order to get a tendency (number / second) it need to use the upwards moment to calculate the time tendency. The flux of aerosols is defined as a vertical velocity.
The reason why I do think I understand the structure now is that I went through the units of the equations and was able to get from the two output values (fraction (so unitless) and m/s, to (kg of air)-1 * seconds -1. The main trick is that part of the calculations deal with fractional column values so it does not have to bother with actual concentrations.
This vertical velocity should be / is assumed be the same vertical velocity that drives the supersaturation. There is an exception for the lowest model layer, which has it own parameterisation which according to the comments none really understands.
For ARG parameterisation both of these quantities are calculated in activate_modal.
The problem is that the two quantities are not treated independently and this was what confused me to the point that BM was implemented outside activate_modal despite needing the same input / output fields.
The higher vertical velocities in the pdf is assumed to be less efficient in driving the supersaturation. Since the vertical flux used for calculating the flux is supposed to follow what drives the supersaturation the "vertical velocity flux" is reduced from the integrated value to this modified value. If there is no pdf then the flux = vertical velocity. In other words it looks like the simplification I did in the first place was valid.
BN does not use this assumption so to take into account the distribution it is enough to integrate the speed over the pdf so a good portion of fraction of the ARG calculations can be bypassed and replaced by the pdf integral (i.e erf function).
Also making it simpler, this particular assumption can be seen as inherent to the ARG parameterision so should not be included in BN.
For coding I suggest that BN should be moved into the same type of subroutine as the present activate_modal subroutine, but not not inside the same routine which I think would be hard to read.
@ingvisau @gold2718 @MichaelSchulzMETNO
Beta Was this translation helpful? Give feedback.
All reactions