Skip to content

Feature/cd ssp input - #330

Open
chengdang wants to merge 11 commits into
feature/btj_REL-3.2.0from
feature/cd_ssp_input
Open

Feature/cd ssp input#330
chengdang wants to merge 11 commits into
feature/btj_REL-3.2.0from
feature/cd_ssp_input

Conversation

@chengdang

@chengdang chengdang commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Description

This PR adds an optional CRTM interface that allows aerosol and/or cloud optical properties to be provided directly as input for forward radiance calculations.

It supports:

Aerosol optical properties - options%AOP
Cloud optical properties - options%COP
total optical properties - options%TOP

New data structure. (OP for optical profiles):

OP_Input_type see src/Options/OP_Input/OP_Input_Define.f90
This data structure is included as part of existing CRTM data structure Options, src/Options/CRTM_Options_Define.f90

The following optical profiles are needed as input for radiance calculations:

  • Layer extinction optical depth
  • Layer scattering optical depth
  • Layer phase function coefficient for scatters
  • Layer backscatter coefficient (optional)

As a reference, users may check the following modules for optical profile calculation: CRTM_Compute_AerosolScatter, CRTM_Compute_CloudScatter

The following programs and data are included as examples in folder: test/mains/unit/Unit_Test/

  • Utility programs to generate optical inputs for all channels or for a subset of channels:
    test_OP.f90, test_OP_Subset.f90
  • Unit tests, forward calculations with OP inputs for all channels or for a subset of channels:
    Generate_OP.f90, Generate_OP_Subset.f90
  • OP input files:
    AOP_SingleProfile.nc COP_SingleProfile.nc TOP_SingleProfile.nc
    AOP_Subset.nc COP_Subset.nc TOP_Subset.nc
  • Atmosphere and land profiles used as example:
    Load_Atm_Data.inc, Load_Sfc_Data.inc

Note

Option COP/TOP does not support fractional cloud coverage. If needed by users, we can add later on.

Issue(s) addressed

#327

Dependencies

None

Impact

None

Checklist

  • I have performed a self-review of my own code
  • I have made corresponding changes to the documentation
  • I have run the unit tests before creating the PR

@chengdang chengdang self-assigned this Jul 14, 2026
@chengdang
chengdang marked this pull request as ready for review July 15, 2026 01:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants