Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / waterfutures/epyt-flow issues and pull requests
#24 - Loading custom data and network
Issue -
State: closed - Opened by meghnathomas 17 days ago
- 2 comments
#23 - Extended visualization
Pull Request -
State: closed - Opened by kurceliana 20 days ago
- 3 comments
#22 - A suggestion: I think it would be nice to add a page at the beginning of the in-depth tutorial summarizing the functionalities epyt-flow offers. This could include a complete list of the uncertainties, events, faults, and controls you allow users to model, and ideally would include time series or spatial plots to better visualize these things (e.g., abrupt and incipient leaks, sensor override attacks, different uncertainty distributions, etc). Having all of these cases in one single page could provide users with a clear overview of what the package offers
Issue -
State: closed - Opened by andreArtelt about 1 month ago
- 2 comments
#21 - Events -> Sensor faults: currently epyt-flow can model only one kind of fault affecting any sensor, right? Just curious - in the future, will you consider allowing multiple faults to affect sensors?
Issue -
State: closed - Opened by andreArtelt about 1 month ago
- 2 comments
#20 - Scenarios -> Basics: what sort of "potential exceptions that might occur during the process of setting up and running the simulation" might a user encounter?
Issue -
State: closed - Opened by andreArtelt about 1 month ago
- 2 comments
#19 - Abrupt Leakage Example: not a big deal at all, but would it be possible to standardize the y-axis ticks so it is easier to interpret?
Issue -
State: closed - Opened by andreArtelt about 1 month ago
- 2 comments
#19 - Abrupt Leakage Example: not a big deal at all, but would it be possible to standardize the y-axis ticks so it is easier to interpret?
Issue -
State: closed - Opened by andreArtelt about 1 month ago
- 2 comments
#18 - I recommend adding legends to all plots with multiple lines so it is clear what each line represents. And also checking the x and y axis labels and ticks (e.g. in Pump State Events Example top plot, does y axis value = 2.0 means the pump is off and 3.0 mean the pump is on? In the bottom plot, are you plotting tank water volume? I think it is straightforward to interpret the plots if you are a WDS expert but it might be useful to have more clear plots for newer users! :-) )
Issue -
State: closed - Opened by andreArtelt about 1 month ago
- 2 comments
#17 - Event Detection: would it be possible to elaborate a little more on the results and the plot? Is the algorithm able to successfully detect one event but not all three?
Issue -
State: closed - Opened by andreArtelt about 1 month ago
- 2 comments
#16 - What is the default sensor placement for each network/scenario?
Issue -
State: closed - Opened by andreArtelt about 1 month ago
- 3 comments
#16 - What is the default sensor placement for each network/scenario?
Issue -
State: open - Opened by andreArtelt about 1 month ago
- 1 comment
#15 - Events -> Actuator events: actuator events are analogous to EPANET time-based controls, correct? What takes precedence if you have both an actuator event and a control acting on an element (e.g., a pump)?
Issue -
State: closed - Opened by andreArtelt about 2 months ago
- 2 comments
#14 - How would you recommend new users learn to use the package? Would you suggest they first go through the in-depth tutorial then recreate all the examples? Since epyt-flow offer so many functions, I think it would be great to include suggestions for how to get started! Or at least add a link to the in-depth tutorial on the landing page since it seems like a very important guide to the package functionalities
Issue -
State: closed - Opened by andreArtelt about 2 months ago
- 2 comments
#13 - Events -> Leakages: how are leaks modeled in epyt-flow? I see leaks are assigned to pipes, unlike in EPANET, where leaks are modeled by assigning emitter coefficients to junctions.
Issue -
State: closed - Opened by andreArtelt about 2 months ago
- 2 comments
#12 - Modeling of water distribution networks -> Topology: in the definition of a pump, how do you define "segment?" I would add that pumps add hydraulic head to the system or something to that extent
Issue -
State: closed - Opened by andreArtelt about 2 months ago
- 2 comments
#11 - Scenarios -> Basics: what happens if you don't close the scenario?
Issue -
State: closed - Opened by andreArtelt about 2 months ago
- 2 comments
#10 - JOSS Review
Issue -
State: closed - Opened by kbonney 2 months ago
- 14 comments
#9 - JOSS Review
Issue -
State: closed - Opened by meghnathomas 3 months ago
- 20 comments
#8 - geodataframes objects
Issue -
State: closed - Opened by jorgelcq 6 months ago
- 3 comments
#7 - ScadaDataXlsxExport - export functions - If I want to see also the raw data? not only sensor readings?
Issue -
State: closed - Opened by Mariosmsk 9 months ago
- 3 comments
Labels: enhancement
#7 - ScadaDataXlsxExport - export functions - If I want to see also the raw data? not only sensor readings?
Issue -
State: closed - Opened by Mariosmsk 9 months ago
- 3 comments
Labels: enhancement
#6 - Sometimes I have the error below - self.__find_temporary_file()
Issue -
State: closed - Opened by Mariosmsk 9 months ago
- 5 comments
Labels: bug
#5 - WaterDistributionNetworkScenarioSimulator change to `Simulator` or `ScenarioSimulator` or `FlowSimulator`
Issue -
State: closed - Opened by Mariosmsk 9 months ago
- 1 comment
Labels: enhancement
#4 - Improve how we retrieve sensor readings over the entire simulation
Issue -
State: closed - Opened by Mariosmsk 9 months ago
- 3 comments
Labels: enhancement
#3 - Add new specific functions for each sensor type
Issue -
State: closed - Opened by Mariosmsk 9 months ago
- 1 comment
Labels: enhancement
#2 - Create action - `draft-pdf.yml`
Issue -
State: closed - Opened by Mariosmsk 9 months ago
Labels: enhancement
#1 - Create actions for build - `build_tests.yml`
Issue -
State: closed - Opened by Mariosmsk 9 months ago
Labels: enhancement