lasso-wrf issueshttps://code.arm.gov/lasso/lasso-wrf/-/issues2019-04-11T17:19:13Zhttps://code.arm.gov/lasso/lasso-wrf/-/issues/9Add cell-specific cloud fraction calculations to LES stats2019-04-11T17:19:13ZSherman BeusAdd cell-specific cloud fraction calculations to LES stats*Created by: wgustafson*
Calculate high time frequency cloud fraction for each cell and output the full 3-D volume with LES statistics output frequency.
Should we also output 2-D column-integrated cloud mask with the same high-freque...*Created by: wgustafson*
Calculate high time frequency cloud fraction for each cell and output the full 3-D volume with LES statistics output frequency.
Should we also output 2-D column-integrated cloud mask with the same high-frequency calculation? How different would this be from turning the cell-based high-frequency cloud fraction into a 2-D mask? How much does cloud overlap impact this conversion?https://code.arm.gov/lasso/lasso-wrf/-/issues/8Add single-column output for multiple locations2019-04-11T17:19:14ZSherman BeusAdd single-column output for multiple locations*Created by: wgustafson*
We need to output profiles for multiple locations at high temporal frequency to compare with the spatially averaged statistics. The current WRF method for this uses text files with a mix of variable-specific fil...*Created by: wgustafson*
We need to output profiles for multiple locations at high temporal frequency to compare with the spatially averaged statistics. The current WRF method for this uses text files with a mix of variable-specific files and blended variable files for column vs. single-point values. We should convert this to netCDF and all in one file. One dimension would be site location.https://code.arm.gov/lasso/lasso-wrf/-/issues/6Handling of fluxes in crm_stat is inaccurate2019-04-11T17:19:14ZSherman BeusHandling of fluxes in crm_stat is inaccurate*Created by: wgustafson*
Consider modifying calculation of fluxes in crm_stat to directly get the information from the dynamics calculations so that they are more accurate. *Created by: wgustafson*
Consider modifying calculation of fluxes in crm_stat to directly get the information from the dynamics calculations so that they are more accurate. https://code.arm.gov/lasso/lasso-wrf/-/issues/7Handling of vertical averaging in crm_stat could be improved2019-04-11T17:19:13ZSherman BeusHandling of vertical averaging in crm_stat could be improved*Created by: wgustafson*
We should average to height levels to calculate the domain-wide averages instead of using the eta levels.*Created by: wgustafson*
We should average to height levels to calculate the domain-wide averages instead of using the eta levels.https://code.arm.gov/lasso/lasso-wrf/-/issues/10Ice is not considered in any cloud fraction calcuations in crm_stat2019-04-11T17:19:13ZSherman BeusIce is not considered in any cloud fraction calcuations in crm_stat*Created by: wgustafson*
We need to revamp the handling of cloud fractions and cloud masking within crm_stat. Currently, cloud ice isn't even passed into the routine. We need to take the ice into consideration. I think it currently isn'...*Created by: wgustafson*
We need to revamp the handling of cloud fractions and cloud masking within crm_stat. Currently, cloud ice isn't even passed into the routine. We need to take the ice into consideration. I think it currently isn't done to imply a low-cloud fraction. But, we can independently calculate low, mid, and high cloud fractions that take ice into account. This would be a better way to handle this.
While we're at it, we can also add output for ice water content and profile averages of frozen condensate. The cldtot variable should be turned into a true "total" for liquid+frozen.