Skip to content

Conversation

@softwareengineerprogrammer
Copy link
Owner

@softwareengineerprogrammer softwareengineerprogrammer commented Dec 20, 2025

Description

Addresses NREL#443

  1. Multiple construction years: Update Fervo_Project_Cape-4 (or make new Fervo_Project_Cape-5) based on publicly stated timelines - https://fervoenergy.com/fervo-energy-raises-462-million-series-e-to-accelerate-geothermal-development-and-meet-surging-energy-demand-with-clean-firm-power/
    1. Phase I (100 MW)
    2. Phase II (500 MW)
  2. Reservoir engineering updates
    1. ~8.5" ID
    2. Flow rate
    3. Fracture surface area
    4. PI/II instead of impedance
    5. Number of Fractures per Stimulated Well
    6. Increased lateral length (adjust fracture separation accordingly)
  3. Higher discount & bond rates
  4. Sensitivity analysis
  5. Incorporate ATB updates: https://atb.nrel.gov/electricity/2024b/geothermal
  6. Calibrate exploration cost to https://atb.nrel.gov/electricity/2024b/geothermal

Testing & Verification

  1. Unit tests added: Describe new unit tests added, if any.
  2. Unit tests updated: Describe existing unit tests that were updated, if any.
  3. Manual testing: Describe any additional manual testing steps that were performed, such as running the change on a pre-existing data set you own.

Change Checklist:

Observe the following checklist items if your change includes a new version (see versioning notes and version management docs).

Before merging:

  1. Add a CHANGELOG entry (example). RST Template:
M.m.P: `TITLE <https://github.com/NREL/GEOPHIRES-X/pull/PR-NUMBER>`__ | `release <https://github.com/NREL/GEOPHIRES-X/releases/tag/vM.m.P>`__

After merging:

  1. Push tag(s) to GitHub: git push origin refs/tags/vM.m.P
  2. Post a change announcement to the GEOPHIRES Change Announcements Discussion (example). Markdown template:
M.m.p: [TITLE](https://github.com/NREL/GEOPHIRES-X/pull/PR-NUMBER) | [release](https://github.com/NREL/GEOPHIRES-X/releases/tag/vM.m.P)

Additional metadata such as TODO items or link to your initial self-review (PR into your own fork created prior to submission)

@softwareengineerprogrammer
Copy link
Owner Author

Rebased, see #117

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants