-
Notifications
You must be signed in to change notification settings - Fork 35
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
[Question] apply crosscutting relationship to fault network #138
Comments
Hi Matt, if you have faults that overprint other faults then what you need to do is pass the keyword faults with an argument which is a list of faults that overprint the fault, so basically if you have three faults a,b, and c and fault c is faulted by both a and b when you build fault c you would use this syntax. model.create_and_add_fault('c',displacement,faults=[a,b]) where a and b are the object returned from create_and_add_fault or model['a']... hope this helps. If you do this you will have to have the displacement vector consistent with the direction of displacement and you need to change the displacement magnitude to fit the observed fault pattern. Cheers |
Thanks Lachlan, Makes sense |
How does loopstructural expect to receive the displacement vector? is it an angle, or dx/dy or something else? |
Hi matt, you need to specify the 3 components of the displacement vector as a list or numpy array. Or use data to constrain the first coordinate of the fault frame. |
Hi Matt, Sorry, that is actually my misunderstanding of your question and being in holiday mode! The fault displacement is defined by a vector which is the slip vector. This vector is then scaled by the displacement which should be a signed value. If you want to specify the slip vector you'll need to add the argument cheers |
To make things "simpler" could I just assume that all older faults are crosscut by all younger faults, even if they aren't anywhere near each other and don't intersect? This way I could just group the younger fault sets rather than specify a crosscutting relationship for each. This might not be a good idea... |
If you want to visualise the movement sense you can add the following: view.add_vector_field(BendigoZone_model[fault_display[i]][1],locations=model.regular_grid()[:100]) This will add the slip vector as a vector field randomly within the model at 100 locations (BendigoZone_model.regular_grid() is just a helper method to get points within the model area). The fault restoration vector (opposite to displacement) is this vector multiplied by the displacement magnitude. |
I've got multiple generations of faults. abutting relationships work well within the same generation. However I've a couple of later episodes cut the older faults by ~90 degrees and offset them.
Is there an option to add this sort of relationship?
Also, is there a way to add a little more detail to the intersections to reduce the sawtooth pattern?
The text was updated successfully, but these errors were encountered: