[MOAB-dev] MOAB insights?

[Nico Schlömer]

Thanks everyone!

I believe that right now, I cannot efficiently use MOAB yet. We really need
to be able to read from standardized file formats like XDMF, VTU, Exodus.
This is what the tool set is composed around, and it'd probably much work
to get it right for MOAB's custom HDF5-thing.

That said, I'd be happy to help out with extending MOAB in these
directions. Perhaps after the release, we can arrange a plan.

Cheers,
Nico

On Fri, Oct 30, 2015 at 12:40 AM Grindeanu, Iulian R. <iulian at mcs.anl.gov>
wrote:

> Hi Nico,
> Sorry I missed your message
> I modified one of the examples to construct all edges and faces, and
> output them in some files
>
> after compiling it, you can launch it with
>
> ./HelloMOAB
>
> or
> ./HelloMOAB <other_file>
>
> other_file can be any file that can be loaded in MOAB, in serial (for
> example, a gmsh file)
>
> for parallel IO, you can look at HelloParMOAB example, or tests in
> test/parallel
>
>
> There is a list of examples on doxygen page, with more links on how is
> data accessed.
> http://ftp.mcs.anl.gov/pub/fathom/moab-docs/examples.html
>
>
>
> Iulian
>
> ------------------------------
> *From:* Nico Schlömer [nico.schloemer at gmail.com]
> *Sent:* Thursday, October 29, 2015 3:37 PM
>
> *To:* Grindeanu, Iulian R.; moab-dev at mcs.anl.gov
> *Subject:* Re: [MOAB-dev] MOAB insights?
> Absolutely!
>
> I'm interested to see
>  * how I/O works,
>  * how edges/faces arecreated,
>  * how relationships are queried (Which cells does this face border on?
> Which nodes does this cell have? etc)
>
> If there's an example in the sources, I'd be more than happy to look at
> that, too, of course.
>
> Cheers,
> Nico
>
>
> On Thu, Oct 29, 2015 at 9:19 PM Grindeanu, Iulian R. <iulian at mcs.anl.gov>
> wrote:
>
>>
>> ------------------------------
>> *From:* Nico Schlömer [nico.schloemer at gmail.com]
>> *Sent:* Thursday, October 29, 2015 12:45 PM
>> *To:* Grindeanu, Iulian R.; moab-dev at mcs.anl.gov
>> *Subject:* Re: [MOAB-dev] MOAB insights?
>>
>> > what means long for you, and what is the size of the mesh on one
>> > rank? what is a cell for you? a polyhedra or a
>> > tet/hex/prism/quad/triangle?
>>
>> For me, long means (much) longer than the actual (linear) solver in the
>> end. On a test cube [1] of 140k tets and 27k nodes, creating edges takes
>> about one minutes, faces about two (on one core that is). The linear solver
>> in the end takes about seven seconds.
>>
>> hmmm, that is too long, indeed.
>>
>> For moab, creating the edges and/or faces for that size of a mesh is on
>> the order  of seconds, on a laptop
>>
>> I will write a small example if you are interested
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/moab-dev/attachments/20151031/48d9eab2/attachment.html>