Home › Forums › RORB – general use › Fatal Error
Tagged: Troubleshooting
- This topic has 6 replies, 5 voices, and was last updated 3 months, 2 weeks ago by Benson Liu.
-
AuthorPosts
-
May 24, 2019 at 10:48 AM #1476TKParticipant
Hi,
I get a ‘fatal error’ message when I click past the second last window of running RORB (i.e. before kc etc are entered). This relates to my catchment file, since the run works with other catchment files. How do I fix this error and make RORB run? How do I go on about troubleshooting this kind of message?Thanks
May 28, 2019 at 1:33 PM #1479Benson LiuModeratorHi TK,
When there is a fatal error normally RORB will have a window pop up that will give you some details as to what the problem is. The window will normally outline what data it has read in and have an error message at the bottom detailing what has gone wrong. If the window didn’t pop up for whatever reason you can view the text file in a text file editor. The file is called RORBWin.tmp and is normally stored in the same folder as the catchment, the storm or parameter file depending on your settings. This file normally isn’t of much use but can give some information for when a run has failed to start. If this file doesn’t give you any sort of information about the problem then can you send me an email with the catchment, parameter and any other input files I would need as well as some extra details about how you are trying to run RORB. My email is benson.liu@dev7.preflight.com.au.
Kind regards,
Benson
July 31, 2023 at 4:40 PM #3055royalbert867ParticipantHello
March 29, 2024 at 10:36 AM #4152Peter CampbellParticipantHi,
I’m getting a similar error. I’m trying to run RORB with a user defined IDF file. After the Model Parameters (Design Rainfall Specification) window, RORB returns the fatal error message “You will need to fix up the catchment (vector) file before proceeding”. The RORBWin.tmp file says:Data checks:
************
Next data to be read & checked:Catchment name & reach type flag
Control vector & storage data
Code no. 9 7.0 Location read as powerhouse
Sub-area areas
Impervious flag
Initial storm data
Rainfall burst times
Data error: burst times 0 0I’ve checked the catchment file and can’t find any errors. Looking at the storm file (which RORB generates), I can see that it’s not applying any of the rainfall data from the ifd file, but I don’t know why. I haven’t seen this error before – can anyone tell me how to fix it, or why it’s saying it’s a catchment file error?
Thanks
PeteApril 2, 2024 at 10:17 AM #4154Benson LiuModeratorHi Peter,
Based on what you have written, the catchment file isn’t causing this error. The error message is a legacy error message from when the rainfall inputs were combined with the catchment file. Since the storm file doesn’t have rainfall in it, and the .tmp file has a data error at the rainfall burst time. This means there is something wrong with the IFD file and RORB isn’t able to create a proper storm file. The first thing to check would be the format of the IFD file and whether RORB is reading it in properly. You can get RORB to open the IFD file and in that window you can check if RORB is reading it properly.
Kind regards,
Benson
August 15, 2024 at 2:27 PM #4173Naomi CParticipantHi,
I keep getting a fatal error when I try to run the RORB input of my data text file. This is my text file that I am trying to run. My teacher’s example works in RORBWin, but when I try my inputs, it just goes to error and my teacher said not to email him about the code… I also sometimes get the FORTRAN error as well. I really cannot identify what error I have and this is our first time using the program.Catchment 4 at Sydney
1, CHANNEL TYPE FLAG – ALL REACHES NATURAL
1,5.1,-99, SUB-AREA A (reach length 5.1KM)
3, STORE HG
1,8,-99, SUB-AREA B (reach length 8km)
4, ADD HG FROM A TO B
5,9.3,-99, ROUTE TO C
2,10,-99, SUB-AREA C
3, STORE SUM
1,8.9,-99, SUB-AREA D (reach length 8.9km)
4, ADD HG FROM c TO A & B
3, STORE
1,7.6,-99, SUB-AREA E (reach length 7.6km)
4, ADD HG FROM E TO C & D
5,3.6,-99, ROUTE TO F (reach length 3.6km)
2,8.5,-99, SUB-AREA F (reach length 8.5km)
5,3.7,-99, ROUTE FROM NODE TO JUNCTION (reach length 3.7km)
3, STORE
1,5.85,-99, SUB-AREA G (reach length 5.85km)
4, ADD HG FROM F TO G
5,5,-99, ROUTE TO K (reach length 5km)
3, STORE
1,10.7,-99, SUB-AREA H (reach length 10.7km)
2,6.7,-99, SUB-AREA I (reach length 6.7km)
3, STORE
1,9.7,-99, SUB-AREA J (reach length 9.7km)
4, ADD HG FROM I TO J
5,3.4,-99, ROUTE TO K (reach length 3.4km)
4, ADD HG FROM K TO I & J
2,5.3,-99, AT THE OUTLET
7.1, NOW AT THE OUTLET. COMPARE OBSERVED AND CALCULATED H/Gs.
0, END OF CONTROL VECTOR
C SUB-AREA AREAS
48.5,44.5,49.7,48.5,48.8,77.5,47.5,52.7,64.9,50.2,64.3,-99
0,-99, ALL AREAS PERVIOUS
0900 HOURS ON 6 NOVEMBER 1971
FIT
C TIME INCREMENTS=2hrs, CALCULATIONS FOR 40 TIME INCREMENTS, 1 BURST, 1 RAIN GAUGE, ASSUME UNIFORM RAINFALL DISTRIBUTION (Give design storm information)
2.,40,1,1,0,-99
0,5, RAIN FROM 0-5 TIME INCREMENTS
Sydney
5.3,14.4,14.4,22,5,-99
C HYDROGRAPH DATA
0,19,-99, START AND END TIMES
CATCHMENT OUTLET
1.9,1.7,1.6,2.2,19.2,42.2,45,52,38,25.5,21.1,18.7,14.5,12.6,11,10,6.5,4,2,1.8,1.6,-99 H/G 19 TIME INCREMENTS AND 20 VALUES.Please help us!!! Assignment due next week.
Many thanks.Attachments:
You must be logged in to view attached files.August 19, 2024 at 9:44 AM #4175Benson LiuModeratorHi Naomi,
From the error message the error is in the storm file portion, the RORB manual goes through the correct format with examples at the end that you can follow.
Also noting that combining the catchment file and storm file is a legacy format and in practice is no longer used. It is now standard practice to have the catchment file and storm file be separate files. The FIT mode is also a legacy mode from when computers had a lot less power and now we generally only use the DESIGN mode, this is so that you have more control over the losses that are chosen and you are able to decide what characteristics of the hydrograph you want to place emphasis on when trying to calibrate.
Kind regards,
Benson
-
AuthorPosts
- You must be logged in to reply to this topic.