Dear Bentley Team,
I have model three scenarios rapid valve closure, Valve Closure and Slow Valve Closure and developed three different Transient Closure Pattern. When I am computing with batch scenarios of all three. All my results are same, when I compute scenario separately then results different from each other which make sense. I think I am doing mistake in Alternatives (Initial Settings) because it is computing with that pattern of valve which is selected in last. I have attached picture of batch run.
Thanks & Regards,
Syed
Hello Scott,
Yes I have found my mistake and rectified, Now I am getting combined graph of all the scenarios.
Thanks a lot .
Regards,
SA
Hello Syed,
All three scenarios have the same transient alternative. This means that all use the same operating rule for the valve. If you look at the TCV properties in each of the scenarios, they are all set to "Rapid Closure."
You will need to make a transient alternative for each of the scenarios and assign these to the scenario. You can then make each scenario active in turn and assign the correct operating rule. After recomputing, there should then be a difference in the results.
Scott
I have compared two scenarios by running "Scenario Comparison Tool". It highlights Initial Setting Valve Closure and Valve Closure - Slow and when I generate report no difference is found there. I have also uploaded model file,
I would recommend running the scenario comparison tool, which can identify differences in the scenarios in your model. The transient alternative will be the place that stores the different valve closure patterns.
If that doesn't help, I would review the user notifications for the transient run to make sure there is no issue that might be impacting the results. If that doesn't help either, we may need to see a copy of the model files.