search

ORNL-CEES / DataTransferKit

A library for multiphysics solution transfer. ARCHIVED
https://datatransferkit.readthedocs.io/en/dtk-3.0/
BSD 3-Clause "New" or "Revised" License
47 stars 26 forks source link

Are there any basic DTK example problems? #557

Closed PeterK26 closed 5 years ago

PeterK26 commented 5 years ago

I have DTK2.0 installed any it passes its self checks, but I'm still not too sure how to start running my own problems. I've looked at the docs for the C API, but a sample problem would be a lot more helpful. Are there any basic examples included anywhere in the installation?

So far I've used DTK through libMesh (there's a solution transfer example using DTK), but the solution changes when it's transferred to the target mesh (as far as I know, the actual solution transfer part is done with DTK). Since this example is behaving strangely, having another simple example would be useful. I'm interested in solution transfer between Exodus II meshes like in libMesh's DTK example.

image

sslattery commented 5 years ago

This is the best example for using libmesh: https://github.com/ORNL-CEES/DataTransferKit/blob/dtk-2.0/packages/Adapters/Libmesh/example/tstMoabtoLibmeshParallelTransfer.cpp

Note that the target mesh in this case is libmesh while the source mesh uses Moab. You can use the target libmesh code as an example of how to replace the source mesh code with libmesh. The internal libmesh example you pointed to uses an even older legacy version of DTK than 2.0 and if I remember they had pinned themselves to a specific repo hash of DTK for their work so I am not surprised that the internal example is not functioning correctly.

PeterK26 commented 5 years ago

Thanks, that example looks very helpful.