PV update using PNet

[hanseongji]

Hi Hyeonbeen,

Thank you for providing the great material on automating RD using Python.
I'm currently trying to move from C# ProcessNet to Python, and have a question regarding the necessity of the "model_document.UpdateDatabaseWindow()" method when the PV is changed.

In my experience, simply using the command "PV.Value = PVvalue" did not update the PV in the model.
In the RD GUI, when we implement a model, we press the "OK" or "Apply" button in the Parametric Value Tab after modifying some values.
This triggers an internal model update (redraw) process.

However, it appears that the update process is not explicitly performed when using ProcessNet.
When I was using PNet in C#, I preferred to use the model document updating or model redraw functions because of the reason.
I often encountered a similar behavior when following the code you provided (RunDOE_GUI).
It would be greatly appreciated if you could share your experience regarding this matter.

[leehyeonbeen]

Hi, thank you for pointing out the potential issue.

Update

In my environment (RecurDyn V9R5 and 2023), just passing PV.Value=value worked fine.
However, as you have pointed out, this method doesn't seem to seamlessly communicate with the RecurDyn GUI.
I have updated the function modeling.ChangePVvalue to complement the pointed deficiency.

Existing issue

However, this also does not explicitly change PV value in the RecurDyn GUI. As I know, calling model_document.UpdateDatabaseWindow() demands high computational load if the model is large. Therefore if the function ChangePVvalue does not work as expected, it is considerable to additionally call model_document.UpdateDatabaseWindow(). Since the expected behaviors can differ by RecurDyn versions and OS, it will be ultimately the user's choice.