How to record detailed well data without storing all states?

[Kunqing-Jiang]

Hi,

Currently, I can only access well outputs at report steps. Ideally, I would like more detailed well results, for example by logging them at each solver step. Since storing the full reservoir state at each solver step would use up too much disk space, I was thinking of only keeping sparse reservoir data and detailed well data.

Is there any way to achieve this, perhaps with something like a probe or observer for wells? Alternatively, do you have any suggestions on how I could implement this myself?

Thanks!

[Kunqing-Jiang]

Just a quick follow-up: I added a small hook to simulate in Jutul so that I can pass the well and variable symbols I want to log through simulate_reservoir in JutulDarcy. This allows me to record well results in a CSV file at each mini_step, and it works quite well in practice.

That said, I realise that modifying Jutul directly may not be the cleanest approach.

[moyner]

I think this is on the todo-list. You can set output_substates = true, but this will also include all the dense data. So your temporary solution is the way to go (you can use post_ministep_hook to call a function after each step without modifying the code)

[Kunqing-Jiang]

Thanks for the reply! The post_ministep_hook approach is indeed more elegant and fits my problem much better.