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

Add-API for UserDemand tables #1921

Open
SouthEndMusic opened this issue Oct 29, 2024 · 0 comments
Open

Add-API for UserDemand tables #1921

SouthEndMusic opened this issue Oct 29, 2024 · 0 comments
Labels
python Relates to one of the Ribasim python packages

Comments

@SouthEndMusic
Copy link
Collaborator

It has turned out on several occasions that the UserDemand tables (specifically the UserDemand \ time table), are hard to understand in terms of what they allow the modeller to do. In essence this table define mappings of the form (node_id, priority, time) -> demand, but it is not a priori clear which column is an input of this mapping an which is an output. Hence the erroneous conclusion that priority can be time dependent (for instance here).

These confusions arise in part because the tables are in long format, but we probably are not going to deviate from that. To make defining input more intuitive, we can offer more user-friendly functions in Ribasim python which create these tables in the background. This has earlier been proposed (but not yet implemented) here.

@github-project-automation github-project-automation bot moved this to To do in Ribasim Oct 29, 2024
@SouthEndMusic SouthEndMusic added python Relates to one of the Ribasim python packages enhancement labels Oct 29, 2024
@SouthEndMusic SouthEndMusic changed the title Add-API for Userdemand tables Add-API for UserDemand tables Oct 29, 2024
@visr visr removed the enhancement label Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
python Relates to one of the Ribasim python packages
Projects
Status: To do
Development

No branches or pull requests

2 participants