Sounds good - here is my proposed plan - New ExodusII library -> COMMITED - Exodus/Nemesis patches to write 0 IDs instead of std::numeric_limits<T>::max() for certain operations - Configurable subdomainID size patch (defaults to 2 bytes)
Vacation time - NetCDF patch Cody On Jul 12, 2011, at 12:04 AM, Roy Stogner wrote: > > > On Mon, 11 Jul 2011, Cody Permann wrote: > >> This update looks good from my perspective, however maybe we need to >> update netCDF too? Opinions? > > My vote would be to update netCDF as long as we're at it, but if > you've got things working without such an update there's no reason to > bundle everything into a single commit; start with exodus-alone. > >> I'm happy to commit my changes but I'd like to hear back from the >> developers before doing so. > > I'd say go ahead and commit so everyone else can start testing too. > > Besides, the svn head is already in a state of shame at the moment. > My new NodeConstraints feature goes into an infinite loop with > ParallelMesh, so there's four "--enable-everything --enable-parmesh" > regression test failures that I'm still trying to correct. Even after > that, we aren't planning a new official release soon. That nasty > PetscVector::localize() issue ought to get a real fix instead of just > a workaround first. > --- > Roy ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
