Closed stvdwtt closed 1 year ago
PostProcessor
class? Going back to the earlier plan to do the analysis in VisIt works for me. I was thinking that we'll eventually need some of this functionality in adamantine itself for the in-build optimization, but since the method there is still up in the air, waiting on it makes sense. Doing it with VisIt should be pretty quick. If/when we do need to bring some of this into adamantine, the PostProcessor
class makes sense as a home for that functionality.
Since we went with VisIt, I'm going to close this for now. If/when we do this in adamantine, we can open a new issue more tailored to what we need.
Motivation: To interact with the optimization framework we need access to certain quantities of the fields (e.g. temperature at a point, maximum von Mises stress).
Proposed implementation:
Initial thoughts for postprocessing options:
Here the field could be a primary field (e.g. temperature) or some pre-defined derived quantities (von Mises stress).
Before I start any work on this, @Rombur, does this sound reasonable? My plan would be to start with just the "field value" one and then add others once we're happy with the interface for that.