Closed YProDia closed 1 year ago
Where did you get the rupture file? The format it uses is invalid and before it only happened to work. The error message is clear, you have too many complexFaultGeometry
nodes, there can be only one. Before the engine was just taking the first node, now it is warning you about the others. If you want to get the same results as in the past just remove the extra nodes of kind complexFaultGeometry
.
Previous issue and resolution: https://github.com/gem/oq-engine/issues/5440
Where did you get the rupture file? The format it uses is invalid and before it only happened to work. The error message is clear, you have too many
complexFaultGeometry
nodes, there can be only one. Before the engine was just taking the first node, now it is warning you about the others. If you want to get the same results as in the past just remove the extra nodes of kindcomplexFaultGeometry
.
Thanks for your answer. I made the rupture file in the webui interface with the earthquake rupture preparation tools. My rupture is an actual fault in my study area, so I used its coordinates. Sorry, I'm afraid I'm not quite sure what are the "nodes" exactly. I've taken a look at the user manual and I'm not sure whether it's the English language (which is not my mother tongue) or the programmer language, but I'm not really grasping what are you referring to. I checked issue #5440 before opening this issue but I still couldn't figure out where the problem was for the same reason, I don't know what "node" refers to in this context.
This is a node named complexFaultGeometry
in XML:
<complexFaultGeometry>
... something inside ...
</complexFaultGeometry>
In general any structure with the form <name> ... </name>
is an XML node called name
.
Ok, thank you so much! I get it now. You see, this fault has a really weird geometry, it not only changes dip with depth but the upper part sort of bifurcates into two strands, like in depth it can be projected in the horizontal as a single straight line, but as you move from the lower part towards the surface that line splits into two at a certain point (at 2.5 km depth) and from there upwards the dip changes for both strands. At first I tried including two complexFaultGeometry surfaces which at 2.5 km depth shared the middle point in the intermediate edge, because I thought that was the most accurate way to represent that geometry... Clearly not a good idea now that I know how it works and reads the file. Thanks again!
I've been having some trouble with a seismic hazard scenario simulation including a complex fault rupture in OpenQuake. The simulation keeps failing and this is the traceback error that I get:
The rupture input file that I'm using is this one:
The weird thing is, I've done simulations with the same rupture before (a few years ago), and they used to work. But now I have to redo some calculations and I need to make a new simulation with this particular rupture, and it no longer works. The old simulation crashes too if I try to remake it, and I get exactly the same traceback, so my guess is the issue is somewhere around the rupture file. I've even remade the rupture input file to make sure the format was up to date with the current version of the engine, and the simulation still fails. I'm not really a programmer, I use OpenQuake through the webui user interface, and I don't really understand where is the error exactly or how to fix it. If someone could please help me with this issue, I'd honestly appreciate it.