Dear Konstantinos, > I think this could also be one solution in your case. Instead of using > directly the getfem model class, just create your own model description > class [...]
Thank you for your answer. Indeed building a proxy layer on top of getfem::model class would be a solution in my case. This is however less attractive than enhancing getfem::model. First of all all information I need is already in getfem::model, it needs only to be exposed. Secondly I think that getfem::model is quite generic and one could attempt to write export modules to other FEM models or even treet getfem::model as a sort of universal interface (what I am having in mind is Fenics project: http://fenicsproject.org/). I also think that GetFEM should have what you have implemented in your application -- it should be possible to read model description from a text file and build all the components automatically. Of course saving the model should be possible too. Regards, Roman -- Roman Putanowicz, PhD < [email protected] > Institute for Computational Civil Engng (L-5) Dept. of Civil Engng, Cracow Univ. of Technology www.l5.pk.edu.pl, tel. +48 12 628 2569, fax 2034 _______________________________________________ Getfem-users mailing list [email protected] https://mail.gna.org/listinfo/getfem-users
