NatLabRockies / NatLabRockies/H2Integrate
Add any notion of on or offshore locationality
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 26
- Forks
- 44
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 16
Description
Add any notion of on or offshore locationality
Prior versions of GreenHEART had different logic if a technology was located on or offshore.
Most all of the offshore capabilities have not been maintained with the newer H2I framework.
This includes both fixed and floating offshore.
Proposed solution
With #384, we've removed some of the offshore computations and files.
We'd have to bring some of that back in and integrate it with the existing framework to enable these offshore capabilities.
Alternatives considered
Additional context
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing issue #384 and the offshore computations and files it removed, then compare that history with the current H2I framework. Determine the integration points needed for onshore, fixed offshore, and floating offshore technologies. Done means all three location modes are supported by the existing framework and their behavior is covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100