-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Description
It might be a good idea to think of alternative ways to couple AEGIS outputs to MOOSE.
Previously I managed to couple AEGIS heatfluxes to MOOSE via writing them out in a csv format (x,y,z, heatflux) and using that to create a constant heat source function applied as a Neumann BC in a heat transfer solve in MOOSE. This works but I'm sure that there are better ways to do this.
Limitations of my current approach. (Will update as I think of any others):
- Relies on MOOSE's
NearestReporterCoordinatesFunctionwhich assigns a heatflux value to the nearest (spatially) node in the exodus mesh. I just don't think this is the best method, results in interpolation between nodes across elements and doesn't take into account the fact that I can now launch multiple particles per element. - If I ever wanted to create a time dependent heatflux function in MOOSE which relied on multiple AEGIS "shots" with varying eqdsks/equilibrium definitions then I think this file based approach won't really suffice.
- With MOAB, I have the ability to attach metadata to elements in a mesh so I feel like there must be a way I can just attach this heatflux data to the exodus mesh that is read into MOOSE.
Metadata
Metadata
Assignees
Labels
No labels