Custom Query (454 matches)
Results (43 - 45 of 454)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #14 | fixed | Atten Rel Plotter printing bugs | ||
| Description |
When printing data from the Attenuation Relationship Plotter, I can only get the a truncated first line of the parameters (see attached scan). Also, the last line of data on each page is garbled. Any suggestions for a fix? Thanks Maurice Amendolagine, P.E., G.E. Senior Geotechnical Engineer GEI Consultants, Inc. 2141 Palomar Airport Road, Suite 160 Carlsbad CA 92011-1463 760-795-1968 direct 760-929-9136 main 760-929-0836 fax mamendolagine@… |
|||
| #144 | fixed | AttenuationRelApp nightlies crashing on startup | ||
| Description |
Editors not loading properly becasue propEffectParams return DoubleEditor? but the themselves do not descend from DoubleParameter?, rather PropEffectParam?<Double>. All the propEffectParams are distance values that are doubles so I'm going to change the hierarchy which will reduce some of the generic tagging. However, I'm not sure what side-effects this might have just yet. |
|||
| #470 | fixed | AttenuationRelationship assumes that func.get(i).setLocation(x,y) will update underlying func (CRITICAL) | ||
| Description |
AttenuationRelationship?.getExceedProbabilities(...) updates the passed in function by getting Point2D values, and then calling setLocation. This is not (or at least should not be) part of the DiscretizedFunc? specification, as some functions are not (and have never been) backed by Point2Ds - for example evenly discretized functions. This is a big bug that has affected any hazard curve calculations in the last 2 weeks (since the switch to the fixed x value function in the calc code), and any prior curve calculations or imr.getExceedProbabilities calls that were done with evenly discretized x values (uncommon). We definitely got lucky that the unit tests last night caught this bug. |
|||
