Hi,
I'm setting up Multi Species Analysis (MSX) runs for Water Quality modelling however I noticed that regardless of the 'Tank Mixing Model' I specify the MSX run is simulating the tank as if it was 'Completely Mixed'.
Is there another method to change this for MSX runs?
Thank you,
Ryan
Hello Ryan,
Can you share your MSX model with us? See the link below for sharing hydraulic models over the forum;
Sharing Hydraulic Model Files on the OpenFlows | Hydraulics & Hydrology Forum
Let me know when you upload the model files.
Regards,
Yashodhan Joshi
I don't see why you need a model to answer a question about the functionality of the software but sure... here's a copy of one I built earlierTank Mixing Test model.wtgpkg.zip
Ryan, we are currently looking into this. We believe that other mixing models should be supported in WaterCAD and WaterGEMS (even if the MSX extension itself does not) and there may be something preventing it from working correctly. While we assess this, please let us know if this is preventing you from continuing your work or if Completely Mixed is OK for you to use in the meantime.
Jesse DringoliTechnical Support Manager, OpenFlowsBentley Communities Site AdministratorBentley Systems, Inc.
Thanks Jesse,
Unfortunately it is impeding our progress, we're in a three month sprint so the timeframe is tight. We have a large number of reservoirs with single inlet/outlets where LIFO would be the most appropriate simulation. And as I'm sure you're aware the difference between LIFO and completely mixed can be very different.
It also affects our scope, if it's possible to choose the mixing model I need to organise workshops with someone experienced in CFD modelling to determine the best option to simulate reservoirs with less usual configurations (for example inlet/outlet at 90 degrees to each other). However if it's not possible I proceed with completely mixed and add the caveat that the results coming from reservoirs that should be LIFO or two-compartment could be notably inaccurate.
Hi Ryan,
Thanks for the explanation. Our developers are investigating this (Defect #897360) and we shall get back to you with an update.