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 get some nice results. This year we plan to
get crack branching and 3D working. This code definitely needs some more
cleanup before it's ready to merge into MOOSE. Derek, sometime you and I
need to have a discussion about how this should fit in to the MOOSE
architecture so that I can move forward with cleaning the code up to get it
ready to merge in. I'm confident that the way I've currently hacked it in
isn't the answer, but it shouldn't be too hard to rearrange things.
The big thing that's preventing me moving forward with merging this into
the mainline MOOSE is that 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 that to work, but
it breaks other stuff. We've talked about this in the past, and need to
revive that discussion. It hasn't been a show stopper for me proceeding
forward with my work so far, which is why I haven't taken the time to get
to the bottom of the issue, but I need to. It would be really helpful to
talk with someone who knows that code better. Is that you, Roy?
-Ben
Benjamin Spencer
Fuels Modeling and Simulation
Idaho National Laboratory
PO Box 1625
Idaho Falls, ID 83415-3840
208-526-1683
On Fri, Nov 21, 2014 at 12:18 PM, Derek Gaston <fried...@gmail.com> wrote:
> 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 <royst...@ices.utexas.edu>
> 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 lists closely right now.
>>
>> Some of the code that he put in is here:
>> https://github.com/libMesh/libmesh/pull/326
>>
>> if you'd like to look it over. I don't know how much more effort
>> would be necessary to get it completed.
>> ---
>> Roy
>>
>>
>> ------------------------------------------------------------------------------
>> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
>> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
>> with Interactivity, Sharing, Native Excel Exports, App Integration & more
>> Get technology previously reserved for billion-dollar corporations, FREE
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Libmesh-devel mailing list
>> Libmesh-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/libmesh-devel
>>
>
>
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
