-
Notifications
You must be signed in to change notification settings - Fork 6
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
Introduce optimization equation #98
Merged
Merged
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
glatterf42
force-pushed
the
include/optimization-equation
branch
2 times, most recently
from
August 22, 2024 14:36
7b510d8
to
9dcb186
Compare
glatterf42
force-pushed
the
include/optimization-equation
branch
from
September 30, 2024 10:43
0677fa0
to
8c25ad6
Compare
meksor
approved these changes
Oct 2, 2024
glatterf42
force-pushed
the
include/optimization-equation
branch
from
October 3, 2024 08:59
8c25ad6
to
0ce1557
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.
This PR introduces the final item of the message data model:
Equation
. It comes complete with everything the other items already have and only minor changes toColumn
that are required for this to work.Since this is almost identical to #97, my questions are also very similar:
level
s andmarginal
s doEquation
s have? At the moment, I'm assuming that everyKey
(one row of entries inEquation.data
) can have its ownlevel
andmarginal
, making those two just arbitrary columns inEquation.data
(though maybe we could limit them to beingfloat
s or so).Equation
s need to getdata
added to them manually via anadd()
function? Or is there data sort of filled in automatically by the gdx code? I don't think I remember lots ofequation.create()
,equation.add_data()
functions from the westeros tutorials.Working on the transport tutorial, I noticed that I had completely forgotten about adding
equations = db.relationship()
in theRun
DB-table. I have even run migrations for these other PRs, but no error came up. I'm wondering if we even need theserelationship()
declarations at all.