Store element connectivity as "Mixed" format to Xdmf file. It's a long
list where first number is element code and then there is connectivity
data (starting from 0). Xdmf format does not support several
Topology-elements in Xml file format, so before it was not possible to
store e.g. both Tri3 and Quad4 elements in same problem. After this
commit this should now be possible. Paraview Xdmf3 reader is needed to
use.
* refactored code for solvers.
* Added elementary tests for least-squares fitting of strain and stress fields
* A more realistic postprocess + Xdmf writing test
* removed debug keyword argument from test
* Rewrite update_xdmf!
New function to update Xdmf file no longer takes Solver object but
xdmf, problem, time and fields to write, for example
julia> update_xdmf!(xdmf, problem, 0.0, ["displacement", "temperature"])
All problems are written separately and put together into one
SpatialCollection, allowing to have more structured Xdmf and making
it easier to write complicated field configurations. Support for Xdmf
API 3.0 added.
* Support for Tensor6 field writing
* moved update_xdmf! to io.jl
* Removed some empty files
* Not use old Postprocessor, obsolete code.
* Not use old XDMF (obsolete code). Fixed test.
* removed some postprocessing to pass test, maybe we should drop abaqus.jl from code as obsolete
* add function get_temporal_collection back, it's used by update_xdmf of modal solver
* postprocess of boundary problems also
* added test for contact pressure. dl+quad test output was written in wrong file, fixed.
* postprocess for contact pressure
* contact pressure postprocess
* with boundary problems always store also the primary unknown field
* Change "reaction force" -> "lambda"
* testing postprocess of reaction force also
* sign convention
Jukka Aho