On Wed, Jan 20, 2016 at 4:33 PM, John Peterson <jwpeter...@gmail.com> wrote:
> > > On Wed, Jan 20, 2016 at 4:29 PM, Junchao Zhang <junchao.zh...@gmail.com> > wrote: > >> I guess that is because the input mesh is read from a file in >> adaptivity_ex2, >> however the input file does not boundary info. >> > > That's correct, there are no boundary ids in mesh.xda. > > > >> I am trying to add this to the input file. It looks the format of .xda >> files is not well documented. >> > > Check out, e.g. reference_elements/3D/one_hex.xda, the boundary conditions > are at the end of the xda file, and I think they are (elem,side,id) > triplets. > > 6 # number of boundary conditions > 0 0 1 > 0 1 2 > 0 2 3 > 0 3 4 > 0 4 5 > 0 5 6 > Oh yeah, also there's a LaTeX document here doc/latex/xda_format/xda_format.tex describing the format. -- John ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
