Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

User Input Unit Conversion (bbl/week to bbl/day) #109

Closed

Conversation

melody-shellman
Copy link
Contributor

Fixes/Addresses/Summary/Motivation:

The goal is to convert current user input units (bbl/week) to bbl/day while maintaining the same time period discretization for the model optimization model. Our variables v_F_Piped and v_F_Trucked will now represent a rate bbl/day, but decisions will still be made on a weekly time scale.

Changes proposed in this PR:

Input Files (layflat full, small case study)

  • Create new tab "TimePeriodSetup" for user input days_in_period
  • Change all user input to be in units per day. Modify the tabs: CompletionsDemand, PadRates, FlowbackRates, InitialPipelineCapacity, InitialDisposalCapacity, InitialTreatmentCapacity, FreshwaterSourcingAvailability, PadOffloadingCapacity, DisposalCapacityIncrements, TreatmentCapacityIncrements, PipelineCapacityIncrements
  • Update the label (not values) of units on the following tabs from $/bbl to $/bbl/day: (DisposalExpansionCost, TreatmentExpansionCost, PipelineCapexCapacityBased)

Model

  • Add new model parameter tau^DaysInPeriod
  • Update constraints with the DaysInPeriod factor. The constraints affected by this changes are those related to storage balance, total volumes, and operational costs.
  • Update RST documentation

Testing and Results

  • Currently does not pass all tests. CBC does not reach an optimal solution for the small strategic case study in the 7min allotted. This should be resolved with the scaling.
  • These changes alter the results slightly: This comes from capex costs for treatment, disposal, and pipeline (capacity based). These were originally calculated with these units:

[binary] * capacity [bbl/week] * cost per capacity [$/bbl] = [$/week].

This is not technically right. This should be a straight dollar value. I converted units to per day for our unit conversion, I also updated the cost per capacity to be in units to [$/bbl/day] so we get to following:

[binary] * capacity [bbl/day] * cost per capacity [$/bbl/day] = [$].

Cost per capacity values from Karen, I believe, were already in [$/bbl/day], but capacity values decreased in the conversion, so the cost for the same capacity expansion has decreased by a factor of 7, changing the results slightly.

Legal Acknowledgement

By contributing to this software project, I agree to the following terms and conditions for my
contribution:

  1. I agree my contributions are submitted under the license terms described in the LICENSE.md file
    at the top level of this directory.
  2. I represent I am authorized to make the contributions and grant the license. If my employer has
    rights to intellectual property that includes these contributions, I represent that I have
    received permission to make contributions and grant the required license on behalf of that
    employer.

@lbianchi-lbl lbianchi-lbl added this to Unprioritized in Priority Mar 15, 2022
@ksbeattie ksbeattie moved this from Unprioritized to Normal priority in Priority Mar 15, 2022
@ksbeattie ksbeattie added the Priority:Normal Normal Priority Issue or PR label Mar 15, 2022
@ksbeattie ksbeattie removed this from Normal priority in Priority Mar 15, 2022
@melody-shellman melody-shellman marked this pull request as ready for review April 13, 2022 22:33
@melody-shellman melody-shellman requested review from RuudWag and removed request for NienkeWagenaar April 25, 2022 14:09
@melody-shellman melody-shellman marked this pull request as draft May 3, 2022 19:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority:Normal Normal Priority Issue or PR
Projects
No open projects
Status: Done
Development

Successfully merging this pull request may close these issues.

None yet

2 participants