WaterCAD/ WaterGEMS crashes on large scale MSX models

Hi Attila,

The 2 GB limit of the MSX output files should be resolved as of CONNECT Edition Update 2 (10.02.XX.XX and greater). What version of WaterCAD/WaterGEMS are you currently using? You can check under File > Help > About. 

If you find that you are using an earlier version, please see the following article for assistance on upgrading: Downloading OpenFlows Software

If you find that you are already using Update 2 or Update 3 (the latest is 10.03.00.69), please provide a copy of the model file, steps to reproduce, and the details of the crash: Sharing Hydraulic Model Files on the OpenFlows Forum

Hi Jesse,

I'm on 10.02.03.06, so the 2GB results file shouldn't be the problem. I shared the model in question using the secure upload option. The active scenario is a short 24 hours long simulation with an extremely simplified MSX model (multi-tracing) that results in a crash after the hydraulics are calculated. So it requires just a 'compute current scenario' step to reproduce the issue.

Thanks for your help with the model in advance!

Regards,

Attila

Hi Attila, thanks for sending the model. I can reproduce the crash and will be looking into this. Thank you for your patience.

Hi Attila, I was not able to determine an exact cause or workaround for this issue, so I have reported it to our development team as Defect # 1095997. I have marked at as medium priority for now (typically investigated for the next version) since this model appears to be configured with test data for MSX. 

Is this a "real" model setup or just for experimentation? If you have a model file with the actual MSX values you intend to use, and if you're stuck and unable to progress further with your project, please let us know and provide a copy of those model files so we can escalate the priority of this issue.

Hi Jesse,

Thank you for your support!

Well, I have used this model setup to mitigate any problem regarding MSX's ODE solver. That's why I had a multi-tracing setup for this scenario. I had no problems with multi-tracing before ( except the 2GB limit ). It is a good way to check if the quality of the calculated hydraulics is good enough to not cause any problems, according to my experiences (eg.: extremely short pipes or near-zero flows have caused some problems before).

Although, we have another model setup, of which we are trying to deliver the results. I am going to share that scenario too the same way if it gets you closer to a solution or workaround.

Regards,

Attila

Hi Attila, since we can reproduce in the model previously provided, we should have everything we need to investigate and find a fix. If this issue is hampering your work progress, please let us know. Otherwise, our developers will look into this for a future version.

Hi Attila, since we can reproduce in the model previously provided, we should have everything we need to investigate and find a fix. If this issue is hampering your work progress, please let us know. Otherwise, our developers will look into this for a future version.

Hi!

We have a project to deliver in the beginning of the summer, so it definitely hampering our work and progress. I would really appreciate it if you could elevate the priority of this issue, because we need the results of this model to deliver.

Best regards,

Atitla Bibok

Hi Attila,

In order to ensure that the problem is not related to the unusual MSX setup (I see the same issue in this model in an older version 10.02.03.06 which the model was last saved in), please provide a copy of the other model you mentioned was set up to "deliver the results". Sharing Hydraulic Model Files on the OpenFlows Forum