right now every quality boundary is initialized as a set point type of source.
It's useful to allow different Epanet source types to be specified. I'm guessing this happens in the input file. And it probably should come with the requirement that any quality boundary be appropriately specified in the input file, else it would generate a toolkit error at simulation time.
right now every quality boundary is initialized as a set point type of source.
It's useful to allow different Epanet source types to be specified. I'm guessing this happens in the input file. And it probably should come with the requirement that any quality boundary be appropriately specified in the input file, else it would generate a toolkit error at simulation time.