modified values: 0 in 0 files

[Yuestas]

Hello,
I'm running Suif2 calibration. I have 71 parameters that I'm calibrating (they are not 71 different ones but some parameters I'm calibrating at the subbasin level). During the calibration, for some parameters  even though it changes the " value" for each simulation run, it says 0 in 0 files changed for the "modified values".  For other parameters it will say "modified values:  5 in 5 files."  Is there something wrong, if it says modified values: 0 in 0 files  (i.e., perhaps my text file for par_inf.txt does not have the correct syntax)?

Thank you for your time,
Yuestas.

[Karim]

Well send the file to see...

--
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/groups/opt_out.
 
 

[Yuestas]

Thank you very much for the quick reply. I've attached a docx file that has both the screen shot of the problem and the information contained in my par_inf.txt file. Your help is much appreciated.

Y.

[Karim]

Groundwater parameters are not defined at the hru level....
0 file means it found no files matching that condition...

[Yuestas]

Thank you for the clarification.

[zaher tlue]

Hi
I have the same problem that you have. can you tell me how you did fix this problem?

[Yuestas]

Hey Zaher, 

The reason why it happens is because the sub-basin or hru level parameter that you are describing in the parameter text file doesn't exist in the project. Some reasons for this is:

1. your format in your text file may have a mistake

2. the parameter you are trying to change may not exist at the level you are trying to change at (i.e., you can't change a basin wide parameter at an hru level) - to know what level each parameter operates at you can check your swat2009 access database in the "autoinpar" table. The column "type" specifies at what level each parameter operates at:

1 = basin-level parameter 2 = subbasin-level parameter 3 = hru-level parameter 4 = crop-level parameter

3. (what my problem was) If you are trying to change parameters at the hru level, the format asks you to sepcify the parameter, landuse, slope, and  soil "texture" , not soil name. I was using custom soils and had not filled in anything for soil texture since it was optional and was not necessary to run the project in arcswat. What I ended up doing is that I gave each soil a unique arbitrary soil texture so that it can be used to differentiate hrus. You have to do this in your swat2009 access database in the usersoil table.

4. Even after you do all this, you might still get a few files unchanged when changing parameters at the hru  level. This is because these hrus may have been removed as a result of HRU definition that you have done in the arcswat project. 

I hope this helps. If you don't figure it out you can upload your par_inf.txt and I can see if I can spot any mistakes. 

Cheers, 

Yuestas.

Upload your par_inf.txt file here. 

[Mike]

Hi,

I'm having a similar problem.  I'm trying to modify the percent rock in my soil layers, but no files are changing when I run the calibration.  My parinf.txt file is below.  Note that I've purposefully set the MUSLE soil parameters to unreasonable values for testing purposes.  Thanks!

13    : Number of Parameters

    1     : number of simulations

r__CN2.mgt    0.2   0.2

v__ALPHA_BF.gw    1   1

v__ESCO.bsn    0   0

v__EPCO.bsn    1   1

r__SOL_AWC().sol    -0.2   -0.2

v__GWQMN.gw    0.1   0.1

v__USLE_C{6-8,10}.crop.dat    0.2   0.2

v__USLE_C{2}.crop.dat    0.2   0.2

v__USLE_C{5,11,15,16,17}.crop.dat    0.5   0.2

v__USLE_K().sol    0.65   0.65

v__SLSUBBSN.hru    80   80

v__HRU_SLP.hru    0.3   0.3

v__ROCK().sol    5   5

[Karim]

Please use the Form view of the par_inf for correct formulation. There may be mistakes in the Absolute_SWAT_Values file, which you may correct accordingly. 

The formulation is 

V__SOL_ROCK().sol

Best, Karim 

--

[Camila Andrade]

Just in case someone else is having the same problem:

I was following the description on SWATCUP manual to calibrate CN2 (specifying the hru using the soil hydrologic group and the landcover - CN2.mgt__A____FRSE) but I was always getting 0 modified values in 0 files.

Then I decided to use the texture instead of the hydrologic group (writing the texture code after 4 underscores, just as described on swatcup manual - CN2.mgt____LA__FRSE) and it finally worked!

I don't know if swatcup (swat_cup_setup_dec2016_5162) was supposed to recognize the soil hydrologic group code for CN2 calibration, but if it was, it is not working...

Cheers!

[Abbaspour, Karim]

Only two underscore…

CN2__A__FRSE__

 

Karim

--

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.

[Camila Andrade]

Oh, thank you, Karim!

I thought it was necessary to put two extra underscores even if I was not using the texture code.

Thanks a lot!

[Karim]

Actually it is necessary! Sorry, i misunderstood! The reason soil hydrologic group does not change is because it does not appear in the .mgt file, hence CN2 does not depend on it.

 

Karim

[Camila Andrade]

Yes! I tried again and I had to use the underscores. I am sorry, my message was not very clear...

Karim, it's just interesting that the texture doesn't appear in the .mgt either, but swatcup is still able to identify and change CN2 values that refer to the texture soils that I specify using the code "CN2.mgt____LA__FRSE", for example.
Anyway, I was just trying to use the hydrologic group in order to reduce the number of parameters to calibrate. Using the texture gives pretty much the same results!

Thanks again!