-
Notifications
You must be signed in to change notification settings - Fork 176
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
Pollutants can't be attached to direct [INFLOWS] #157
Comments
Clarification - one can add pollutants to [INFLOW] on a node-by-node basis as in the example shown below, but cannot assign it globally, as allowed for groundwater, rainfall/runoff, DWF, and RDII [POLLUTANTS] [INFLOWS] [DWF] |
Can't we use the scaling factor and have many nodes use one pollutograph time series? |
Perhaps my application is esoteric, but I wanted to attach tracers to baseflows specified via the [Inflows] section, as well as to other flow types. For other types, I simply needed to create a pollutant and assign a source concentration of 100 to track flow fractions in the collection system. For inflows, I needed to create a concentration entry for each load point, as shown below. Thus, I didn't need a timeseries, but did need to create an entry for each load point. If no one has complained about the awkwardness of this configuration in the two decades since SWMM5 was released, I suppose it's moot. [INFLOWS] |
Now that you mention it this has been a complaint in other software as well. It would be nicer to have on global concentration applied to the time series like all of the other processes you mentioned |
Pollutants cannot be attached to direct [Inflows], but can be assigned to every other flow source (i.e. rainfall, groundwater, I&I, and DWF)
TracerTest.zip
The text was updated successfully, but these errors were encountered: