Re: [ice-dev] DTK for converting meshes for ICE?

["Billings, Jay Jay" <billingsjj@xxxxxxxx>]

Stuart,

Okay, great. Do you have any time to sit down with us next week?

Jay

Jay Jay Billings
Oak Ridge National Laboratory
Twitter Handle: @jayjaybillings

---

From: Slattery, Stuart R.
Sent: Thursday, May 19, 2016 9:52 PM
To: Billings, Jay Jay
Cc: ice-dev@xxxxxxxxxxx
Subject: Re: DTK for converting meshes for ICE?

 

Hi Jay

This is a good idea. I think the big thing right now that would prevent us from doing this is that our interfaces for mesh data are read only so we wouldn’t have the write capability needed to generate the other mesh. Also, our interfaces may not be rich enough to do a full copy - all information may not be transferred.

I think its certainly worth some more discussion, however, to flesh out how this might work.

Stuart

-- 
Stuart R. Slattery, Ph.D.
Computer Science and Mathematics Division
Oak Ridge National Laboratory
office: 865.574.8774
fax: 865.241.0381

On May 19, 2016, at 9:20 PM, Billings, Jay Jay <billingsjj@xxxxxxxx> wrote:

Stuart,

The team and I were talking today about some upcoming work we have to develop a mesh conversion tool that ICE can use to convert between its own mesh format and others like Exodus and Silo. I was wondering if DTK could help with this? Alex thought that it might, and that it could be done with a minimal amount of work by creating a new copy operator for each mesh type supported by DTK as well as the required implementations for ICE, (Entities, etc.). We're not looking to do any mappings, just straight conversions between formats.

It would be cool to get your thoughts on this. If we could use DTK to do the conversions/copies between different mesh formats then it would save us a lot of time.

Jay

Jay Jay Billings
Oak Ridge National Laboratory
Twitter Handle: @jayjaybillings