USACE / USACE/go-consequences

Add LifecycleHazardProvider

Open
#61 0 comments 0 reactions 1 assignee View on GitHub

@HenryGeorgist is already working on this.

Since Jul 12, 2021.

enhancement
Dominant language
Go
Stars
21
Forks
12
Avg merge
2d 10h
Merged PRs (30d)
4

Description

We need a lifecycle hazard provider this will help compute lifecycle based consequences at a structure including activities like reconstruction.

The interface might look something like the call below

ProvideHazards(l geography.Location) ([]hazards.HazardEvent, error) 

where the list of hazard events represent events across time, that will allow for a structure to know all of the sequence of events at the time of compute.
Other designs might be relevant, where we create a hazards.TemporalHazardEvent which tracks date time of the event? This would be beneficial to help regardless, but we need the list at the time a structure is processed to allow for the structure to preserve memory - which is a bit problematic because that requires the entirety of the hazard to be stored prior to computation of consequences.

There are alot of pieces to this puzzle that we need to think about clearly to create the best process possible.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.