If it’s possible in your project, I would recommend you use our latest model, SWAT+. This is the model we are currently working with and supporting. I believe you will find our new model with updated interfaces and new options (not included in SWAT) to be improved and easier to use. I have included a link to SWAT+ below for your review.
If the data is the same for both of your debug and release simulations, these discrepancies you are seeing likely due to the property settings used to create the executables at that time. SWAT is an older model and our team has learned more information on the settings we used in these compiles.
Let me know if you have any questions or concerns.
Nancy
https://swat.tamu.edu/software/plus/
From: arc...@googlegroups.com <arc...@googlegroups.com>
On Behalf Of bakery sweetie
Sent: Friday, January 30, 2026 6:32 AM
To: ArcSWAT <arc...@googlegroups.com>
Subject: [ArcSWAT:13994] Discrepancies of output between 64-bit debug and 64-bit release
|
You don't often get email from fanmeng...@gmail.com. Learn why this is important |
I have successfully built a SWAT project. But when I run it, I found discrepancies of output between 64-bit debug and 64-bit release. For example, when I choose 64-bit debug, the value of ET is smaller than 64-bit release. What is the reason of the discrepancy? Which version should I choose for calibration and validation?
--
You received this message because you are subscribed to the Google Groups "ArcSWAT" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
arcswat+u...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/arcswat/33610c55-9648-46c7-bb75-25d098d2ae54n%40googlegroups.com.