> I'm not sure if anyone else already responded to you, but no, I don't > believe we currently write subdomain IDs to xda/r files. One could > either append the subdomain ID to the end of each element connectivity > list, or make a separate section of subdomain IDs somewhere after the > boundary conditions. Either approach would probably require modifying > the output file header to specify either the number of subdomain IDs > present or merely a flag stating that they are/are not available. > > What approach are you currently using? If you are keeping the > subdomain IDs in a separate file that might still be the simplest > course of action for the time being.
The new structure in the XdrIO class actually permits several options, and writing a file where the elements have subdomain ids set *should* do the right thing. Take a look at reference_elements/3D/one_hex.xda in the svn head. The line n/a # subdomain id specification file Says there are no subdomain ids in the current file, and if instead you change it to . # subdomain id specification file Then the ids should be read in the element connectivity section immediately following the element type id. The intent is to admit the following: "mymap.ids" # subdomain id specification file Where the ids will be read from file, but this is not yet implemented. Sorry this is not well documented (yet). -Ben ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
