On Wed, 14 Nov 2007, Derek Gaston wrote:
> Do we need to do some redesign of equation_systems_io ? Right now it
> appears that you can only read xdr/a files for reading equation
> systems.... is this true?
I believe so.
> I see that GMV now has a "copy_nodal_solution" to allow you to copy in
> a solution from a GMV file... but it appears that the equation system
> itself has to be all setup before that happens (ie the variables
> defined and such).
I seem to recall that the GMV input stuff was mostly a hack to support
some old data sets that John didn't have .xdr/a files for. I'm not
too distressed about having to set up an EquationSystems object before
reading in a saved solution, though, since anyone who creates their
own subclasses of System (e.g. anyone using FEMSystem) has to do the
same thing; even people who attach function pointers for assembly have
to do that by hand, although they can do it after the read call.
> I would really like to be able to do an es.read("something.e") and
> just have it work... do you guys think that's feasible?
To a limited extent, yes. You may not be able to continue
timestepping the resulting EquationSystems without more work, but you
should be able to at least read solutions to take norms, differences,
postprocessed values, etc.
> Also... Exodus files have "Element Fields" in them... essentially
> scalar (and vector actually) values that are defined on elements
> (sometimes only a subset of elements). Do you guys have any ideas on
> how we would support that?
Monomial or XYZ elements with p=0? We'll have to finally get around
to implementing turned-off elements with "p=-1" to support values
limited to subdomains, though.
---
Roy
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Libmesh-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
