Closed jamie-carter closed 2 years ago
Fixed in NSPECT/QNSPECT dle_work branch, commit 5f7b0b83f8cf0a6b848898ce2fe0b7e837fee745
@NSPECT @DaveEslinger
The initial thought behind calling it Desired Outputs
was that it has runoff output as well which is not a pollutant? Are we fine with calling it Desired Pollutant
despite that?
We can make it non-optional to make it more clear that is required.
We definitely need to make it more apparent that this is where one specifies the desired pollutants. You may recall that, like Jamie, I missed it my first several times running the tool and had to ask when the pollutant aspects would be implemented.
I think calling it pollutants and making it non-optional will help. Maybe change the label to "Define runoff and pollutant outputs" and remove the optional setting. I'm also not too concerned about having runoff listed and calling it a pollutant.
We definitely need to make it more apparent that this is where one specifies the desired pollutants. You may recall that, like Jamie, I missed it my first several times running the tool and had to ask when the pollutant aspects would be implemented.
I think calling it pollutants and making it non-optional will help. Maybe change the label to "Define runoff and pollutant outputs" and remove the optional setting. I'm also not too concerned about having runoff listed and calling it a pollutant.
Sounds good. Can you change the optional to False
and make the name change here as well
I can't contribute to NSPECT/dev branch directly.
Latest QNSPECT version
Similar requests do not exist
Feature description
Let’s change the name for the “Desired Outputs [optional]” group in the Run Pollution Analysis tool to something like “Pollutant Outputs [optional]”. This is really what people are looking to generate, and I totally missed it the first few times trying to run the tool. If possible, it would be good to make it very clear what this is, and that it must be selected in order to generate outputs.
Additional context
No response