Replies: 2 comments 3 replies
|
Hi @ifariasg , thanks for starting up this discussion, and for posting the script along with the findings. It's very helpful for us to further improve the code. We (the development team, @Manangka) will definitely have a closer look at this. But since the Groundwater Modeling and More conference in Princeton is coming up, it might take a few weeks until you'll hear from us :-). Just two things for now. You mention that for more advective problems, the results are quite good. Can you share what type of problems you have looked at? And about the performance results, A quick look in the listing file tells me that there are convergence issues with the transport model. I didn't have time to go into it any further, but I think it will distort the run time performance numbers significantly. I guess we will need to straighten that out first. |
|
Hi @ifariasg. Thank you for sharing your model and great to hear that for some of your problems the new utvd scheme shows improved results. The first thing i noticed is that with the notebook the SEAWAT and MODFLOW takes about the same amount of time (around 2s on my machine). I haven't dived into the reason why there is a difference in runtime between your script and my notebook The second thing is that I indeed see that there is a difference between the SEAWAT concentration and that of MODFLOW. The SEAWAT model has less numerical dispersion. A good way to see this is by plotting the contour lines of the concentration. The width between them says something about the spread. The reason why MODFLOW displays more numerical dispersion is due to the internal limiter we use under the hood. By default this is fixed to use the van Leer flux limiter. This limiter is known for its stability but is also more diffusive than some of the other limiter. When I switch to a more compressive limiter, like the Superbee limiter, the results of SEAWAT and MODFLOW are comparable. Unfortunately this setting is not something you can set through an option though but it is hardcoded. And the frames at the last time step |





Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Together with @dzamrsky we have been investigating how MF6+BUY results compare to SEAWAT due to a general idea that MF6 (GWT specifically) tends to show more numerical dispersion. Since UTVD was added to MF6 v6.7.0 we thought this was acknowledged and improved so we started migrating some existing models to MF6 to compare.
For more advective problems results seem to be quite good, but when looking at more density-driven problems we noticed discrepancies. For example, we tested a simplified version of the rotating interface problem.
We found that when dispersion parameters are set to 0, there area noticeable differences in concentration results, with MF6 showing consistently more numerical (?) dispersion. No matter what setup I used I couldn't improve the results. Some of the things I tried:
What's also worrying, the MF6 version was ~10 times slower to run, no matter the settings.
At this stage I can only think of two possibilities, there is an option I didn't implement that makes both models essentially different, or there is something strange going on internally. To spark some discussion, I'm sharing the script used to see if anybody has an idea on what could be causing this. Also it would be interesting to know if anybody has been experiencing similar problems.
benchmark_seawat_vs_mf6.py
This is the comparison with no dispersion

...and strangely enough, with dispersion the results look a lot more alike...

All reactions