Skip to content

Need a factor to reduce PAR from visible solar for I compset cases #1713

Open

Description

@ekluzek

This is something that Rong Li brought to our attention in her work on the SIF code. There are two issues. One is that in datm we divide solar radiation evenly between the visible and near-IR bands using a ratio of 0.5. The other is that PAR is only part of the visible spectrum and not the entire amount.

The ratio between NIR and VIS is done for the offline model in datm. The ratio based on FluxNet sites is more like 0.43. The justification for this ratio in datm given in a comment is:

          ! relationship between incoming NIR or VIS radiation and ratio of
          ! direct to diffuse radiation calculated based on one year's worth of
          ! hourly CAM output from CAM version cam3_5_55

However, if we modify NIR and VIS in the datm, that will have a whole list of downstream affects on the model that would likely be a big tuning exercise to workout.

@RongLi29 way to resolve this was to apply a factor inside of surface radation that only applies for what's being used as PAR. The factor is only appropriate when running I cases (with datm rather than CAM). So we'll need to have it apply for I cases, but not B or F cases.

@RongLi29 @danicalombardozzi

Activity

  1. ekluzek commented on Apr 15, 2022

    @ekluzek
    ContributorAuthor

    This is the modification that @RongLi29 made to SurfaceRadiationMod.F90 to adjust for this for the offline I cases:

               ! for leaf APAR
               parlsun_z(p,iv) = forc_solad(g,ipar)*fabdl_sun_z(p,iv)*0.87 + forc_solai(g,ipar)*fabil_sun_z(p,iv)*0.87
               parlsha_z(p,iv) = forc_solad(g,ipar)*fabdl_sha_z(p,iv)*0.87 + forc_solai(g,ipar)*fabil_sha_z(p,iv)*0.87
    
  2. dlawrenncar commented on Apr 18, 2022

    @dlawrenncar
    Contributor
  3. ekluzek commented on Apr 18, 2022

    @ekluzek
    ContributorAuthor

    Here's the entire bit of code from CDEPS that gives this when only SW down is provided. You are right the ratio between direct and diffuse is 0.5, the ratio between near-IR and visible is more complex.

            swndr = strm_swdn(n) * 0.50_r8
             ratio_rvrf =  min(0.99_r8,max(0.29548_r8 + 0.00504_r8*swndr  &
                  -1.4957e-05_r8*swndr**2 + 1.4881e-08_r8*swndr**3,0.01_r8))
             Faxa_swndr(n) = ratio_rvrf*swndr
             swndf = strm_swdn(n) * 0.50_r8
             Faxa_swndf(n) = (1._r8 - ratio_rvrf)*swndf
    
             swvdr = strm_swdn(n) * 0.50_r8
             ratio_rvrf =   min(0.99_r8,max(0.17639_r8 + 0.00380_r8*swvdr  &
                  -9.0039e-06_r8*swvdr**2 + 8.1351e-09_r8*swvdr**3,0.01_r8))
             Faxa_swvdr(n) = ratio_rvrf*swvdr
             swvdf = strm_swdn(n) * 0.50_r8
             Faxa_swvdf(n) = (1._r8 - ratio_rvrf)*swvdf

    If I've got this right it looks like it starts out more evenly divided for low SW levels, but as SW increases it goes to the threshold of 99% visible and 1% near-IR for full sun.

  4. dlawrenncar commented on Apr 18, 2022

    @dlawrenncar
    Contributor
  5. RongLi29 commented on Apr 19, 2022

    @RongLi29

    Yeah, my understanding is shortwave is evenly split into VIS and NIR, and the ratio between direct and diffuse is the more complex one (the polynomial). From the code: NIR direct + NIR diffuse = Faxa_swndr+Faxa_swndf = strm_swdn * 0.5; similarly, total VIS = Faxa_swvdr+Faxa_swvdf = strm_swdn * 0.5.

    My rough estimate based on FLUXNET data showed the ratio between PAR and SR is closer to 0.43 (see figure below). I would also note that in Ryu et al (2018), BESS and GLASS gave global average PAR/SR of 0.46 (they also reported slight positive bias of SR and negative bias of PAR, which may partially explain the difference between their ratio and what I derived from fluxnet), and Tsubo and Walker (2005) has a summary of PAR/SR reported at different locations ranging from 0.44-0.48 if PAR is defined as 0.4-0.7 μm. So there might be some discussion on which is the proper value to use, but 0.5 seems to be on the high end.

    PAR_SR_hh

    The code here seems consistent with the CLM5 tech note by the way:

    image

  6. added
    enhancementnew capability or improved behavior of existing capability
    scienceEnhancement to or bug impacting science
    and removed on Aug 8, 2024
  7. added
    nextthis should get some attention in the next week or two. Normally each Thursday SE meeting.
    on Feb 27, 2025
  8. ekluzek commented on Feb 27, 2025

    @ekluzek
    ContributorAuthor

    What kind of milestone should this have?

  9. added this to the Eventually milestone on Mar 6, 2025
  10. removed
    nextthis should get some attention in the next week or two. Normally each Thursday SE meeting.
    on Mar 6, 2025
  11. wwieder commented on Mar 6, 2025

    @wwieder
    Contributor

    I don't think this is a high priority at this point

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementnew capability or improved behavior of existing capabilityscienceEnhancement to or bug impacting science

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions