Extra singlezone SPM humidity min created if humidifier downstream of fan

[asparke2]

If you have the configuration below, where you have a humidifier downstream of a fan, and therefore a humidity control SPM on the supply outlet node, the SPM magic creates an unnecessary clone of the humidity SPM on the upstream side of the humidifier. @KaiyuSun found this configuration in the outpatient reference building.

I think the current workarounds are either to move the humidifier upstream of the fan, or to manually specify the SPMs so the magic doesn't happen.

Here's the example OSM:
spm_humidity_minimum.osm.txt

[jmarrec]

This happens here:

OpenStudio/src/energyplus/ForwardTranslator/ForwardTranslateAirLoopHVAC.cpp

Lines 195 to 204 in 7cec475

	for (auto& lowerNode : lowerNodes) {
	std::vector<SetpointManager> _setpointManagers = lowerNode.setpointManagers();
	if (std::find_if(_setpointManagers.begin(), _setpointManagers.end(), isTemperatureControl) == _setpointManagers.end()) {
	for (auto _setpointManager : _supplyOutletSetpointManagers) {
	SetpointManager spmClone = _setpointManager.clone(t_model).cast<SetpointManager>();
	spmClone.addToNode(lowerNode);
	spmClone.setName(lowerNode.name().get() + " OS Default SPM");
	}
	}
	}

I'm not 100% sure what's safe/recommended here. Currently it clones ALL SPMs that are on the supplyOutlet Node to add it to any node downstream of fan that does not have a temperature SPM already.

1. Only clone the Temperature ones?
2. Keep cloning all?

I'm leaning towards 1. https://bigladdersoftware.com/epx/docs/9-5/input-output-reference/group-setpoint-managers.html#setpointmanagersinglezonehumidityminimum

The calculated supply air humidity ratio is then used as the setpoint for the designated setpoint node. A humidifier component placed upstream of the setpoint node can then use the humidity ratio setpoint to control its moisture addition rate