Are there any linked Issues or Pull Requests?
No response
Brief description
CoMorph currently interacts with hydrometeor mass and cloud-fraction prognostics, but not the hydrometeor number concentrations used in CASIM. We need to plumb the prognostic number concentration arrays through CoMorph so that it increments them consistently with hydrometeor mass and cloud-fraction.
In this implementation, we will retain CoMorph's existing microphysics scheme and set the in-plume number concentrations to the simply-parameterised values it currently uses. These values will then be detrained along with the hydrometeor masses. This way, CoMorph updates but has no dependency on the prognostic number concentrations. This means we only need to transport number on the final dynamics outer loop (if CoMorph had strong dependence on the number, we'd need to transport number on both dynamics loops to ensure mass and number passed into CoMorph are always consistent with eachother).
This will build upon some of the relevant changes already coded in this branch:
cc86710
Further details of the issue.
No response
Are there any linked Issues or Pull Requests?
No response
Brief description
CoMorph currently interacts with hydrometeor mass and cloud-fraction prognostics, but not the hydrometeor number concentrations used in CASIM. We need to plumb the prognostic number concentration arrays through CoMorph so that it increments them consistently with hydrometeor mass and cloud-fraction.
In this implementation, we will retain CoMorph's existing microphysics scheme and set the in-plume number concentrations to the simply-parameterised values it currently uses. These values will then be detrained along with the hydrometeor masses. This way, CoMorph updates but has no dependency on the prognostic number concentrations. This means we only need to transport number on the final dynamics outer loop (if CoMorph had strong dependence on the number, we'd need to transport number on both dynamics loops to ensure mass and number passed into CoMorph are always consistent with eachother).
This will build upon some of the relevant changes already coded in this branch:
cc86710
Further details of the issue.
No response