Eirik Keilegavlen

I think you need to store data on which CellBlock `'gmsh:physical'` belongs to; right now I think there is a (tacit) assumption that length of `'gmsh:physical'` equals the number of...

I don't know if the best is to move 'gmsh:physical' to `Mesh.cell_sets`?

I agree, but would it not break the idea that cell_data are numpy arrays with one item per cell?

As long as it does not violate the assumptions in read/write functions, I think `None` is a good option.

This will partly be taken care of by #613. To complete the task, methods relating to index operations should be moved to a separate module (pp/utils/index_operations.py?), and be merged there...

My idea here has been what you sketch out in the last line: Force an operator to have all its components evaluated at the previous iteration (but not those already...

This will be implemented while revisiting the models.

I will try to help out. See my comments in #477, though: We can afford some pragmatism in how aggresive we are in rooting out the old terminology.

This should to a large degree have been solved in #673, but we'll keep it open for a while as a reminder.

Thank you for the kind words and encoragement! We'll try to fix the pymetis import. pymetis is not really needed for anything, but if available, it is very useful at...