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.

Sign up for GitHub

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

Jump to bottom

[Feature Request] Keep the datafile paths. #35

Open
samgdotson opened this issue Feb 18, 2022 · 0 comments
Open

[Feature Request] Keep the datafile paths. #35

samgdotson opened this issue Feb 18, 2022 · 0 comments
Labels
Comp:Input This issue has to do with the input component of the code or document. (input parameters, prep) Difficulty:1-Beginner This issue does not require expert knowledge and may be a good issue for new contributors. Priority:4-Low This work is valuable, but not urgent or mission critical. Status:1-New No one has claimed this issue yet. It is in need of solving. Type:Feature New feature or feature request

Comments

@samgdotson
Copy link
Collaborator

Demand commodities and technologies with variable capacity factors should keep the file paths used to create their respective time slices.
@samgdotson samgdotson self-assigned this Feb 18, 2022
@samgdotson samgdotson removed their assignment Feb 11, 2025
@samgdotson samgdotson added Comp:Input This issue has to do with the input component of the code or document. (input parameters, prep) Difficulty:1-Beginner This issue does not require expert knowledge and may be a good issue for new contributors. Priority:4-Low This work is valuable, but not urgent or mission critical. Status:1-New No one has claimed this issue yet. It is in need of solving. Type:Feature New feature or feature request labels Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Comp:Input This issue has to do with the input component of the code or document. (input parameters, prep) Difficulty:1-Beginner This issue does not require expert knowledge and may be a good issue for new contributors. Priority:4-Low This work is valuable, but not urgent or mission critical. Status:1-New No one has claimed this issue yet. It is in need of solving. Type:Feature New feature or feature request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@samgdotson