Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: davegill/SCRIPTS
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: master
Choose a base ref
...
head repository: wrf-model/SCRIPTS
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: master
Choose a head ref
  • 12 commits
  • 400 files changed
  • 1 contributor

Commits on Sep 13, 2022

  1. Copy the full SHA
    4bbd51e View commit details
  2. Merge pull request #3 from kkeene44/boolean_warning

    Python is updated to V3.8 for regression testing and now when running a WRF test, a warning message is printed out:
    
    /wrf/rd_l2_norm.py:11: DeprecationWarning: np.boolis a deprecated alias for the builtinbool. To silence this warning, use boolby itself. Doing this will not modify any behavior and is safe. If you specifically wanted the numpy scalar type, usenp.bool_ here.
    
    This is not an error, but may cause confusion for some. To remove this error, the file rd_l2_norm.py has been modified so the warning will be ignored.
    kkeene44 authored Sep 13, 2022
    Copy the full SHA
    d78ac8c View commit details
  3. Copy the full SHA
    42b146d View commit details
  4. Merge pull request #4 from kkeene44/update_script_v16

    The new version16 build of the Docker container, which uses GNUv10, now displays different numbers for compiling options during WRF configuration. GNU options were previously 32 (serial), 33 (smpar), and 34 (dmpar). They are now 1, 2, and 3, respectfully. This requires a modification to script.csh to use the updated options.
    
    One command in script.csh used 'python3' and since the repository is updated to use python3.8, this command is updated to "python3.8."
    kkeene44 authored Sep 13, 2022
    Copy the full SHA
    4fe003d View commit details

Commits on Nov 1, 2023

  1. Copy the full SHA
    2cb7e42 View commit details
  2. Merge pull request #1 from kkeene44/update_namelists_ghg_input

    Add ghg_input=0 to namelists with non-compatible radiation options
    
    By default, ghg_input is turned on. This is only compatible with radiation options: CAM, RRTM, Dudhia, RRTMG, and RRTMG fast. There are several namelists in the regression tests that use other options and therefore the model is not able to run for those tests. All namelists that include non-compatible radiation options now include ghg_input=0 in the &physics record.
    kkeene44 authored Nov 1, 2023
    Copy the full SHA
    ae317fd View commit details

Commits on Nov 15, 2023

  1. Revert "add ghg_input=0 to namelists w/ non-compatible radiation," wh…

    …ich is causing regtest fails
    
    This reverts commit 2cb7e42.
    kkeene44 committed Nov 15, 2023
    Copy the full SHA
    d193ebf View commit details
  2. Merge pull request #2 from kkeene44/revert_ghg_input_nl_changes

    Revert "add ghg_input=0 to namelists w/ non-compatible radiation,"
    kkeene44 authored Nov 15, 2023
    Copy the full SHA
    35f81c3 View commit details

Commits on Dec 5, 2023

  1. Copy the full SHA
    4649b3f View commit details
  2. Merge pull request #3 from kkeene44/build.csh_config_numbers

    modified configuration options (#s) in script.csh
    Reg-tests are failing (or rather aren't providing any pass/fail information) for all tests - there is no output provided for real.exe or wrf.exe. This was due to the configuration options (the numerical values) for the variable CONF_BUILD_NUM in script.csh. A while back they were changed to 1, 2, and 3, but they should be 32, 33, and 34. The script has been changed back to allow the reg-tests to work again.
    kkeene44 authored Dec 5, 2023
    Copy the full SHA
    35d36d2 View commit details

Commits on Dec 12, 2023

  1. Add ghg_input=0 to namelists with non-compatible radiation options

        By default, ghg_input is turned on. This is only compatible with radiation options: CAM, RRTM, Dudhia, RRTMG, and RRTMG fast. There are several namelists in the regression tests that use other options and therefore the model is not able to run for those tests. All namelists that include non-compatible radiation options now include ghg_input=0 in the &physics record.
    kkeene44 committed Dec 12, 2023
    Copy the full SHA
    22922ae View commit details
  2. Merge pull request #4 from kkeene44/add_ghg_input_0_namelists

    By default, ghg_input is turned on. This is only compatible with radiation options: CAM, RRTM, Dudhia, RRTMG, and RRTMG fast. There are several namelists in the regression tests that use other options and therefore the model is not able to run for those tests. All namelists that include non-compatible radiation options now include ghg_input=0 in the &physics record.
    
    This was committed previously, but due to some debugging, it had to be reverted. It is now being added again as a new commit.
    kkeene44 authored Dec 12, 2023
    Copy the full SHA
    416918d View commit details
Loading