On Fri, Aug 22, 2014 at 3:19 AM, Benny Malengier <[email protected]> wrote:
> > For long term storage, specific serialize and deserialize methods are > needed. In text format for very long term (over OS and arch boundaries) > For example, boost serialize in C++ classes ( > http://www.boost.org/doc/libs/1_56_0/libs/serialization/doc/index.html ). > Easy to add in C++ to a class. > For python, working on top of json > https://docs.python.org/2/library/json.html seems like the way to go. > Benny, thanks for the insights. I was thinking more along the lines of standard ways to store meshes, field variables, equations and parameters with standard representations independent of FiPy and more interpolatable with other solvers, viewers etc. -- Daniel Wheeler
_______________________________________________ fipy mailing list [email protected] http://www.ctcms.nist.gov/fipy [ NIST internal ONLY: https://email.nist.gov/mailman/listinfo/fipy ]
