Fierro
Fierro copied to clipboard
lanl
Fierro is a C++ code designed to aid the research and development of numerical methods, testing of user-specified models, and creating multi-scale models related to quasi-static solid mechanics and co...
Currently, Fierro has limited unit testing coverage. This needs to be remedied for the long-term health of the project. Automated unit testing allows for the safe integration of new features...
## Issue When we render the voxel VTK we are going to give to the EVPFFT backend, the positions of the voxels are stored in coordinate space. This can be...
MPI Mesh IO is handled in the Parallel Explicit Solvers class. It also consists of a significant amount of copied code and does not load all of the mesh properties...
For any kind of proper scalability, we rely on MPI. As it stands, we have separate code on top of our mesh classes that operate with MPI. We use Zoltan2...
Some parts of the code use IJK and some use the EnSight node ordering convention. It might not technically be a problem right now, but its bound to cause us...
Keying off of the "output_strain" yaml flag, we allocate space for strain outputs in the elastic module, but we don't actually put anything there leading to seg faults if someone...
Currently some of our code pretends to support restarting. Despite it being an important functionality for HPC users that expect long running jobs (1day+), we don't really support it. We...
Currently HDF5 serialization is a pain. It require a significant amount of boiler plate code to implement and is error prone to modify as we want to serialize new data...