Opened 13 years ago

Closed 13 years ago

#165 closed defect (fixed)

Bug in IM event set calculator ver 3

Reported by: keith@… Owned by: Kevin Milner
Priority: major Milestone: OpenSHA 1.2
Component: sha Version:
Keywords: Cc:

Description

From Keith Porter:

Hi, Kevin,

I just noticed that in IM event set calculator ver 3, Vs30 for site 0 seems always to default to 760 m/sec, then site 1 is assigned the Vs30 shown in the input file for site 0, and site 2 is assigned the Vs30 for site 1, etc. There's a workaround: duplicate input records at every change in Vs30, but I thought you might want to check the indexing on Vs30.

Also, I realize that I wrote the spec on HAZ01A and HAZ01B, but I find in practice that the 1st line of explanatory text is a nuisance, and doesn't provide value. If you update the calculator, may I suggest eliminating that line of output and just starting with the column header line?

Best regards,

-- Keith

Change History (1)

comment:1 Changed 13 years ago by Kevin Milner

Milestone: → OpenSHA 1.2
Resolution: → fixed
Status: new → closed

Fixed in revision [7570]. This bug is only in the output file...not the actual calculated results. The correct Vs30 value was used in calculation, just outputted incorrectly in the HAZ01A file.

I also removed the first header line from HAZ01A and HAZ01B output.

Zip file on the website was also updated. New version can be downloaded here: ​http://opensha.usc.edu/apps/opensha/IMEventSet/IM_EventSetCalc_v3_0_ASCII.zip

Note: See TracTickets for help on using tickets.