-
Notifications
You must be signed in to change notification settings - Fork 1
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
Reverse ordering of corners of a triangular fault #3
base: triangular_updates
Are you sure you want to change the base?
Conversation
… for amrflags array.
WIP: Triangular Okada updates
Add UNSET option to flag2refine2
Thanks for looking at this @dsrim. I thought it might be an assumption of orientation. A few comments.
|
… set ``self._fix_orientation`` flag then fix the sign - removed ``rake=90.`` as an optional input argument to ``self.calculate_geometry_triangles()`` and made ``rake`` required for ``self.set_corners()``
9d292db
to
be6e92f
Compare
to see if travis then works on clawpack/clawpack
add liblapack-pic to apt-get
…angular_angular
… or ``self.calculate_geometry_triangles``
Triangular angular - fix rise_time functions
The solver assumes that the corners (vertices) of the triangular subfault should be oriented counter-clockwise. If two vertices are swapped, the orientation reverses, negating the resulting deformation. This is now fixed when we check the sign of
normal[2]
(if the normal points downwards, it is oriented clock-wise), by reversing the ordering of givenself._corners
byself._corners.reverse()