[MOAB-dev] A PDE example with MOAB.
Vijay S. Mahadevan
vijay.m at gmail.com
Wed Apr 13 15:59:06 CDT 2011
Jed,
I will check out the dohp library and the test programs to understand
MOAB usage for elliptic problems. It looks like parts of the library
already provide the functionality that I was planning to do for
example, like figuring out dof numbering, connectivity, evaluating
basis on an element etc. These are very basic FEM building blocks and
your library will help refine my understanding.
Thanks,
Vijay
On Wed, Apr 13, 2011 at 3:43 PM, Jed Brown <jed at 59a2.org> wrote:
> On Wed, Apr 13, 2011 at 22:15, Vijay S. Mahadevan <vijay.m at gmail.com> wrote:
>>
>> I will definitely look at NEK as per your suggestion but if they only
>> use MOAB to read the mesh and convert it to their own mesh data
>> structures, it beats the purpose of my question. Thanks for the
>> pointer though.
>
> I have a library that does a bit of a hybrid. A key aspect is to retain
> enough structure to make high-order and composite finite element methods
> efficient while still having reasonable performance for low order. I don't
> think it's really what you're looking for because it just pulls out arrays
> for most tasks (though it doesn't maintain a full mesh data structure on its
> own), but I use sets and tags for some purposes. Be warned that it is quite
> immature and since I don't have any users that I know of, I change things
> pretty arbitrarily. There are also several places that assume hex elements
> rather than work through the correct API. Let me know if you have questions.
> https://github.com/jedbrown/dohp
> MOAB/iMesh is not user-visible in a typical assembly loop, so Dohp is
> probably irrelevant to you
> https://github.com/jedbrown/dohp/blob/master/src/fs/tests/ellip.c#L430
More information about the moab-dev
mailing list