Custom Query (454 matches)
Results (10 - 12 of 454)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #492 | fixed | Add NGAWest2's to Attenuation Relationship Plotter | ||
| Description |
Requires some parameter modifications to the attenuation relationships themselves, not just addition to the list in the application. |
|||
| #115 | fixed | Add Nitin's modifications of gridded regions | ||
| Description |
Requirement was to provide an ability where lat and lon intervals can be specified differently. Usually 1 degree lat and lon translate to 111 kms but as we go up North, within Canada, that is not the case, 1 degree lat is not equivalent to 1 degree lon, ie. 111kms. In fact 1 degree lon might translate to may be 40-50kms (don't quote me the exact number). Thus this requirement. To accomplish this, I modified the GriddedRegion? class, where it takes lat interval as well as lon interval. Internal functionality of the class remain the same, just instead of using a common interval when creating locations within the gridded region, all longitudes will be based on lon spacing and all latitudes will be based on lat interval. Once the list of lats and lons are created, the one's within the polygon remain and others are excluded (this part exactly what it was earlier). BTW, the ability to specify a common interval for both lat/lon still remains, and internally within the code both lat and lon spacing will be using this common spacing. Specifying a different lat/lon spacing (in degrees) helps to keep them equidistant in kms and thus reduce event set while keeping the hazard almost the same. I did test to the extent that all locations generated, using different spacing, are within the given polygon. |
|||
| #318 | fixed | Add Preconditions to ERF_GuiBean & IMR_MultiGuiBean to make sure no duplicates, not null, etc | ||
| Description |
The ERF_GuiBean & IMR_MultiGuiBean should make sure that it doesn't get a list of ERFs/IMRs that:
|
|||
