Uploaded image for project: 'Ergo'
  1. Ergo
  2. ERGO-363

Buried pipeline damage task should add logging if hazard type is not correct

XMLWordPrintableJSON

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • 4.1.0
    • 4.0.0, NIST-V1
    • Analysis
    • None

      HazusPipelineDamageTask should log a warning if no matching hazard type was found for a fragility curve. Currently, if no exact demand type is found and no conversion is found, it defaults to 0.0.

      Should pipes always use PGV? If so, we can fail the analysis. If not, then we should at least log a warning that no conversion was found.

              Unassigned Unassigned
              cnavarro Christopher Navarro
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:

                  Estimated:
                  Original Estimate - 2 hours
                  2h
                  Remaining:
                  Remaining Estimate - 2 hours
                  2h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified