972184 radiant surf temp humidity control

Code for surface temperature control of radiant systems and humidity based (dew point temperature) control of zone outside air systems working; needs testing
Note: the build tests are "failing" because of differences in the err files not the eso/csv files according to the build log.  Not sure why that is happening or how to fix this easily.
Mike:

Yuck…well, those “changes” were not intended at all.  The only changes should have been to the zone outdoor air unit (new humidity control) and the radiant systems (new surface temperature control).  Everything else was an accidental change coming from the use of MS Word for Mac.  So, all of those changes should be “reject” or taken back to what it was.

Edwin:

Is there any “easy” way to scale this back a version without having to do this manually for each of these occurrences?  If not, how do I download a “previous” version of a file so that it can get put back to what it was?

Thanks—and sorry again for the problems.  I will make sure to use a plain text editor in the past as using Word on the Mac seems to be a real issue.

Rick


On Nov 26, 2014, at 10:59 AM, Michael J. Witte <notifications@github.com> wrote:

> In idd/Energy+.idd.in:
> 
> > @@ -663,15 +663,15 @@ ZoneAirMassFlowConservation,
> >         \key No
> >         \default No
> >         \note This optional choice input field allows users triggering the zone air mass flow
> > -       \note balance calculation when desired. This global object has two choice KEYs: �Yes� and
> > -       \note �No�. If this input field is specified as �Yes�, then EnergyPlus attempts to enforce
> > -       \note the zone air mass flow conservation, or else if it is specified as �No�, then EnergyPlus
> @Myoldmopar @RKStrand Would prefer to see these replaced by standard apostrophe and quote characters rather than lost. Except we should probably change the field names for Young's Modulus and Poisson's Ratio to not have an apostrophe - that means a doc change as well.
> 
> —
> Reply to this email directly or view it on GitHub.
>