Benoit Bovy

A intermediate option between the current, fixed workflow and the flexible workflow defined above would be to keep fixed ``initialize`` and ``finalize`` stages and, instead of two ``run_step`` and ``finalize_step``...

Note that the suggestions in the comments above are still very elusive. I'm not sure at all if it is a good idea. At least it deserves carefull thinking to...

Thanks for the suggestion @Chilipp ! I haven't really looked into existing solutions for automating cmd line interface yet but I'll look into your package.

Could you provide a concrete example where such *quasi-cyclic* situation happens? I wonder if you could refactor your problem into 3 processes `A`, `B`, `C`, or if user-defined process ordering...

Would it be an option to declare `C.leaf_dry_matter` with `intent='inout'` and with some default value (i.e., some placeholder for the value at t = -1)? This way you could avoid...

> Ok, a fat apology No worries at all! > Thank you for your outstanding support! You're welcome!

Thanks for sharing your notebooks, it gives a clear overview of the problem. I admit that the 'inout' variable with a default value workaround is not ideal in the case...

> I don't understand why it would break it because you have it already (global/group + 'inout'). I think such a change would just bring this option to the surface...

> Nevertheless - I regard this as settled and remain quite now and hope you keep up your excellent work! :) Thanks! Please continue to give helpful feedback, it's very...

> However, with multiple different processes that need to be updated (e.g. have this cyclic behaviour), this greatly increases the number of processes, just to implement updating a variable. I...