Merge noaadevelop updates 08282026 - #46
Merged
Merged
Conversation
…'t updated during latest merge of gsl/develop.
…he gsl/MPAS_stoch_physics in the stochastic_physics repo.
…teger seed workaround.
… smoke) from "output" to "output_smoke" (and file from "history..." to "history_smoke...". This is necessary because the stream name "output" is already taken by the main output stream, and having the same name for two different output streams apparently causes SMIOL I/O errors during the forecast (and incorrect/corrupted history*.nc files).
…) no stale stream_list.atmosphere files exist in the two default_inputs directories (one under core_atmosphere and the other immediately under the MPAS-Model top-level directory), and (2) for the atmosphere core, all files (stream-related as well as namelist) in the top-level directory are backed up before new such files are copied from the default_inputs directory back up a level into the top-level directory. Previously, existing (and thus possibly outdated) stream_list.atmosphere.* files in the top-level directory were not being replaced by newer ones in default_inputs, and that was causing unexpected (and wrong) behavior. Probably a similar fix is needed for the init_atmsophere core and maybe even other ones.
…ll as its output file) so it doesn't conflict with the default output stream.
…tochastic_physics's master branh will gradually happen.
…/MPAS_stoch_physics_try_merge_stoch_master
…tochastic_physics code know that the dycore being used is MPAS.
…ill instead be defined in the Makefile for stochastic_physics only (in a separate commit into the stochastic_physics repo) since it is only needed by the stochastic_physics submodule.
…e that is now added in the Makefile in stochastic_physics).
…s the TEMPO tables.
…the top level of MPAS-Model.
…hat generates the data tables for the TEMPO microphysics scheme. This is necessary because the makefile invoked (Makefile.intel) is only for the intel fortran compiler but the CI tests for the repo include build tests with gnu fortran (which are failing with these lines present).
…building TEMPO's executable for generating microphysics tables.
…nflicts with noaa/develop branch.
…oaa/develop branch into this one (src/core_atmosphere/mpas_atm_core.F), commit six manually-merged versions of files that github reports will have conflicts when noaa/develop is merged in. This should avoid those conflicts.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
…ted and propogated to other directories.
…ations to whole-physics tendencies. This should not make a difference.
…output * Add 5 diagnostics variables to output. All are time-maxima (since last output time): -Instantaneous precipitation rate -Composite reflectivity -1-minute average precipitation rate -5-minute average precipitation rate -10-minute average precipitation rate * Fix to correct 1-/5-/10-minute average prate calculation. * Fix error in character string length in warning message. * Requested changes to code to contract loopaple code. * Add IF statements to control when maximum precipitation rate calculations should be computed based on choice of microphysics scheme. * Corrected bug for sub-hourly max prate calculation * max_prate code cleanup. Includes removal of pseudo-SPPT temporarily added for idealized testing. * Correct max composite reflectivity logic for select MP schemes. * Modified spacing in Registry to match tabbing instead of repeated single-spaces * Update README.md --------- Co-authored-by: Clark Evans <clark.evans@noaa.gov> Co-authored-by: Dustin Swales <dustin.swales@noaa.gov>
…for make don't interfere with the ones for cmake); also fix naming bugs (e.g. the intel MPI one should be Intel-MPI, not AUTOTOOLS).
… except building with intel.
…ranch Merge stochastic physics (SPPT only) into GSL's develop branch
Add aerosol emission for TEMPO MP
* Add a safeguard for smoke inputs. * Update version number --------- Co-authored-by: Clark Evans <clark.evans@noaa.gov>
…entation faults during LBC/IC generation (ufs-community#263) * Safeguard invalid scalar indices to prevent segmentation faults during LBC/IC genereation * Change to a more robust safe guard * revert changes on index_nwfa, index_nifa outside the init_atm_case_lbc subroutine * fine tuning
…cessfully * detect NETCDF_C_ROOT and NETCDF_FORTRAN_ROOT automatically for the make system, to be consistent with the CMake system * update the stochastic_physics submodule hash add "$(RM) -r libchem" * Use all capitalized NETCDF_C_ROOT/NETCDF_FORTRAN_ROOT in the Makefile * Update README.md --------- Co-authored-by: Dustin Swales <dustin.swales@noaa.gov>
…ty#281) * allow switching on/off the compiling of stochastic_physics * CMake uses 'build.sh -s' to compile with stochastic_physics * fine tuning * Apply batched suggestions from code review Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> * add separate build tests for stochastic_physics remove the NetCDF, BLAS/MKL installation for the non-stochastic tests * update the build test name * update build_mpas_stoch.yml * update build_mpas_intel.yml and build_mpas_intel_stoch.yml * make LAPACK_LIBS optional based on whether to compile with stochastic_physics * make LAPACK_LIBS optional for ifort_icx and intel-mpi-ursa as well * revert hardcoded MPAS_USE_MPI_F08 * Update README.md --------- Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Co-authored-by: Dustin Swales <dustin.swales@noaa.gov>
…unity#283) * Update intel-llvm-mpi Make target Enables optional stochastic physics compile functionality for the intel-llvm-mpi Make target * Update gfortran Make target * Update version number
…p_updates_08282026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The title above should be a 1 line short summary of the pull request (i.e. what the project the PR represents is intended to do).
Enter a description of this PR. This should include why this PR was created, and what it does.
Testing and relations to other Pull Requests should be added as subsequent comments.
See the below examples for more information.
MPAS-Dev/MPAS#930
MPAS-Dev/MPAS#931
Mandatory Questions
Priority Reviewers