-
-
Add support in Moose to be able to configure the framework to automatically execute scrips (e.g. connectors) on a schedule or on an event-based trigger
-
These BLAS/Lapack forward declarations conflict with declaration we pull in through PETSc:
https://github.com/Argonne-National-Laboratory/neml/blob/65c2ee4bbfb4f5499f17952e64ed87f85a1ef538/include/ma…
-
# Problem
In the babbler folder created by using the command `./moose/scripts/stork.sh Babbler'.
I try to build a new application, it's still the same.
```
(moose) kimi@DESKTOP-7APSM1S:~/proje…
-
Thank you for providing a64fx solutions for these OSSs. Could you offer a patch for MOOSE framework or a build guide? I need to install it on UTokyo's Wisteria. I have tried several days using your Fu…
-
## Rationale
MOOSE could be and should be faster. I believe much of the work needed to make that happen can be done entirely at the libMesh level, but there will be cases (where MOOSE itself is …
-
## Bug Description
I am trying to compile Cardinal on Sawtooth and get the following error message with `make -j8`:
```
Cardinal is using HDF5 from /home/delcmarc/cardinal/contrib/moose/petsc/…
-
We're about to use this library in a big software project that has strict guidelines about compiler warnings. The parser library emits a bunch of `unused parameter` warnings. We could silence `-Wunuse…
-
### Bug Description
We get these warnings for classes using templated members (especially the variables)
```
ld: warning: direct access in function 'AdvectiveFluxAux::AdvectiveFluxAux(InputParame…
-
I tried running `moose dev` in framework-internal-app. Noticed we're seeing an error in flows about a topic not being available. It seems like we're deleting UserActivity_0_3 topic from the CLI code, …