Paraview Plot classes similar to Sensor class

[srosenbu]

Currently, plotting is left to the developer of the Material Problems, whereas, for Sensors, the user can decide which fields they want to save. Most of paraview plots have a very similar structure (either direct storage of some component of problem.fields or projection of sth, in problem.q_fields), therefore i would suggest to introduce sth. like

class Plot(ABC):
    @abstractmethod
    def write(self):
        pass

class DisplacementPlot(Plot):
    def __init__(self, name):
        ....

    def write(self, problem):
        with df.io.XDMFFile(problem.experiment.mesh.comm, problem.pv_file, "a"):
             ....

[eriktamsen]

I am not sure how you would use this.
I would rather suggest to directly combine sensors and paraview output.
A "DisplacementPlot" is nothing then a "full field displacement sensor".
Basically only write to paraview, what has been captured by a sensor.
This would also make adopting VMAP later on simple, as this is the idea there. Longterm, we want to use VMAP as the output format and then generate paraview outputs based on that.

[srosenbu]

Do you mean that a sensor should get a method to write the full field to paraview and the normal sensor output is still included? Or do you mean that also the PointSensor output should be somehow written to paraview and the full plot is just a special case of that?