@Manav:
Were you able to run DTK and use it for solution transfer?
I tried doing it but I was unable to transfer solutions across meshes. I think
dtk for libMesh may be broken. If you get it to work, kindly let me know
Thanks and Regards
Vegnesh
________________________________________
From: libmesh-users-requ...@lists.sourceforge.net
[libmesh-users-requ...@lists.sourceforge.net]
Sent: Thursday, August 11, 2016 5:43 AM
To: libmesh-users@lists.sourceforge.net
Subject: Libmesh-users Digest, Vol 123, Issue 20
Send Libmesh-users mailing list submissions to
libmesh-users@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/libmesh-users
or, via email, send a message with subject or body 'help' to
libmesh-users-requ...@lists.sourceforge.net
You can reach the person managing the list at
libmesh-users-ow...@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Libmesh-users digest..."
Today's Topics:
1. question about distributed mesh (Manav Bhatia)
2. dtk and petsc (Manav Bhatia)
3. Re: dtk and petsc (John Peterson)
4. Re: question about distributed mesh (Manav Bhatia)
5. Re: question about distributed mesh (John Peterson)
6. Re: question about distributed mesh (Manav Bhatia)
7. Re: question about distributed mesh (Roy Stogner)
8. Re: question about distributed mesh (Manav Bhatia)
----------------------------------------------------------------------
Message: 1
Date: Wed, 10 Aug 2016 17:17:11 -0500
From: Manav Bhatia <bhatiama...@gmail.com>
Subject: [Libmesh-users] question about distributed mesh
To: libmesh-devel <libmesh-users@lists.sourceforge.net>
Message-ID: <d9f290b0-9929-4a22-84e4-f2495c63d...@gmail.com>
Content-Type: text/plain; charset=us-ascii
Hi,
Is it possible to tell/force DistributedMesh to maintain a copy of a
selected set of elements across all processors?
If this is currently is not a part of the functionality, is there a quick
and dirty way of accomplishing the same?
I would greatly appreciate your comments.
Thanks,
Manav
------------------------------
Message: 2
Date: Wed, 10 Aug 2016 17:20:51 -0500
From: Manav Bhatia <bhatiama...@gmail.com>
Subject: [Libmesh-users] dtk and petsc
To: libmesh-devel <libmesh-users@lists.sourceforge.net>
Message-ID: <22c45643-1440-49de-9702-fbee77160...@gmail.com>
Content-Type: text/plain; charset=us-ascii
Hi,
If I intend to use dtk from inside libMesh, am I constrained to using
trillions for the system linear solver, or can I also have access to petsc in
addition to dtk?
Thanks,
Manav
------------------------------
Message: 3
Date: Wed, 10 Aug 2016 16:24:13 -0600
From: John Peterson <jwpeter...@gmail.com>
Subject: Re: [Libmesh-users] dtk and petsc
To: Manav Bhatia <bhatiama...@gmail.com>
Cc: libmesh-devel <libmesh-users@lists.sourceforge.net>
Message-ID:
<caj-bnt6w40ilttbvxjmcrsp7khskyrpwypkjtx18gu6yj82...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
On Wed, Aug 10, 2016 at 4:20 PM, Manav Bhatia <bhatiama...@gmail.com> wrote:
> Hi,
>
> If I intend to use dtk from inside libMesh, am I constrained to using
> trillions for the system linear solver, or can I also have access to petsc
> in addition to dtk?
>
You should be able to build libmesh with both PETSc and Trilinos enabled...
we have some tests of this on the MOOSE CI server.
The default solver used will be PETSc, see default_solver_package() in
libmesh.C
--
John
------------------------------
Message: 4
Date: Wed, 10 Aug 2016 17:40:52 -0500
From: Manav Bhatia <bhatiama...@gmail.com>
Subject: Re: [Libmesh-users] question about distributed mesh
To: libmesh-devel <libmesh-users@lists.sourceforge.net>
Message-ID: <7cacd1da-7ab8-43e2-a332-3f07080d8...@gmail.com>
Content-Type: text/plain; charset=us-ascii
Seems like DistributedMesh::add_extra_ghost_elem() does the trick.
-Manav
> On Aug 10, 2016, at 5:17 PM, Manav Bhatia <bhatiama...@gmail.com> wrote:
>
> Hi,
>
> Is it possible to tell/force DistributedMesh to maintain a copy of a
> selected set of elements across all processors?
>
> If this is currently is not a part of the functionality, is there a quick
> and dirty way of accomplishing the same?
>
> I would greatly appreciate your comments.
>
> Thanks,
> Manav
------------------------------
Message: 5
Date: Wed, 10 Aug 2016 16:43:13 -0600
From: John Peterson <jwpeter...@gmail.com>
Subject: Re: [Libmesh-users] question about distributed mesh
To: Manav Bhatia <bhatiama...@gmail.com>
Cc: libmesh-devel <libmesh-users@lists.sourceforge.net>
Message-ID:
<caj-bnt5qpasqbemjnupzrr4alwyuqetdee-xn8hwsbnahfh...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
On Wed, Aug 10, 2016 at 4:40 PM, Manav Bhatia <bhatiama...@gmail.com> wrote:
> Seems like DistributedMesh::add_extra_ghost_elem() does the trick.
>
Roy is also in the midst of generalizing the algorithms used to control
which elements are ghosted where, so you may want to keep an eye on what
he's doing...
--
John
------------------------------
Message: 6
Date: Wed, 10 Aug 2016 17:58:01 -0500
From: Manav Bhatia <bhatiama...@gmail.com>
Subject: Re: [Libmesh-users] question about distributed mesh
To: John Peterson <jwpeter...@gmail.com>
Cc: libmesh-devel <libmesh-users@lists.sourceforge.net>
Message-ID: <9fc1cb05-8843-41bf-9561-47fd90fe3...@gmail.com>
Content-Type: text/plain; charset=us-ascii
will do. Thanks!
-Manav
> On Aug 10, 2016, at 5:43 PM, John Peterson <jwpeter...@gmail.com> wrote:
>
>
>
> On Wed, Aug 10, 2016 at 4:40 PM, Manav Bhatia <bhatiama...@gmail.com
> <mailto:bhatiama...@gmail.com>> wrote:
> Seems like DistributedMesh::add_extra_ghost_elem() does the trick.
>
> Roy is also in the midst of generalizing the algorithms used to control which
> elements are ghosted where, so you may want to keep an eye on what he's
> doing...
>
> --
> John
------------------------------
Message: 7
Date: Wed, 10 Aug 2016 18:54:55 -0500 (CDT)
From: Roy Stogner <royst...@ices.utexas.edu>
Subject: Re: [Libmesh-users] question about distributed mesh
To: Manav Bhatia <bhatiama...@gmail.com>
Cc: libmesh-devel <libmesh-users@lists.sourceforge.net>
Message-ID:
<alpine.lrh.2.20.1608101847500.31...@spark.ices.utexas.edu>
Content-Type: text/plain; charset=US-ASCII; format=flowed
On Wed, 10 Aug 2016, Manav Bhatia wrote:
> will do. Thanks!
If you want to chime in or just read my thoughts on the design
questions, the issue where I've been documenting them is
https://github.com/libMesh/libmesh/issues/1028
The first third of the design got merged in
https://github.com/libMesh/libmesh/pull/1057
and I hope to have the next third by the end of the week.
This is going to have libmesh_experimental() all over it for a while;
I think the design overview is solid but API arguments, return values,
etc. aren't set in stone yet.
---
Roy
------------------------------
Message: 8
Date: Thu, 11 Aug 2016 05:42:54 -0500
From: Manav Bhatia <bhatiama...@gmail.com>
Subject: Re: [Libmesh-users] question about distributed mesh
To: Roy Stogner <royst...@ices.utexas.edu>
Cc: libmesh-devel <libmesh-users@lists.sourceforge.net>
Message-ID: <15e577d3-7f62-4f19-b99b-33dba83f1...@gmail.com>
Content-Type: text/plain; charset=utf-8
Thanks for pointing me to the discussions, Roy.
So if I understand correctly, the current implementation of
DistributedMesh::add_extra_ghost_elem() only provides the G() version of your
new API without an ?evaluable? entity? If my interest is in the E() entity,
would it be best to wait for your API, or is there a way to get it to work in
current libMesh? Perhaps follow the implementation in MOOSE?
-Manav
> On Aug 10, 2016, at 6:54 PM, Roy Stogner <royst...@ices.utexas.edu> wrote:
>
>
> On Wed, 10 Aug 2016, Manav Bhatia wrote:
>
>> will do. Thanks!
>
> If you want to chime in or just read my thoughts on the design
> questions, the issue where I've been documenting them is
> https://github.com/libMesh/libmesh/issues/1028
>
> The first third of the design got merged in
> https://github.com/libMesh/libmesh/pull/1057
> and I hope to have the next third by the end of the week.
>
> This is going to have libmesh_experimental() all over it for a while;
> I think the design overview is solid but API arguments, return values,
> etc. aren't set in stone yet.
> ---
> Roy
------------------------------
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. http://sdm.link/zohodev2dev
------------------------------
_______________________________________________
Libmesh-users mailing list
Libmesh-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-users
End of Libmesh-users Digest, Vol 123, Issue 20
**********************************************
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. http://sdm.link/zohodev2dev
_______________________________________________
Libmesh-users mailing list
Libmesh-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-users
