-
Notifications
You must be signed in to change notification settings - Fork 108
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
Store everest results in ERT storage #9161
Open
yngve-sk
wants to merge
6
commits into
equinor:main
Choose a base branch
from
yngve-sk:24.10.25.store-everest-opt-results-in-ertstorage
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Store everest results in ERT storage #9161
yngve-sk
wants to merge
6
commits into
equinor:main
from
yngve-sk:24.10.25.store-everest-opt-results-in-ertstorage
+1,310
−1,596
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #9161 +/- ##
==========================================
+ Coverage 90.70% 90.72% +0.02%
==========================================
Files 351 351
Lines 21903 21908 +5
==========================================
+ Hits 19867 19876 +9
+ Misses 2036 2032 -4
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
yngve-sk
force-pushed
the
24.10.25.store-everest-opt-results-in-ertstorage
branch
14 times, most recently
from
November 13, 2024 11:20
7081e58
to
32193bd
Compare
yngve-sk
changed the title
(wip) Store everest results in ERT storage
Store everest results in ERT storage
Nov 13, 2024
yngve-sk
force-pushed
the
24.10.25.store-everest-opt-results-in-ertstorage
branch
13 times, most recently
from
November 15, 2024 13:06
5b54ee7
to
dda3db9
Compare
yngve-sk
force-pushed
the
24.10.25.store-everest-opt-results-in-ertstorage
branch
from
December 20, 2024 12:24
dfcba5a
to
7f9f165
Compare
yngve-sk
force-pushed
the
24.10.25.store-everest-opt-results-in-ertstorage
branch
2 times, most recently
from
December 20, 2024 12:41
7edb72e
to
08a476c
Compare
yngve-sk
force-pushed
the
24.10.25.store-everest-opt-results-in-ertstorage
branch
8 times, most recently
from
January 6, 2025 13:41
25bd3a1
to
a23a3bf
Compare
yngve-sk
force-pushed
the
24.10.25.store-everest-opt-results-in-ertstorage
branch
8 times, most recently
from
January 8, 2025 07:08
afae3e0
to
92b78dd
Compare
Deprecated by storage (which exports all the data anyway)
yngve-sk
force-pushed
the
24.10.25.store-everest-opt-results-in-ertstorage
branch
2 times, most recently
from
January 8, 2025 12:38
2e14874
to
fc694ab
Compare
yngve-sk
force-pushed
the
24.10.25.store-everest-opt-results-in-ertstorage
branch
from
January 8, 2025 12:58
fc694ab
to
b3761a4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
Resolves #8811
Store it as some dataframes and dump it in storage, not entirely sure how much of it should be saved. Will use everest_data_api as reference for what is required.
Objectives, constraints and control names are pivoted so that each distinct value has its own column, which is more concise and better to serve via an API. It makes each row in the dataset represent the entire set of controls, objectives, and constraints for one
batch | batch -> realization | batch -> realization -> perturbation
.Objective results:
Gradient results: