While "Weekday and weekend hourly time patterns for Dry Weather inflows are now correctly applied in a mutually exclusive manner" was implemented for version 5.1.001, the user interface still indicates that inflow is the product of the average times all the patterns. This should be revised to match the engine methodology and with the User's Manual, which states that "The number and meaning of the multipliers changes with the type of time pattern selected" and that weekend patterns are the "Same as for HOURLY except applied to weekend days." The "Time Patterns" page in the GUI Help file is ambiguous, indicating that Weekend patterns are "hourly multipliers for weekend days", while the Time Pattern Editor page indicates "Same as for HOURLY except applied for weekend days."
N.B. I usually recommend building models that use HOURLY patterns but omit DAILY and WEEKEND patterns. I find that these patterns add minimal value for models' expected uses.
While "Weekday and weekend hourly time patterns for Dry Weather inflows are now correctly applied in a mutually exclusive manner" was implemented for version 5.1.001, the user interface still indicates that inflow is the product of the average times all the patterns. This should be revised to match the engine methodology and with the User's Manual, which states that "The number and meaning of the multipliers changes with the type of time pattern selected" and that weekend patterns are the "Same as for HOURLY except applied to weekend days." The "Time Patterns" page in the GUI Help file is ambiguous, indicating that Weekend patterns are "hourly multipliers for weekend days", while the Time Pattern Editor page indicates "Same as for HOURLY except applied for weekend days."
N.B. I usually recommend building models that use HOURLY patterns but omit DAILY and WEEKEND patterns. I find that these patterns add minimal value for models' expected uses.