From 411682c46695291789bd284ddc8b0b4039f68dff Mon Sep 17 00:00:00 2001 From: Joakim Hove Date: Tue, 25 Jan 2022 07:48:56 +0100 Subject: [PATCH] Slightly rewritten paragraph about ACTIONX <-> simulator interaction --- docs/tm/udq_actionx/actionx.tex | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/tm/udq_actionx/actionx.tex b/docs/tm/udq_actionx/actionx.tex index a4bb40a36..a85bd2334 100644 --- a/docs/tm/udq_actionx/actionx.tex +++ b/docs/tm/udq_actionx/actionx.tex @@ -348,9 +348,11 @@ group configuration only take place at report steps, and in between those the simulator ``owns'' the well and group data. Unfortunately this is no longer the case when \actionx{} is active, and depending on the keywords in the \actionx{} block we need to update the simulator data structures after \actionx{} has been -evaluated to true. This complex, and most of the bugs in the \actionx{} -implementation have been in this interface. There are probably more bugs waiting -here. +evaluated to true. This is complex, and most of the bugs in the \actionx{} +implementation have been in this interface. Some details of what is currently +updated is decsribed in sections \ref{actionx_change_well} - +\ref{actionx_welpi}. This update mechanism will probably need to be continously +updated in the future. The simulator code makes \emph{copies} of many of the objects like wells and connections from the \inlinecode{Schedule} class, and also assembles many