Wouter J. de Bruin
Wouter J. de Bruin
A potential solution in this direction is printing the group id. That would give you insight in which connections belong to eachother.
✔️ kmeans clustering has now been added https://github.com/equinor/semeio/pull/286 🚫 currently still blocked by https://github.com/equinor/ert/pull/1316
✔️ kmeans clustering has now been added https://github.com/equinor/semeio/pull/286 ✔️ speed improvement for many observations https://github.com/equinor/ert/pull/1316
🚫 Currently blocked by the new commits not yet being in pypi.
Both packages are now updated on pypi (2.21.b0 and 1.0.b0) ✔️ Ready for testing.
Great.... It must be the weather.
It's still pyscal that takes by far the most time when individual relative permeability tuning is done. 
https://github.com/equinor/pyscal/blob/0e5aaf0df49b47d229febeb41f778b817bf220ee/pyscal/utils.py#L21 ~45 seconds spend there.
There is also quite some memory usage. I see values of up to 130G used in my VM when 125 `flownet_render_realization` processes are running simultaneously.
Can you explain how to recreate this?