Yes, this is more clear! :) Xujun
On Fri, Nov 21, 2014 at 4:46 PM, Dmitry Karpeyev
wrote:
> Ben,
>
> Xujun and I work on particles in fluid -- point particles for now,
> generalizing to colloidal suspensions (of extended particles later).
> In particular Xujun has a few ideas for using enriched
Thank you for your answer and sharing those information.
Yes, I am working with Dmitry at Argonne:-). We have considered using the
xfem/pum to model particulate flow problems which may involve either
singular type enrichment or interface type enrichment. I have also worked
on xfem/lsm modeling of
Ben,
Xujun and I work on particles in fluid -- point particles for now,
generalizing to colloidal suspensions (of extended particles later).
In particular Xujun has a few ideas for using enriched bases he wanted to
try. These may be related to the basis enrichment ideas we had discussed a
few mon
On Fri, Nov 21, 2014 at 1:57 PM, Xujun Zhao wrote:
> Thank you very much for those information. If this involves MOOSE, I think
> I should bring Dmitry in :-)
>
Definitely. Are you working with him? We work with him quite a bit, and
we've had some discussions on this topic in the past.
> It
On Fri, 21 Nov 2014, Benjamin Spencer wrote:
I could definitely be doing something wrong here -- I came up with
my method for adding elements and nodes and deleting elements based
on trial and error. I'm pretty sure we're not explicitly calling
DofMap::reinit() anywhere. Does it get called by
If you want to look at my code, it on my branch of MOOSE called
xfem_phantom at g...@github.com:bwspenc/moose. Look at the file
moose/framework/src/base/XFEM.C in the cut_mesh_with_efa() method.
Every time an element gets cut by a crack, I need to create new nodes
identical to some of the nodes o
On Fri, 21 Nov 2014, Benjamin Spencer wrote:
the prolongation/restriction code used for adaptive refinement in
libmesh is getting hung up dealing with the nodes that I create in
XFEM because they don't have old dof indices. I've made a couple of
small changes to my version of libmesh to get th
Thank you very much for those information. If this involves MOOSE, I think
I should bring Dmitry in :-)
It seems both LibMesh and MOOSE are working to implement xfem on fracture
problems. Is this for dynamic cracks or just static ones? How about the
weak discontinuity problems, for example, materi
> As for the old dof indices bit, I'd be happy to participate in that
>> discussion, especially if you can create the problem with a minimal example.
>>
>>
I appreciate the offer. I'll work on setting up a really minimal test
case.
-Ben
---
We've tried a few techniques for integrating the partial elements. For our
problems, we're really interested in using the original integration points
to avoid the need to map any stateful data to new integration points.
We've experimented with some techniques to use the original integration
points
Yes, I am working on XFEM in MOOSE. I'm following a different route from
what Ben Kirk is doing -- I'm using the phantom node approach rather than
adding degrees of freedom to enriched nodes.
We have a reasonably complete implementation of brittle fracture in 2D with
our code, and have used it to
I'm curious if you've had any issues relating to integrating over
discontinuities, as that's the first & only thing I've taken a stab at.
As for the old dof indices bit, I'd be happy to participate in that discussion,
especially if you can create the problem with a minimal example.
-Ben
-
Ben Spencer (copied on this email) has done quite a bit of this in MOOSE (
mooseframework.org ) as well. Maybe he'll tell us when it's going to get
committed to the main MOOSE repo! :-)
Derek
On Fri, Nov 21, 2014 at 1:27 PM, Roy Stogner
wrote:
>
> On Fri, 21 Nov 2014, Xujun Zhao wrote:
>
> >
On Fri, 21 Nov 2014, Xujun Zhao wrote:
> I guess I post it at the wrong place.
libmesh-users was the right place; unfortunately I suspect you posted
at the wrong *time*. Ben Kirk would be the expert on the current
preliminary XFEM+libMesh status, but he's probably too busy to follow
the mailing
Hi all,
I guess I post it at the wrong place. Now I re-send it to the developers'
maillist and hope to get some opinions and advice. I have built my xfem
codes with another FEM library FEniCS/dolfin when I studied at
Northwestern, I am curious about the possibility to move it to LibMesh.
Thank you
On Sat, 23 Mar 2013, Kirk, Benjamin (JSC-EG311) wrote:
> On Mar 23, 2013, at 5:51 PM, Derek Gaston wrote:
>
>> Does anyone else (Roy? Paul?) want to be on the conference call as well?
>
> I hope so!
Yes for me, at least. I can give Paul the Cliff's Notes if he's too
swamped to join in.
---
Roy
On 03/23/2013 10:54 PM, Kirk, Benjamin (JSC-EG311) wrote:
> But I was thinking since the level-set scheme is central to a lot of
> interface tracking stuff (not just X-FEM) direct library support might
> be worthwhile.
I definitely agree, level-set functionality would be useful in many
context
On Mar 23, 2013, at 5:51 PM, Derek Gaston wrote:
> We've been doing this work in preparation for talking to you and Roy so we
> would have our ducks in a row for intelligent conversation about what needs
> to be added to libMesh. It appears as if that time has now come ;-)
>
> Let's put toget
On Sat, Mar 23, 2013 at 10:19 AM, Kirk, Benjamin (JSC-EG311) <
benjamin.kir...@nasa.gov> wrote:
> Anyone out there doing anything with the extended finite element method?
>
Yes. We actually have a fairly large push in this direction right now. We
got a proposal funded for this year (and probabl
On Mar 23, 2013, at 1:43 PM, David Knezevic wrote:
> Regarding (2): Are you thinking of adding a libMesh example that implements
> transport of a signed distance function using DG? Or are you thinking about
> adding core functionality related to this, e.g. a new System subclass for
> handling
This sounds very cool. I haven't needed XFEM before personally, but I
can imagine using it in the near future, e.g. for dealing properly with
crack tips.
Regarding (2): Are you thinking of adding a libMesh example that
implements transport of a signed distance function using DG? Or are you
th
21 matches
Mail list logo
