I/O of `ufl` forms
- Dominant language
- Python
- Stars
- 150
- Forks
- 79
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 10
Description
It would be great if the I/O of forms was introduced as part of newfl.
In the context of my work in reduced order modelling, in the former implementation in `RBniCS` I had several routines that took a `ufl` form, processed it in some way, and gave back another `ufl` form as output. The preprocessing is so complex that for problems of moderate mesh size it takes more CPU time than the assembly of the resulting vectors/matrices themselves.
I have not reimplemented yet this feature in `RBniCSx`.
The implementation of I/O is surely somewhat complicated, in the sense that you wouldn't want to save for instance the mesh itself, but only the expressions and the integrals. This is why, for instance, simply pickling the form doesn't work. Furthermore, also simply storing the `__repr__` of the form does not work either, since a string like `Mesh #1` will typically appear in the `__repr__` of a form , and when loading the form there is no guarantee that your actual mesh is still the first one.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.