-
Notifications
You must be signed in to change notification settings - Fork 273
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
complexFaultRupture error, too many values to unpack? #8278
Comments
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 |
Previous issue and resolution: #5440 |
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. |
This is a node named <complexFaultGeometry>
... something inside ...
</complexFaultGeometry> In general any structure with the form |
Ok, thank you so much! I get it now. |
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.
The text was updated successfully, but these errors were encountered: