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

Allow users to omit demand slicing information for uniform demand across the year #367

Open
alexdewar opened this issue Jan 30, 2025 · 0 comments
Labels
enhancement New feature or request future work Not to be tackled in the course of this engagement

Comments

@alexdewar
Copy link
Collaborator

Currently if a user provides demand slicing information for a process for at least one time slice, they must provide information for all time slices (possibly with entries covering whole seasons etc. -- the important thing is all time slices are covered).

However, the user may simply want uniform demand across the year and it seems a little perverse to make them supply all this information in demand_slicing.csv. We could just have a rule that if the user doesn't provide demand slicing for a process for any time slices, then we assume demand is uniform (i.e. just proportional to time slice length).

This does raise the possibility of a situation where no demand slicing needs to be specified at all. At present we don't allow users to provide empty CSV files (#106), so in this case we would have to require that they not provide the file at all.

@alexdewar alexdewar added the enhancement New feature or request label Jan 30, 2025
@github-project-automation github-project-automation bot moved this to 📋 Backlog in MUSE Jan 30, 2025
@alexdewar alexdewar added the future work Not to be tackled in the course of this engagement label Jan 30, 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 future work Not to be tackled in the course of this engagement
Projects
Status: 📋 Backlog
Development

No branches or pull requests

1 participant