- removed comment
Boundary does not check for storage
Issue #1291
closed
I accidentally selected a variable for a flat boundary condition (with thorn Boundary) without storage. This led to a segfault. Instead, thorn Boundary should output an error message or a warning.
Keyword:
Comments (8)
-
-
- removed comment
- changed watchers to stevenrbrandt
Steve: what was the patch made for?
-
- removed comment
I did not intend to attach that patch to this ticket. Please ignore.
-
- removed comment
I removed the patch from the ticket then.
-
- changed status to open
- removed comment
Add patch to check for storage in the upper level boundary apply routine. All bc that need more than a single timelevel check for the existence of more timelevels themselves.
-
- changed status to open
- removed comment
Thanks.
-
- changed status to resolved
- removed comment
Applied as rev 323 and 324 of Boundary.
-
- changed status to closed
- edited description
- Log in to comment
This patch seems to address a different issue. Does the problem with Boundary still exist?