Custom Query (454 matches)

We may want to rethink our default fault sizes, especially since screens are getting higher and higher density. For example, Ned says that he is constantly increasing font sizes for plots.

When a Region(Location, Location) is initialized, it's north and east borders are expanded ever so slightly that contains() returns true. It turns out that double precision rounding errors can contribute to shifting the south and west borders such that nodes on those borders return false for contains(). The same 'inflation' logic should be applied there as well.

In

	protected EvenlyGriddedSurfFromSimpleFaultData(FaultTrace faultTrace, double aveDip,
			double upperSeismogenicDepth, double lowerSeismogenicDepth, double maxGridSpacingAlong,
			double maxGridSpacingDown) throws
			FaultException {
		
		double length = faultTrace.getTraceLength();
		double gridSpacingAlong = length/Math.ceil(length/maxGridSpacingAlong);
		double downDipWidth = (lowerSeismogenicDepth-upperSeismogenicDepth)/Math.sin(aveDip*Math.PI/180 );
		double gridSpacingDown = downDipWidth/Math.ceil(downDipWidth/maxGridSpacingAlong);
/*		
		System.out.println(faultTrace.getName()+"\n\t"+
				maxGridSpacingAlong+"\t"+(float)gridSpacingAlong+"\t"+(float)gridSpacingDown+"\t"+
				(float)(faultTrace.getTraceLength()/gridSpacingAlong)+"\t"+
				(float)(downDipWidth/gridSpacingDown));
*/				

		set(faultTrace, aveDip, upperSeismogenicDepth, lowerSeismogenicDepth, gridSpacingAlong, gridSpacingDown);
	}

the maxGridSpacingDown isn't used, the along strike value is (mistakenly?) used instead.