--
You received this message because you are subscribed to the Google Groups "SWAT-CUP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to swat-cup+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
<RockWellDamWatershed.docx>
The solution to your calibrated problem is the range of the parameters you obtained. You need to keep this range and propagate this range for all of your model uses.
You don’t need to put the parameters in ArcSWAT! Many people ask this and I don’t understand why they think that is what they should have to do!
ArcSWAT is an interface to enable some GIS calculations. SWAT is a Fortran program only concerned with the files in TxtInOut directory. These files are manipulated with SWAT-CUP. So after you build your project, there is really no more need for ArcSWAT for that project.
Also, please note that SWAT is a deterministic model. Meaning, it takes only one set of parameters and gives you one single set of responses. I have written before that deterministic approach is not acceptable for environmental projects and the uncertainty in the model prediction must be quantified. SWAT-CUP allows you to quantify this uncertainty as 95PPU by propagating the uncertainty in the parameters. Again, the parameter ranges are the solution to your calibration problem.
Karim
-------------------------------------------------
Dr. K.C. Abbaspour
Eawag, Swiss Federal Institute for Aquatic Science and Technology
Ueberlandstr. 133, P.O. Box 611, 8600 Duebendorf, Switzerland
email: abba...@eawag.ch
phone: +41 58 856 5359
fax: +41 58 856 5375
http://www.eawag.ch/index_EN
--Dr. James E. Almendinger
St. Croix Watershed Research Station
Science Museum of Minnesota
16910 152nd St N
Marine on St. Croix, MN 55047
tel: 651-433-5953 ext 19
--
You received this message because you are subscribed to the Google Groups "SWAT-CUP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to swat-cup+u...@ googlegroups.com.
For more options, visit https://groups.google.com/d/ optout.
Dear Dr. Abbaspour
Thank you so much!
Your explanations helped me a lot to understand the difference between SWAT and SWATCUP performance, also I read one of your papers which is Estimating Uncertain Flow and Transport Parameters Using a Sequential Uncertainty Fitting Procedure, so now the concepts of 95PPU, SUFI_2, p-factor,... are clear to me.
But a part of your response is somehow confusing to me!! In the last email you said "You need to propagate the parameter ranges by taking for example, 1000 samples or so and get 1000 set of SWAT output values, which serve as the solutions to your problem". My question is that if after calibrating the model, I ended up with USLE_P parameter range between 0.2 to 0.5, should I take 1000 USLE_P between 0.2 to 0.5 and plug them into SWAT and run SWAT 1000 times for each USLE_P, to see for example Sediment Load Range that trap behind dams,... ? On the other hand, after finding Parameters Range, how can I find OUTPUT Range (like sediment load in other part of the Watershed) ?
I really appreciate your help,
Fatemeh
Hello AllI am trying to calibrate a watershed based on Sediment Component (It's already Hydrologically Calibrated!).At the first step, I did sensitivity analysis and ended up with 7 sensitive parameters that have been shown in the attachment. Then for calibrating the model, I ran the SWATCUP several times with different parameters ranges! In all of my simulations, most of Peak Sediment Loads were out of 95ppu band!* I was wondering if any of you have this problem! if yes, could you please tell me how you solved it?!** p- factor is 0.66 (I believe for sediment calibration it can be less than 0.7.), r- factor is 0.93 which is good, I am just worried about NS which is 0.61 (that should be close to 1)! What do you think, do you think this numbers are acceptable for sediment calibration.All required information has been enclosed, if you need further information please let me know.
Thank you so much,
--
--
You received this message because you are subscribed to a topic in the Google Groups "SWAT-CUP" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/swat-cup/0qJBpIzm5cs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to swat-cup+u...@googlegroups.com.
Fatemeh A. Babakhani, Ph.D. Candidate
Graduate Research Assistant, Department of Civil and Environmental Engineering
Wayne State University
Detroit, MI 48202 (313) 844-4902
Hello Everyone,
I hope this email finds you well.
I have set up a SWAT model and conducted calibration using SWAT-CUP. The calibration results are quite satisfactory, as shown below:
Variable p-factor r-factor R2 NS bR2 MSE SSQR PBIAS KGE RSR MNS VOL_FR --- Mean_sim(Mean_obs) StdDev_sim(StdDev_obs)
FLOW_OUT_2 0.85 1.25 0.81 0.79 0.5745 1.1e+001 5.5e+000 -11.0 0.74 0.46 0.61 0.90 5.81(5.24) 5.74(7.29)
Additionally, I manually calibrated the same model. Interestingly, SWAT-CUP suggested different parameter values during calibration, but the results remained consistently good. I have the option to use either calibration approach.
However, I have encountered a challenge regarding satellite data integration. My aim is to compare satellite data (e.g., NASA POWER) with observation data. To achieve this, I input the satellite data into the model that was initially calibrated with observation data and re-ran the model using the same parameter intervals. Initially, the results were promising, but the parameter intervals were quite broad.
To refine the analysis, I narrowed the parameter ranges to align closely with the best values obtained in the initial SWAT-CUP calibration. Unfortunately, the results degraded significantly.
At this point, I have two key questions:
I would greatly appreciate your insights and recommendations on this matter.
Thank you for your time and support.
Best regards,
Sefa Nur