-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Current state of the project #5
Comments
Which of the planned additions is of interest to you? If you are interested in visualization, there is initial support for FMS in VisIt: https://visit.llnl.gov. Are you are interested in contributing or collaborating on some of the planned features? The near future plan is first to extend the data structures to handle inter-processor connectivities, and also, to extend the file I/O to save and read this data -- in other words, to implement parallel data formats. |
I am looking for a mesh format that can represent high-order solutions of various kinds:
Based on this mesh format, I have the following requirements (or rather a wish-list).
I have been investigating several projects, but each has certain drawbacks, which enforced me continue searching for new ones:
Concerning the collaboration, I need to discuss it with my employer whether he allows me to allocate time on working on it. First, I must carefully select a framework (FMS, MFEM format, or something else that you are aware of) that has the future potential:
|
Hi @CsatiZoltan, Based on your wish-list, I don't know a library that supports all the points. And, certainly, FMS lacks support for some of these features: 2 and 3 depend a lot on the format used by the solver that provides the data and if it is compatible with FMS (this will probably be a problem for most mesh libraries); and for 4 and 5 there is currently no support. Ultimately, the goal for FMS is to provide means for connecting the various components of a simulation pipeline: mesh generation and manipulation libraries, discretization and solver libraries, visualization libraries, etc. Also, the idea for the FMS query component is to provide functionality for interpreting the data (e.g. evaluation of values and gradients of the fields at points) from visualization/post-processing libraries. However, developing these features is still in the future. From what I know, at this time, one suitable choice for you may be to use Conduit blueprint with input coming from MFEM (this is supported by Conduit without deep-copying data). Then from Conduit, the data can be used directly in Ascent for in-situ visualization. In the current state, there will be limitations with respect to your wish-list, however, I think there is a path forward for adding missing features. |
I'm interested in this too, for similar purposes (DG-SEM solutions). I'm wondering about the following:
|
I see that the latest commit is from September 2021, setting the version to 0.2.
According to the plans, the in-situ components and the visualization will come in later releases.
Are there any plans to continue this project?
The text was updated successfully, but these errors were encountered: