diff --git a/modules/doc/content/newsletter/2024/2024_09.md b/modules/doc/content/newsletter/2024/2024_09.md index 82e2788bbccb..bd3b3c1dc52c 100644 --- a/modules/doc/content/newsletter/2024/2024_09.md +++ b/modules/doc/content/newsletter/2024/2024_09.md @@ -1,19 +1,7 @@ # MOOSE Newsletter (September 2024) -!alert! construction title=In Progress -This MOOSE Newsletter edition is in progress. Please check back in October 2024 -for a complete description of all MOOSE changes. -!alert-end! - ## MOOSE Improvements -### Specific internal energy added to Solid Properties objects - -The [ThermalSolidProperties.md] objects from the [Solid properties module](modules/solid_properties/index.md) -now provide interfaces to compute the specific internal energy as a function of -temperature. This new interface is useful, for example, in measuring the -internal energy in solids for energy conservation verification. - ### Exit Code Management The ability was added to allow an application to set its exit code, which can @@ -40,8 +28,55 @@ This change should be made as soon as possible as the logic that was changed her impacts the application command line options `--run` and `--copy-inputs` used for executing installed MOOSE applications. -## libMesh-level Changes +### Deployment of the ActionComponents system + +[ActionComponents](syntax/ActionComponents/index.md) were introduced to MOOSE. They are derived from the [Action](Action.md) class and are tasked with +building the geometrical definition of a system. They can be specialized to a given `Physics` and discretization, +or they can be set to instantiate any `Physics` onto their domain. + +The main difference with the Thermal Hydraulics module [Components](syntax/Components/index.md) is that `ActionComponents` are derived +from an `Action` base class and therefore can follow the traditional task-based simulation setup, while `Components` are derived +from `MooseObject` and require inter-component dependency resolution for the simulation setup. +Other differences include the possibility to use `MeshGenerators` in tandem with `ActionComponents`. -## PETSc-level Changes +## MOOSE Modules Changes + +### Release of the fluid properties external submodules + +Fluid properties submodules for air, carbon dioxide, helium, nitrogen, sodium and potassium, including +both single phase and two phase properties, were added to MOOSE. They are optional submodules, and +they can be downloaded using the command below. Once downloaded, an application must use the fluid properties +module to be able to use these properties. + +``` +cd ~/projects/moose +git submodule update --init --checkout modules/fluid_properties/contrib/ +``` + +### Physics for k-epsilon turbulence + +[WCNSFVTurbulencePhysics.md] was added to the Navier Stokes module. It facilitates the setup of the k-epsilon +equations in a Navier Stokes flow simulation with the weakly compressible finite volume discretization. It is currently +only available for the Newton solver. Performance is limited for larger problems. +A similar `Physics` should be created for the high performance linear finite volume segregated solver in the next fiscal year. + +### Specific internal energy added to Solid Properties objects + +The [ThermalSolidProperties.md] objects from the [Solid properties module](modules/solid_properties/index.md) +now provide interfaces to compute the specific internal energy as a function of +temperature. This new interface is useful, for example, in measuring the +internal energy in solids for energy conservation verification. ## Bug Fixes and Minor Enhancements + +- Linking warnings due to visibility settings differences at compile-time of various templates + were resolved by using template instantiation declaration in the affected headers. +- The framework folders are now all built using the folder unity technique which speeds up the compilation. + As a reminder, unity builds can be disabled by setting `export MOOSE_UNITY=false` to reduce memory use during compilation. +- The `execute_on` parameter was removed from `Function` objects, as they are generally never executed on + an execution schedule but rather computed on-the-fly on every call. +- The [ProjectionAux.md] specifically checks for mixed order projections to avoid double-counting nodes present + in both lower and higher dimensional blocks +- The [QuadraturePointsPositions.md] object was added to output quadrature points from elements in either the mesh or + subdomains of the mesh to JSON. They can also be used to create MultiApps, as in the [QuadraturePointMultiApp.md] +- A new MOOSE container is available for profiling purposes using Google's `gpertools` and `pprof` software. diff --git a/modules/doc/content/newsletter/2024/2024_10.md b/modules/doc/content/newsletter/2024/2024_10.md new file mode 100644 index 000000000000..bc2d780633a1 --- /dev/null +++ b/modules/doc/content/newsletter/2024/2024_10.md @@ -0,0 +1,24 @@ +# MOOSE Newsletter (October 2024) + +!alert! construction title=In Progress +This MOOSE Newsletter edition is in progress. Please check back in November 2024 +for a complete description of all MOOSE changes. +!alert-end! + +## MOOSE Improvements + +## libMesh-level Changes + +## PETSc-level Changes + +## Bug Fixes and Minor Enhancements + +## Conda Package Changes + +- `moose-mpi`, our lowest level package, has been updated to allow users wishing to + build their own PETSc, libMesh, WASP to do so without needing to install any + additional Conda packages. +- HDF5 has been downgraded to solve issue: [Floating Point Exception, #28350](https://github.com/idaholab/moose/issues/28350) +- The minimum MacOS build SDK has been bumped to MacOS Big Sur (11.3). Users of + MacOS versions older than this may run into issues building and running MOOSE, + MOOSE dependencies, or other MOOSE-based applications. diff --git a/modules/doc/content/newsletter/index.md b/modules/doc/content/newsletter/index.md index cfa9c5cb740f..44986a092710 100644 --- a/modules/doc/content/newsletter/index.md +++ b/modules/doc/content/newsletter/index.md @@ -6,6 +6,7 @@ monthly to the [MOOSE discussion forum](contact_us.md) as well as provided below ## 2024 +- [September, 2024](2024_09.md) - [August, 2024](2024_08.md) - [July, 2024](2024_07.md) - [June, 2024](2024_06.md)