Torben Schiz

The error probably occurs because "k_11" is set and returned in the `initialize`-method in nutils `micro.py` or dumux `micro.cpp`, respectively, leading to a mismatch as it is not expected to...

The relevance of the corner case should not be underestimated as keeping the interpolation local could lead to many said cases in a parallel execution.

We discussed using inverse distance weighting and implemented it in #85 but so far it is done based on spatial distances. I also thought about this and for the snapshot...

In the following a few ideas for the configuration, sticking with the "json"-configuration and not adding another configuration file for the input parameters for now. It could make sense to...

A complete configuration file for the snapshot parameter configuration could be ```json { "micro_file_name": "full_order_model", "snapshot_params": { "read_data_names": {"strain": "vector"}, "write_data_names": {"stress": "vector", "stiffness": "vector"} }, "snapshot_data": { "macro_data": "strain",...

My understanding from an in-person discussion is that, for the moment, the JSON configuration file should only provide an hdf5-file name and location telling the snapshot tool where to read...

How could it be decided what simulation is similar enough? Especially in the case of adaptivity, as I understand it, simulations that are similar to each other rely on one...