USACE / USACE/go-consequences

diagram out structural changes to code to support reconstruction

Open
#126 17 comments 0 reactions 1 assignee View on GitHub

@sebastianrowan is already working on this.

Since Nov 24, 2025.

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

Description

Reconstruction is a feature in go-consequences we seek to include. This ticket is for evaluating the strategy and structural changes expected in the code base to plan out the feature.

  1. is this a relevant change to go-consequences or should this be in consequences-runner?
  2. evaluate what parameters need to be tracked for reconstruction, identify all interfaces that need to be created or extended
    a. is reconstruction period a damage category or occupancy or structure level attribute? what does it contain?
    b. what other reconstruction parameters need to be tracked? number of times damaged? if it is in the flood zone (eo11988 compliance)
    c. how do we want to handle events? do we extend the consequences receptor interface to allow for an array of hazards? how do we want to manage it?
    d. do we need hazard provider changes?
  3. given the parameters develop psuedo code for how reconstruction would be accomplished.

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.