-
**Describe the bug**
Hi! I tried the MOOSE to segment CT on the Windows server with 32 cores. It outputs an error:
```
🔮 PREDICT:
\ [1/1] Preparing data for prediction for S1...Exception in t…
-
Refactor the framework to better manage the infrastructure
-
### Motivation
To get a better picture on the bottlenecks in moose, we should be able to easily profile the code.
### Design
Add gperftools and pprof to the default moose containers.
### Impact
E…
-
-
Dear libmesh community,
This issue requests to make `write_element_data()` (and sister methods) more resistent to missing subdomains.
As you know, [Moose](https://mooseframework.inl.gov/index.ht…
-
Could be just the head or full body
-
Should we simplify the inspector by removing some tabs ?
For example, inspect a group of Classes, there is a "SystemComplexity" tab, a "UML tab, a Nesting tab.
![image](https://github.com/user-att…
-
When propagating a large model, it is slow. Maybe it cannot be easily improved but we should have some progress bar or info bar that shows that the system is working and not blocked
(at least I teste…
-
-
1. If a streaming function already exists with the same source and destination data models specified in the command:
1. The CLI should raise a warning: `Warning: Streaming Function -> already exist…