OS Workflow should not request outputs, especially timestep, by default

[shorowit]

Enhancement Request

By default, an OpenStudio workflow will request a variety of monthly and, worse, timestep/daily outputs. For users that care about runtime speed or file size, this is problematic. Why does OpenStudio assume everyone wants these outputs? If certain reports or workflows or applications need these outputs, they can easily request them.

(Technically these can be skipped by using the skip_energyplus_preprocess option, but that's not easy to know and many end users may not have access to this option with how they are running simulations. And this option might do more than just skip these outputs, I'm not sure.)

Issue originally raised on Unmet Hours.

[jmarrec]

I don't really know, this was already in workflow-gem, I just ported it.

My money is on the fact that this was added for the openstudio_results measure (and maybe the Output:Table:Monthly so that the E+ html output is more useful too).

@DavidGoldwasser could we ensure these are ported to the openstudio_results measure instead of always added by the Workflow?

[DavidGoldwasser]

That makes sense. I think when that code was added pre-dated reporting measures and it was more hard coded in OS App. We should be able to add what we want to the EnergyPlus output request section of OpenStudio results measure. Will have to check if updates also needed for calibration measures and measures in URBANopt.