Skip to content

Conversation

@liranpeng
Copy link

The first line should be a single-line "purpose" for this change

TYPE: choose one of [bug fix, enhancement, new feature, feature removed, no impact, text only]

KEYWORDS: 5 to 10 words related to commit, separated by commas

SOURCE: Either "developer's name (affiliation)" .XOR. "internal" for a WRF Dev committee member

DESCRIPTION OF CHANGES:
Problem:
Generally or specifically, what was wrong and needed to be addressed?

Solution:
What was down algorithmically and in the source code to address the problem?

ISSUE: For use when this PR closes an issue.
Fixes #123

LIST OF MODIFIED FILES: list of changed files (use git diff --name-status master to get formatted list)

TESTS CONDUCTED:

  1. Do mods fix problem? How can that be demonstrated, and was that test conducted?
  2. Are the Jenkins tests all passing?

RELEASE NOTE: Include a stand-alone message suitable for the inclusion in the minor and annual releases. A publication citation is appropriate.

liranpeng and others added 7 commits January 3, 2025 09:27
Fix bug and do not load every time.
This commit adds a new namelist parameter `use_ml_activate` that allows
users to easily switch between ML-based activation (activate_ml) and
traditional activation (activate) methods via the namelist.

Changes:
- Registry/Registry.EM: Added use_ml_activate namelist flag (default=1)
- phys/module_mixactivate.F:
  * Added config_flags parameter to mixactivate and prescribe_aerosol_mixactivate
  * Added conditional logic to call activate_ml or activate based on flag
- chem/module_mixactivate_wrappers.F: Updated all wrapper calls to pass config_flags
- phys/module_microphysics_driver.F: Updated prescribe_aerosol_mixactivate call

Usage in namelist.input:
&physics
 use_ml_activate = 1   ! Use ML activation (activate_ml)
 use_ml_activate = 0   ! Use traditional activation (activate)
/
@liranpeng liranpeng requested review from a team as code owners January 3, 2026 02:50
@weiwangncar
Copy link
Collaborator

@liranpeng The regression tests failed on compilation. I'm attaching one output file here. Please make sure you can compile the code on your local system before submitting a PR. Compilation errors are shown in the attatched file. Please also fill the PR template so that the code reviewers will know what is being changed.
output3.txt

Two wrapper subroutines (sorgam_vbs_mixactivate) had different indentation
and were not caught by the initial replacement. This commit adds config_flags
to those remaining calls.
@weiwangncar
Copy link
Collaborator

@liranpeng Your last commit didn't fix the compilation issue... The tests still failed.

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.

3 participants