[MOAB-dev] h5m format

[JR Cary]

interesting.....J

On 6/2/15 12:56 PM, John Loverich wrote:
> Does Moab have the machinery to write both mesh and simulation data?  
> Obviously I can write the mesh, but I'm wondering if I need to create 
> my own writers for simulation data or do they already exist in moab?  
> Simulation data is just referring to fluid densities on the grid, etc...
>
> Thanks,
>
> John
>
> On Wed, May 20, 2015 at 1:52 PM, Vijay S. Mahadevan <vijay.m at gmail.com 
> <mailto:vijay.m at gmail.com>> wrote:
>
>     You can directly output to vtk in serial or use mbconvert tool
>     under bin directory in your installation to convert the format.
>
>     mbconvert test.h5m test.vtk
>
>     That should work for any files. If there are issues let us know.
>     You can also look at all supported formats by running
>
>     mbconvert -l
>
>     Vijay
>
>     On May 20, 2015 8:27 PM, "John Loverich" <john.loverich at gmail.com
>     <mailto:john.loverich at gmail.com>> wrote:
>
>         Thanks Vijay, also is there a moab format for simulation
>         results?  There is a moab mesh and it's natural to write out
>         data (density for example) corresponding to grid elements
>         (vertices or cell centers for example).  If there is a
>         standard way of doing this, then one can get the commercial
>         visualization tools (like tecplot) to support it.
>
>         John
>
>         On Tue, May 19, 2015 at 9:24 AM, Vijay S. Mahadevan
>         <vijay.m at gmail.com <mailto:vijay.m at gmail.com>> wrote:
>
>             > Hi all, sorry for sending to this address, but couldn't find the
>             proper
>             > place to send questions.
>
>             John, no need to apologize. This is the right place to
>             send these questions.
>
>             > Is there any visualization tool that supports the native
>             Moab mesh format
>             > (h5m)?
>
>             Both Paraview and Visit need to be built from source to
>             visualize the
>             native h5m MOAB format. There are some instructions in [1]
>             but I'm
>             unsure if this is outdated since we've not built the
>             plugin on recent
>             version I think.
>
>             Paraview is a bit easier i.e., compile Paraview from
>             source, configure
>             MOAB using --with-vtk option and install it to a prefix, go to
>             tools/vtkMOABReader and use the CMake configuration to
>             specify both
>             PARAVIEW_DIR and MOAB_DIR to compile the plugin. You can
>             then load the
>             plugin from Paraview and utilize it to natively visualize
>             h5m files.
>
>             We are planning to also make this workflow easier in the
>             coming
>             months. Rajeev, does CMB take care of this right now as it
>             stands ?
>
>             Vijay
>
>             [1] http://sigma.mcs.anl.gov/moab/visualization-with-moab/
>
>             On Tue, May 19, 2015 at 10:09 AM, John Loverich
>             <john.loverich at gmail.com <mailto:john.loverich at gmail.com>>
>             wrote:
>             > Hi all, sorry for sending to this address, but couldn't
>             find the proper
>             > place to send questions.
>             >
>             > Is there any visualization tool that supports the native
>             Moab mesh format
>             > (h5m)?  It seems neither Paraview nor VisIt can read
>             this format, though I
>             > may be mistaken.  On top of that, I'm interested in a
>             standard way to store
>             > field data for a given Moab mesh. Though Moab simply
>             defines the mesh,
>             > suppose I have electric field values stored in a
>             different file linking to
>             > the mesh file.  Obviously I can use vtk or some other
>             format, but would
>             > rather use the Moab HDF5 format directly if possible.
>             >
>             > Thanks,
>             >
>             > John
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/moab-dev/attachments/20150602/7af8215e/attachment.html>