Skip to content

Incorporation of variables for Data types #63

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

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

JulStraus
Copy link
Member

This is a first take at introducing variables as outlined in #11. It is a slight modification compared to the original proposal from my end to allow for declaring variables as well on the abstract type level. In addition, the filtering is used to avoid that a user must create two new functions. Instead, the design is similar to creating new variables for an element.

All data variables are created for a subtype of AbstractElement. This implies that functions must be created for each individual subtype. This is in line with the existing philosophy.

I included the approach as well for InvData to illustrate the application.

The PR also includes a renaming of Data to ExtensionData as proposed in #11. If undesired, we can revert the commit. Note that it is hence better to look directly at the individual commits.

Deprecated versions left within the code base

The following functionality is retained, but will be removed in a breaking release:

  1. I left the old Data.
  2. I left the call for variables_capex in create_model as well as the functions for Link and Node.

@JulStraus JulStraus requested a review from hellemo June 5, 2025 10:51
@JulStraus JulStraus added the enhancement New feature or request label Jun 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant