-
## Reason
`MooseConfig.h` cannot be found in `moose/framework/build/header_symlinks` as it is only created after the symlinks are created. This is curious. I wonder how this file is ever found unless…
-
-
## Reason
To aid in developer experience it would be useful to have the unit test automatically run from an application/module run_tests script.
## Design
Add the ability within TestHarness.b…
-
## Reason
When we specify `--use-split` on command line, we possibly are expecting the sub-apps to use a split mesh file and a different file as well. This feature is not available currently as showe…
-
## Reason
It can be done but it s not well known.
Most people only know about the --use-split method
## Design
Just add some docs to split meshes
## Impact
Easier for large runs
-
## Reason
As pointed out in https://github.com/idaholab/moose/pull/20408#discussion_r1083055339 and https://github.com/idaholab/moose/pull/20408#issuecomment-1398977483 we are avoiding interference w…
-
Compare the inheritance graph on
http://mooseframework.org/docs/doxygen/modules/classSplitCHParsed.html
with this graph I generated locally (using Doxygen 1.8.10)
![classsplitchparsed__inherit__gra…
-
### Description of the enhancement or error report
As we've discussed several times in the recent past, SemiLocal != Ghosted. This is actually a big problem because we use `isSemiLocal()` throughout …
-
### Description of the enhancement or error report
The `InitialCondition::compute()` method is copied from libMesh:
https://github.com/idaholab/moose/blob/devel/framework/src/ics/InitialCondition.…
-
### Description of the enhancement or error report
LibMesh Parsed functions are _not_ thread safe. And thus Moose Functions are not guaranteed to be thread safe. It looks like the framework does set …