Thanks Roy, I'm just trying to cut out unnecessary parts of my Code. My main problem is the memory with my 3-D elasticity + fracture problem. ParallelMesh helps quite a bit but I would like to make the memory footprint even smaller and hopefully make things run a bit faster in the process. I would appreciate any suggestions.
Best, Ata On Sun, Nov 17, 2013 at 9:14 PM, Roy Stogner <[email protected]>wrote: > > On Sun, 17 Nov 2013, Ataollah Mesgarnejad wrote: > > I have a very simple question: When is it necessary to call >> constrain_element_matrix & constrain_element_vector? Do I need to call >> them >> even if I'm not doing any adaptive refinement but using the Dirichlet BCs >> API? >> > > With Dirichlet constraints the situation is even more (painful pun > unavoidable) constraining. Not only do you need to > constrain_element_matrix and/or vector for setting up a homogeneous > solve (such as would occur if you were solving for (u_new-u_old) and > u_old already satisfied your constraints), you need to call > heterogeneously_constrain_element_matrix_and_vector if you ever need a > non-homogeneous solve (such as would occur if you were solving > directly for u_new). > --- > Roy > -- A. Mesgarnejad PhD Student, Research Assistant Mechanical Engineering Department Louisiana State University 2203 Patrick F. Taylor Hall Baton Rouge, La 70803 ------------------------------------------------------------------------------ DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
