Home › Forums › RORB – general use › Missing Individual .out Files
- This topic has 2 replies, 2 voices, and was last updated 2 weeks ago by
Yanni Wang.
-
AuthorPosts
-
March 3, 2026 at 11:20 AM #4481
Yanni Wang
ParticipantHi Benson,
We’ve recently come across an issue in RORB where, when running in ensemble mode, the model occasionally fails to generate the individual .out files. In these cases, the _batch.out file is still produced and appears normal, but the individual output files are missing.
In one of our projects, we found that deleting a dummy junction and reach “magically” resolves the issue. While we can still retrieve the node results by printing the downstream reach, we can’t identify any logical reason why this small structural change would affect whether RORB writes the .out files.
A snippet of the two setups is attached below for reference, along with screenshots of the corresponding output folders.
Would you have any insights into what might cause RORB to behave this way?
Happy to provide the model files if that helps diagnose the issue.
Thanks,
YanniAttachments:
You must be logged in to view attached files.March 10, 2026 at 11:40 AM #4485Benson Liu
ModeratorHi Yanni,
The only thing I can think of is if those print nodes are set as interstation areas and there are only dummy reaches on that branch RORB may have issues with the lack of routing. If you run one of those storm files with the .catg file that doesn’t work, does it produce an output/temp file at all or any errors? That may give an indication on why RORB is failing.
Kind regards,
Benson
March 11, 2026 at 2:02 PM #4486Yanni Wang
ParticipantI don’t think the model has any branches with only dummy reaches. The attached snippet shows a bigger picture of the setup for this interstation area, with the area from my original post highlighted in red. I’m not sure if anything stands out to you?
I can run RORBwin using the individual .stm files with the same .catg file that doesn’t work. There’s no error or temp file created, and the .out file looks great.
Running RORB through the CMD works too, so at the moment the workaround is basically: run RORBwin to generate the .stm files, then run the CMD version again…
As I mentioned earlier, this issue pops up occasionally (not just in this model), but we didn’t realise the “magic fix” until now.
Best Regards,
Yanni-
This reply was modified 2 weeks ago by
Yanni Wang.
-
This reply was modified 2 weeks ago by
Yanni Wang.
Attachments:
You must be logged in to view attached files. -
This reply was modified 2 weeks ago by
-
AuthorPosts
- You must be logged in to reply to this topic.
