Thank you very much, Lotta. Cheers Syamsul
That is not a error message. HYPE simulated successfully. See for instance the post: https://sourceforge.net/p/hype/discussion/1818967/thread/34111166da/?limit=25#f210 /Lotta
Dear all, I got the following error message after running HYPE: Note: The following floating-point exceptions are signalling: IEEE_UNDERFLOW_FLAG IEEE_DENORMAL STOP 0 Observation data checks will NOT be performed Setup- and model data checks will NOT be performed -> Simulation will halt: successfully Please tell me where did I go wrong. Kind regards Syamsul
Thanks for clarifying this. Can I suggest that you add this information as a single sentence in the wiki to avoid potential confused. Maybe right before you write this sentence: The actual infiltration is calculated by subtracting the macropore flow and surface runoff from the sum of snow melt and rain. you could have a sentence like The water that becomes infoverflow is instantaneously transferred to the local river without any storage and delay.
May I humbly suggest that you add some short additional text to the wiki to avoid potential confusion in the future: http://hype.smhi.net/wiki/doku.php?id=start:hype_model_description:hype_routing#simple_outlet_lake_or_dam_olake Right now, the paragraph reads: gratk, gratp and grata are general parameters that apply to all lakes in the model application. ratcorr is parameter region dependent model parameter for adjusting gratk to different regions. The upstream area (uparea, km^2) is included in...
May I humbly suggest that you add some short additional text to the wiki to avoid potential confusion in the future: http://hype.smhi.net/wiki/doku.php?id=start:hype_model_description:hype_routing#simple_outlet_lake_or_dam_olake Right now, the paragraph reads: gratk, gratp and grata are general parameters that apply to all lakes in the model application. ratcorr is parameter region dependent model parameter for adjusting gratk to different regions. The upstream area (uparea, km^2) is included in...
HYPE version 5.35.0
HYPE version 5.35.0. Main changes: three soillayer evapotranspiration, inital soil water options, lake inflow output, concentrations of flow path output.
Hello, No, there is no storage for overflow due to infiltration capacity limit. It is added to the local river the same time step. The ssrcs parameter is only for determining the saturated surface flow. The saturated surface flow does not have a state of its own, but is calculated from the soil water of the uppermost soil layer. The water that become infoverflow on the other hand will not touch the soil water store, but be transfered directly to the river. /Lotta
Yes.
Good to know, thanks! Just to be clear: The unit of the outflow is always m3/s regardless of whether the user runs HYPE with daily or hourly time steps? Presumably the code then integrates the outflow rate in cubic meter per second up to the model time step length? :)
Hello, The unit of the rating curve equation is meter for lake water level (wlm) and threshold (lake_depth), the outflow is in cubic meter per second, and uparea is in square kilometer. In the introduction to HYPE we suggest that these parameters lie in the range gratk=1-100, gratp=1-2 (then grata=0). http://hype.smhi.net/wiki/doku.php?id=start:hype_tutorials:short_intro /Lotta
Thank you Lotta! I am trying out different ways of calibrating one or more of these parameters. But I am struggling with trying to come up with some reasonable parameter ranges to search within I talked to one of your SMHI colleagues and he provided a parameter set (which I think might come from S-HYPE, but I am not entirely sure about this...): gratk = 0.24 grata = 0.45 gratp = 2 I am wondering about the units of the different elements in the rating curve equation: wlm_lakedepth = meters uparea...
Hello, uparea refers to the upstream area of the outlet lake. It is total catchment area of all subcatchments upstream of the subcatchment that contains the olake. Parameter grata was first introduced to transfer rating parameters of an outlet lake to lakes in upstream areas when the catchment/lake was divided into several subbasins. /Lotta
Hi, I have read the wiki page on simple outlet lakes and dams: http://hype.smhi.net/wiki/doku.php?id=start:hype_model_description:hype_routing#simple_outlet_lake_or_dam_olake The wiki describes several equations for the outflow from olakes depending on the value of grata (let's forget the option for regional correction factors corr here), Here is the equation for grata > 0: outflow = gratk * (uparea^grata ) * (wlm_lakedepth^gratp) For the last equation, it is unclear to me what exactly uparea refers...
Hi, I have read the wiki page on the land routines and I am unsure about how surface runoff is handled when using the default macropore/surface runoff formulation (governed by mactrinf and mactrsm). From the wiki, I understand that: infoverflow (surface runoff to nearest stream) occurs when the thresholds mactrinf and mactrsm are exceeded. Surface runoff can also occur from saturated conditions / upwelling to the surface. My questions are about whether these two runoff contributions are treated the...
My mistake for not checking the performance metrics in more detail — there are some samples where KGE, NSE, and CC are around 0.80, and RE values are less than 0.10
HYPE version 5.34.0. Main change: layered lake model. Other changes: loadcrun work with wetlands, landuse dependent OC processes in soil, changed definition of wprodc parameter, OC in manure, additional indatachecks, improved reading of indata files and error messages. T2 bug fixes.
HYPE version 5.34.0. Main change: layered lake model. Other changes: loadcrun work with wetlands, landuse dependent OC processes in soil, changed definition of wprodc parameter, OC in manure, additional indatachecks, improved reading of indata files and error messages. T2 bug fixes.
HYPE version 5.34.0
Hello everyone, I am currently running HYPE by feeding a series of parameter samples on 20 catchments. The parameters include landuse-dependent such as cevp, srrcs, ttmp and macrate, soil class-dependent such as macrate, mactrinf, mactrsm, mperc1, rrcs1-2, srrate, wcep1-2, wcfc1-2, wcwp1-2, and catchment-wide such as cevpam, cevpph, epotdist, lp and rrcs3. I assume that the soils consist of two layers for all catchments, observed data are at least 30 years in length. The only model option applied...
Hello everyone, I am currently running HYPE by feeding a series of parameter samples on 20 catchments. The parameters include landuse-dependent such as cevp, srrcs, ttmp and macrate, soil class-dependent such as macrate, mactrinf, mactrsm, mperc1, rrcs1-2, srrate, wcep1-2, wcfc1-2, wcwp1-2, and catchment-wide such as cevpam, cevpph, epotdist, lp and rrcs3. I assume that the soils consist of two layers for all catchments, observed data are at least 30 years in length. The only model option applied...
Wetlands in HYPE
Wetlands in HYPE
Wetlands in HYPE
Wetlands in HYPE
Hello Lotta, thanks for your help, that problem is fixed. I'm still working on getting my model running with the water transfer included in MgmtData.txt. This question is probably not specific enough, but I'm still battling the problem that different versions of the executable sometimes work and others don't. Also in one case the executable sometimes works and sometimes doesn't. Do you have any idea how to go about this problem? Lenja
Hello, Some, but not all, tests are described in more detail on the HYPE: Test List page. It is part of the code description by doxygen: https://hype.sourceforge.net/doxy-html/index.html. This specific test points at this sentence on the page for MgmtData.txt: "One row is required for each irrigated subbasin, as well as for each subbasin acting as a regional source. " The subid of the regional source was not found among the subids of irrigation in MgmtData. /Lotta
Hello Lotta, thank you. I'm currently trying to find the mistake. My suspicion is that the model is running empty and there is not enough water left. I get the following code in the MgmtData.txt test: 671 reg source in model domain passed: F - In general I was wondering if there is a page when I can look up the codes? I could not find it myself. Lenja
Hi, tricky problem there. I get that Error message sometimes when I have made something wrong. It is telling you anything about where in the code/input files. Best is to check how far the simulation have got in the log-file. That might give a clue. Or as you did add and remove files to perhaps close in on the problem. I have not seen any errors of irrigation particularly in any specific version, and not in 5.32. Since 5.32 was released a bug in simulation of T2 in very small or shallow lakes has...
Hello Lenja, thank you for bringing my attention to this. The executable was supposed to be version 5.32.0, but I uploaded the wrong file. I have now added the correct executable. The forrtran code, the linux executables and the HYPE_nobutton_da.exe was correct, only the HYPE.exe was an older version than it was supposed to be. Thank you/Lotta
HYPE version 5.32.0 updated
Hi, sorry to bug you again. I just don't see a connection when I get a Fortan run-time error and when I don't. I was trying to set up another model calibration. However I didn't get it running with the 5.31.0 version. Now I got it running with the 5.31.x. So - 5.31.0 works for the model set-up where in only implement irrigation but not DamData.txt - 5.31.x works for the model set-up with irrigation and DamData.txt It seems very strange to me, I have no idea what the difference should be between the...
Hello Lotta, thank you for that comment. I added irrcorp to my CropData.txt, everything else seems to be the same. However, when I run the model with the HYPE version 5.31.x (the newest release) I also get a Fortran error. With the version before, 5.31.0 it works and also the older version 5.19.1 I used seemed to work correctly and did not produce a warning message. Also connected to the other post, is there a problem with the 5.31.x version related to irrigation? Lenja
Hello Lotta, thank you for your help. I'm general a bit confused by the newest HYPE release. I downloaded release_hype_5_32_0 again, but in the executable it always says version 5.31.x. Is that supposed to be like that? Lenja
Hello Lenja, I don't know what went wrong with your calibration run, but fortunately it finished the calibration part and wrote your resulting paraemters before it crashed. After the calibration part the HYPE runs a simulation with the found parameters and write results, e.g. subass.txt. It was this part that didn't finish for you, but stopped during 2002. I recommend checking the File_reference pdf of your HYPE version for the correct configuration of the input files. The wiki almost always only...
Hello, In later HYPE versions (5.26.0-), there is a column needed in CropData.txt that defines which corps are irrigated. It is called irrcrop. From HYPE version 5.25 some of the columns in CropData.txt has changed name. This was done when more growth model alternatives where introduced. Maybe you are using a version that require these changes? /Lotta
Hello, I recently started a model run with HYPE version 5.31.x that included Irrigation (MgmtData.txt and CropData.txt) and Damdata.txt. After around 3 days of runtime I got a Fortran runtime error. However a respar.txt file was created that contained all new parameters, simass1.txt and so on were not created though. I ran my model with these new parameters and got a increase in model performance. But in my hyss.log it only says: Start simulate year: 2002; and not the other years I was also simulating....
Hello, I'm currently implementing irrigation into my model. I added MgmtData.txt, CropData.txt and added the needed parameters into my par.txt and optpar.txt files. My model ran and I thought everything worked, because I got an improvement of my model performance (KGE). However, I realized that I got the following WARNING message: File opened: .\CropData.txt WARNING: No irrigation crops found in CropData.txt Irrigation turned off. Crop (vegetation) information loaded Observation data checks will...
That might be the problem, try some smaller areas. You can also try to change the tile size. Go to the "Hydro" Tab and "Create". There you can change this.
Dear Kristina, I increased the memory allocation to -Xmx20480M, but the same error message still appeared. I assume the issue lies with catchment area (some 118,000 sq km). Is this correct? Kind regards Syamsul
Great to hear! Then I hope you will get subbasins in the format you wish. Kind regards, Kristina
Dear Kristina, I have added "-Xmx10240M" to the batch file and subbasin creation process is now running. Attached is a snippet of the grid management window, showing the flow direction, flow accumulation and DEM raster.
Dear Syamsul, "Java heap space" means that there is not enough memory for the WHIST action. Try to add "-Xmx10240M" to the .bat file (if you have RAM > 16 GB or more). Could you please also send me a screen shot of the grid management window as well (go to the main menu/basin/grid folders)
Dear Admin, I have been trying to generate subbasins using different methods (e.g., Floodplain Database and Flow Accumulation_GWD_LR), but I encountered error messages (see attached). I have also attached the method settings I selected for your reference. Could you please advise where I might have gone wrong, or if there are specific adjustments I should make? Thank you for your assistance. Kind regards, Syamsul
Thank you for your answer, Charlotta. Neither 1/24 nor 1 as a scaling factor give satisfactory results. We will look into a different approach :) Best, Maggie
Hello, regarding mactrinf it is one of the parameters that need extra consideration, maybe recalibration. The distribution of the rain during the day is one factor. If the rain falls evenly during the day, a scaling factor of 1/24 give the same amount of surface runoff/macroporflow as the daily model. If all the rain falls during one hour a scaling of 1 (i.e. no scaling of the parameter) will give the same amount. Perhaps the most common rain distribution, or the distribution of the most important...
Hi, We're converting a national hype model from daily to hourly. I've looked, at some of the tutorials, R-package (ParScale) and articles. Simply using the exponential decay transformation creates issues for vertical dynamics e.g. mactrinf, mperc1, mperc2. As an example, "mactrinf" is estimated to 50 mm/day in our daily model, which becomes 2.08 mm/hour by simply dividing by 24. Now, 50 mm over a full day is relatively rare (it doesn't happen every year) but 2.08 mm/hour happens frequently (many...
Thanks for your answer, Charlotta! The problem seems to be mostly solved now :) These are the output variables we usually use: !! Output options !! timeoutput variable crun cout cprc ctmp prec evap epot cfsc snow cct2 gwat cro1 cro2 cro3 cros sml1 sml2 sml3 aqin aqut aqwl timeoutput meanperiod 1 Oddly enough if I remove prec from the output then the model (5_27_0) runs without issues (even if I use the "large" AquiferData.txt and a Tobs.txt with negative values) With 5_18_0 I don't need to make any...
Thanks for your answer, Charlotta! These are the output variables we usually use: !! Output options !! timeoutput variable crun cout cprc ctmp prec evap epot cfsc snow cct2 gwat cro1 cro2 cro3 cros sml1 sml2 sml3 aqin aqut aqwl timeoutput meanperiod 1 Oddly enough if I remove prec from the output then the model runs without issues (even if I use the "large" AquiferData.txt and a Tobs.txt with negative values) Best, Maggie
Thanks for your answer, Charlotta! So far the only solution I've come up with is deleting all other aquifers than the ones in the submodel. I'm hoping to find a way to avoid this, but I'm not sure how to solve it. These are the output variables: !! Output options !! timeoutput variable crun cout cprc ctmp prec evap epot cfsc snow cct2 gwat cro1 cro2 cro3 cros sml1 sml2 sml3 aqin aqut aqwl timeoutput meanperiod 1 Best, Maggie
Thank you for the extra information. I have not been able to reproduce any of the errors although I set up a model with one aquifer per subbasin and run submodel. AquiferData: It is true that aquifer states are not reallocated to be smaller, like the subbasin states, when you are running submodel. This means that all aquifers are "calculated" but only the ones included in the submodel are affecting the results. This was a choice made when introducing aquifers to submodel that it was acceptable to...
Update, if I remove the AquiferData.txt file hype runs without issues using 5.18 version, however with hype 5.27 I get the negative unit error I described in my comment above. If I remove all other aquifers than the ones in the subbasins in question hype also runs without issues. So is the conclusion that when using pmsf.txt then all the files for the larger model can remain intact except for AquiferData.txt?
Update, if I remove the AquiferData.txt file hype runs without issues using 5.18 version, however with hype 5.27 I get the negative unit error I described in my comment above.
And this is the "unit" error I get if there are negative temperatures: HYPE version 5.27.0 New versions of HYPE at the HYPE Open Source Community website (hypecode.smhi.se), as well as information on up-coming courses. Observation data checks will NOT be performed Setup- and model data checks will NOT be performed 2011-01-01 20.158 10.437 4.945 2011-01-01 3.54 5.209 5.312 2011-01-01 0 0 0 2011-01-01 1.451 1.337 1.29 At line 3365 of file readwrite.f90 Fortran runtime error: Unit number is negative...
Hi Lotta, Great to hear from you. Sorry about providing insufficient information. Is there a way of sharing our model set-up to make it easier for you? Based on the error provided in the terminal on a server (see further down) I think you are correct in assuming the error is AquiferData based. We have one Aquiferbasin for each SUBID so I don't see how there could be any dependencies affecting this though. The model runs fine without the pmsf.txt file (and with submodel set to "n" instead of "y")...
Hi Russell, I have not been involved with the study, but as you said some of my colleuges have. From the description in the paper it sound like they changed the "iwet" area for the "SM" scenarios. From the model files it looks like they have data included data for both versions of wetland models. Which one that is active can be changed (partly) by the modeloption wetlandmodel in the info-file (at least you can turn off "river wetland", " iwet" seems to be used regardless of setting). /Charlotta
Hi Maggie and Raphael, I have not had problems with negative temperaturese in Tobs. What do you mean by unit error? Is it in the output of temp or ctmp? Maybe the unit problem is related to the problem that causes segmentation fault when you run with the Tobs with only positive temperature? That problem is difficult to pinpoint from the information given. Only that the all xxData.txt files has been read (but maybe not yet pmsf.txt, observations and par.txt). What does the hyss-logg say? How far has...
This is using the submodel through the pmsf.txt argument (http://hype.smhi.net/wiki/doku.php?id=start:hype_file_reference:pmsf.txt&s[]=submodel)
Hi, I'm trying to run submodels in hype. I'm having a few issues> I get a unit error when temperatures are negative in Tobs.txt. Do you also have this issue? If I only run Tobs with positive degrees, the error disappears but a new one arises (but there is no information about it in the log). This is the information from the terminal: /dmidata/projects/hydrologi/DKHYPE/DKHYPE_development/test_models/DKHYPE_MMA_test/Submodels/model$ ./hype_5_27_0 ./ HYPE version 5.27.0 New versions of HYPE at the HYPE...
Dear all, I have a shapefile representing a catchment that has been subdivided into multiple sub-catchments. Some of these sub-catchments include flow routing information—specifically, which downstream sub-catchment they drain into. However, a few sub-catchments are missing this routing information (please see the picture attached). Is there a way to use WHIST to determine or fill in the missing flow routing data for these sub-catchments?. Thanks in advance for your help.
Hi Charlotta, I was reading the paper on modelling mitigation methods by Wynants et al (2024). The scenarios are interesting and I downloaded the model parameter files. I have used their inorganic fertiliser load reduction scenario on my SE Ireland simulation and it has produced some good results, I'm going to write it up soon. What I'm puzzled by is their "SM" mitigation scenario. When I first looked at the files it appeared that they used the "River Wetland" model which is quite simple to set up...
I wonder about the ACC grid. Are the green areas within the grid "nodata"? If so, this might be thee reason for both one-pixel-size subbasins and it is nor possible to "fill up" without a proper Flow accumulation grid. Kind regards Kristina
Dear Kristina, Please find the attached DEM, flow direction (DIR) and flow accumulation (ACC) along with the method settings. Regarding the "one pixel size" subbasins, is it possible that the basin limit area was too small? Kind regards Syamsul
Dear Syamsul, it is difficult to know why there are holes. Could you send me images of your grids? Bith Flow accumulation and flow direction grid in this area? You have many subbasins of "one pixel size", what kind of area is it? kind regards, Kristina