-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error using soil layer number as constraint to modify soil parameters #32
Comments
Hi sorry for that. For fixing the issue #30 I had to strongly restructure the SWAT2012 input file handling to consider some exceptions in input file structures that I was not aware of. In the restructuring I might have eliminated the layer option. I will try to reintroduce it in the new input file handling. |
Thank you, @chrisschuerz! |
@jsacerot I reintroduced the parameter constrain 'layer' in the new version 0.3.5. If you want to test it please update your |
Hi @chrisschuerz. Now I am getting this error: Error:
Any thoughts about what could be the problem? My code was running before. Thank you! |
@chrisschuerz I performed some tests and discovered that the problem now is with parameters in files *.sub:
|
@jsacerot thanks for looking into it with such detail. It made the search much easier. There was an issue with sub files with different lengths (which is often the case). Version 0.3.5.1 should fix this issue, at least in my tests. Please again update |
@chrisschuerz Thank you so much. The issue seems to be fixed, and everything is running without problem. |
Hi @chrisschuerz . I do not know what happened but after the release of the latest version of SWATplusR, an error is returned when using soil layer number as a constraint to modify soil parameters:
Parameters to modify:
par_mod <- c("SOL_AWC.sol|change = relchg|layer = 1", "SOL_K.sol|change = relchg|layer = 1")
Error:
Error in translate_parameter_constraints(par_names, swat_vers) :
The parameter constraints: layer are not valid!
Could you please help us to solve this issue?
Thank you!
The text was updated successfully, but these errors were encountered: