ETP calibration in specific subbasin

[Gerardo Castellanos]

Hi everyone,

I am trying to calibrate ETP for an unique subbasin, I don't know if thats possible. My problem is that I don't know how to define that specific object when I am adding the observations file. For example, the level in this case is "basin"? When I try to define basin level and "basin number=12" the program just crashes.

Another idea that I have is to select "LSU" level, but as you know, normally we have more than one LSU in a subbasin, so my question is... Is possible to define multiple objects?

If anyone has any idea how I can do this, if possible, I would greatly appreciate the help.

[SWAT+ Toolbox]

What are you trying to calibrate?

Why is basin number 12? Do you mean sub-basin? please clarify

[Gerardo Castellanos]

Sorry for the confusion, what I want to calibrate is a specific sub-basin (number 12), I meant that when the “specific object” is to be selected the available options are HRU, LSU or Basin. I understand that “Basin” refers to the whole basin, not to a specific sub-basin, so if I indicate Basin = 12 (this is not supposed to be correct because we only have 1 basin) the program closes.

[Celray James]

Easiest way to do it is to know which LSUs are in the sub-basin you want from QSWAT+ and select those on the map within SWAT+ Toolbox. SWAT+ Toolbox will find the HRUs for those LSUs. What parameters do you want to add? some parameters cannot be added to Sub-Basin/LSU/HRU objects for example ch_k...

[Saeed Golian]

Good question,

In other words, besides available options, there should be a way to select sub-basins and then the model automatically select all HRUs and aquifer units within that specific sub-basin and calibrate their parameters within that selected sub-basin. 

Regards

Saeed

--
You received this message because you are subscribed to the Google Groups "SWAT+ Toolbox" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sptoolbox+...@googlegroups.com.
To view this discussion, visit https://groups.google.com/d/msgid/sptoolbox/4ebe1ea6-b0be-464a-8517-be12f2f67d1en%40googlegroups.com.

[Celray James]

This is a good idea. I can add this feature in version 2.5 or 2.6, but it will only work if you have the full QSWAT+ Project (not just TxtInOut). Also, there will be a limitation with deep aquifers.

Thanks Saeed.

[Gerardo Castellanos]

So, at the moment of including my ETP observations file, is it possible to assign it to several LSUs at the same time? That is the doubt that arises in my mind. To assign the parameters to specific objects I have it clear, since I can select the objects through the SWAT+Toolbox map. My idea is to use parameters related to evapotranspiration, I think there would be no problem with that.

Thanks for the quick feedback.

[Andreé Hidalgo Ravelo]

I think that's not a good idea, because ETP of your subbasin is the sum of all containing LSU, so your observation data is the result of aggregate all the ETP of LSU inside the subbasin. 

You probably should create a single swat+ model only if this subbasin, and so could be possible to use your observation data to calibrate it. 

Regards. 

--

You received this message because you are subscribed to the Google Groups "SWAT+ Toolbox" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sptoolbox+...@googlegroups.com.

To view this discussion, visit https://groups.google.com/d/msgid/sptoolbox/62b72d7d-aaba-4804-b0da-ca0a2740770en%40googlegroups.com.

[Andreé Hidalgo Ravelo]

Hello Celray,

When could we expect this release version?

I've tried to type multiple HRUs from a single line, but no separation character (- _ : ,) works. 

My project has thousands of HRUs, it would be complicated and inaccurate to select my study sub-basin using the manual mapping selection tool.

The other options are by range (I would have to enter range by range each time), and by single unit, that's where I'm focusing.

My idea is to enter just one line that contains all my study hrus at once. Something like this:

23_65_134_.... etc etc

But I think that's no any special character that allows that.

Thank you for your support. 

Regards. 

To view this discussion, visit https://groups.google.com/d/msgid/sptoolbox/76c5c8a1-8e59-4851-8085-b162c2e3e9bcn%40googlegroups.com.

[Celray James]

Hi.

Right now, there is a pre-release version where I can add separators if you want this feature where you enter comma separated values and it adds all objects listed. I have been contemplating on the sub-basin idea, but SWAT+ does not really work with subbasins (except for demarcating shallow aquifers - as far as i know). Thus for map, it would make sense to stick with LSU selection.

Let me know so I can add it and send you the pre-release for testing. I will need feedback.

Thanks!

[Saeed Golian]

Hi Celray,

Thanks for your response. Maybe not completely related to this post, but can I ask when any version of SWAT+Toolbox compatible with gwflow will be released? Any plan to do so in near future?

Thanks in advance,

Kind regards 

Saeed

To view this discussion, visit https://groups.google.com/d/msgid/sptoolbox/989df8c0-3b8e-4c0e-b444-d5af5740962bn%40googlegroups.com.

[Celray James]

SWAT+ Toolbox is already compatible with gwflow. It knows if your project is using gwflow and treats it as such. the only issue is that the executable is not handling the parameters well based on my tests as I did not find the gwflow parameters to be sensitive. Hopefully this is addressed in the next executable.

[Saeed Golian]

Hi Celray,

Many thanks for your response. So it my be the question for many other users using gwflow, can I ask when a robust version of SWAT+Toolbox with full compatibility with gwflow (in terms of sensitivity analysis and model calibration) will be released?

Thank you again for all you've done/ are doing on Toolbox development.

Kind regards

Saeed

To view this discussion, visit https://groups.google.com/d/msgid/sptoolbox/889ab61c-9e3f-434c-a925-a86d3a169805n%40googlegroups.com.

[Celray James]

SWAT+ with gwflow is already compatible with SWAT+ Toolbox for Sensitivity analysis and Calibration except SWAT Check, the current issue lies in the SWAT executable [where parameters are not sensitive], not SWAT+ Toolbox. If your project is not detected as gwflow, I can help with that.

[Andreé Hidalgo Ravelo]

Hello James, when could we expect this new pre-release with this special feature (separators to add multiple HRUs at once in the parameters tab)?

Please let me know when it will be available for testing.

Best regards!

To view this discussion, visit https://groups.google.com/d/msgid/sptoolbox/989df8c0-3b8e-4c0e-b444-d5af5740962bn%40googlegroups.com.

[Saeed Golian]

Thanks Celray James and others, I hope the new version is also fully compatible with gwflow module.

All the best,

Saeed

To view this discussion, visit https://groups.google.com/d/msgid/sptoolbox/CAKvcvLGc4b%3DipiFSYj189hmTvYNJNAgxhhgWeF%3DpqDN9X2e%2BgA%40mail.gmail.com.

[Andreé Hidalgo Ravelo]

Hello Celray, I've seen the official 3.0 version was released... Is it now possible to add these special separators we talked about to add multiple HRUs at once in this version of Toolbox? In this case, what would be the procedure to follow?

Thank you in advance! 

[Celray James]

Sorry I had forgotten, I just issued a patch for that... check for updates and let me know if it works the way you expected.

[Marcus Galbetti]

Dear all,

I am calibrating the parameters of these LSUs.

3060, 2970, 2820, 2860, 2870, 2800, 2900, 2810, 1960, 2360, 2320, 2730, 1820, 2770, 1920, 2460, 2000, 1790, 1800, 1810, 2600, 2010, 1860, 1850, 1970, 1880, 1890, 2640, 1910, 2080, 2680, 2660, 2690, 2570, 2670, 1830, 2610

However, when I select a parameter to calibrate and input the LSU list, SWAT+ crashes. 

Is there a maximum number of LSUs for calibrating process?

Is there a file where I can write down the parameters and LSU for calibration?  

Any ideas on how to solve this?  

Thanks

Marcus

[Celray James]

SWAT+ does not use LSUs directly, it uses HRUs.

If you select on the map in SPT, it goes and finds the HRUs in those LSUs, but if you want to manually add using the input fields, you need to add HRUs not LSUs. to add HRUs, you can add one by one, range or a comma separated list but make sure to select the correct option.

C. James CHAWANDA

[Andreé Hidalgo Ravelo]

Hello Celray! I have news about testing your new Object List function to add elements in parameters tab.

Well, I've created an algorithm to track tributaries of determined river (Channel ID), after, their associated subbasins of all these rivers, and finally, the hrus within each subbasin in the watershed "of influence" of this chosen river. It works very well, and it's the script is very short. In short words, just putting the channel id number, it's possible to obtain all the associated hrus until their headwaters, directly in a txt to copy paste to Object List function. Don't you think it would be an interesting feature to add to the code? I suppose that you can create a more efficiency algorithm than mine, but I can share with you if you like.

The only handicap that I realize it's that is not correct to add elements of hru type to calibrate parameters that don't belong to HRU parameter group.... I mean, there should be a conflict if I apply this Object List to calibrate the Alfa or Flo_min, because they are Aquifer parameters, and the same to deal with Basin or others. Maybe in the Soil group could work.

I mean that depending of nature of the parameter, it should be allowed to add by Object List a different type of element... for instance, the aquifer code for Alfa calibration, or being disabled when you select a Basin parameter, to be consistent with the model.

The modification of the algorithm to track Aquifers "of influence" wouldn't be hard.

What do you think about that?

Regards! 

To view this discussion, visit https://groups.google.com/d/msgid/sptoolbox/58c98089-d30d-4578-985f-3755a7f38088n%40googlegroups.com.

[Andreé Hidalgo Ravelo]

By the way, I'd like to ask you:

If I apply some parameter values, let's say "general" parameter values that affect the whole basin, and in the same run, also a group of "zonal" parameter values applied only to specified HRUs (added by Object List function)... I suppose that Zonal ones have a higher "hierarchy" in their zones of influence where are overlapped in values with the General ones, and they (zonal ones) would prevail.

Am I right? Or there would be a conflict in this simulation?

Thanks for your support! 

[Celray James]

This is actually a very interesting idea which would make life easy for most people. I think to resolve the issue of the Aquifers... one would only enter the channel and this would automatically select all associated LSUs on the LSU map and associated aquifers on the aquifer map... and then the user can confirm to add the selection or not, first for HRU parameters, and then for Aquifer Parameters (and in the future - for Channel parameters on the channel map). The only drawback is that it would not work with independent TxtInOut (those without QSWAT+ structure - but this is not common, so I would say it is a viable option).

I will definitely be implementing this feature and I think you will love the way I will implement it. If you feel like sharing the code you wrote, feel free to provide a starting point but I already have ideas of tracking connections through the connect files.

What are your thoughts on this.

C. James

[Celray James]

Concerning the basin-wide parameters, there is no easy way out for that. the only way is to split your model set-up into smaller and route them using point-source feature. That way you can have zoned basin-wide parameters based on each chunk.

C. James