Good Morning, I used the examples and have figured out some of the coding. I was hoping there was a primer explaining each of the entries for the version.
Thank you. Brandon On Fri, Feb 1, 2019, 11:38 AM John Peterson <jwpeter...@gmail.com wrote: > > > On Fri, Feb 1, 2019 at 9:10 AM Stogner, Roy H <royst...@ices.utexas.edu> > wrote: > >> >> On Fri, 1 Feb 2019, Brandon Denton wrote: >> >> > I'm currently working through a mesh converter from FEMAP to .xda. Is >> there >> > a primer for the .xda file format? >> >> I'm afraid it's even worse than "no primer"; the XDA format changes >> without notice. We never really conceived of it as a stable >> "standard", just something that could let our users save files without >> trashing data (p refinement levels, exotic FE types, whatever) that >> might not be supported in pre-existing standards. We add new data >> every couple years: nodeset/BC/subdomain names and element unique_id >> values in 0.9.2, node unique_id values in 0.9.6, edge and shellface >> BCs in 1.1.0, more complicated field width encoding in 0.9.2 and again >> in 1.3.0... and we don't even bother adding write options for old >> formats, just backwards compatible reads via version string. >> >> Honestly the easiest way to write a mesh converter would probably be >> to write a libMesh MeshInput subclass and use our meshtool app. If >> you need something standalone, I'm sorry but the only authoritative >> source on the format is src/mesh/xdr_io.C >> > > Of the xda files that are checked in to the repository: > > examples/adaptivity/adaptivity_ex2/mesh.xda > examples/adaptivity/adaptivity_ex3/lshaped.xda > examples/adaptivity/adaptivity_ex3/lshaped3D.xda > examples/subdomains/subdomains_ex3/hybrid_3d.xda > examples/adjoints/adjoints_ex3/H_channel_quads.xda > examples/adjoints/adjoints_ex4/lshaped.xda > examples/adjoints/adjoints_ex1/lshaped.xda > examples/miscellaneous/miscellaneous_ex5/lshaped3D.xda > > One that was generated relatively recently is: > > examples/adaptivity/adaptivity_ex3/lshaped.xda > > so you could probably use that to reverse-engineer most of the current > file format. > > Also, I assume you are only interested in reading mesh data (nodes, > elements, connectivity, etc.)? Solution data uses a different file and > format from mesh data. > > -- > John > _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
