Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PMV follow up #8561

Merged
merged 15 commits into from
Mar 1, 2021
Merged

PMV follow up #8561

merged 15 commits into from
Mar 1, 2021

Conversation

xuanluo113
Copy link
Contributor

@xuanluo113 xuanluo113 commented Feb 25, 2021

Pull request overview

This PR fixes several follow up for the PMV Enhancement feature in Issue #8573. Please see the reply below.

  1. Using the new example file 1ZoneUncontrolled_Win_ASH55_Thermal_Comfort with all of the thermal comfort-related schedules blank, This is the err output:
   ** Severe  ** GetInternalHeatGains: People="ZONE ONE PEOPLE", blank Work Efficiency Schedule Name is required for this item.
   ** Severe  ** GetInternalHeatGains: People="ZONE ONE PEOPLE", invalid Clothing Insulation Schedule Name entered=
   ** Severe  ** GetInternalHeatGains: People="ZONE ONE PEOPLE", blank Air Velocity Schedule Name is required for this item.
   ** Severe  ** GetInternalHeatGains: People="ZONE ONE PEOPLE", blank Ankle Level Air Velocity Schedule Name is required for this item.
   **  Fatal  ** GetInternalHeatGains: Errors found in Getting Internal Gains Input, Program Stopped

Nothing in the errors here indicates that these are required for certain thermal comfort models.
1ZoneUncontrolled_Win_ASH55_Thermal_Comfort-blankschedules.idf.txt

Detailed error messages were added.

  1. New example file 1ZoneUncontrolled_Win_ASH55_Thermal_Comfort throws this warning:
   ** Warning ** Ankle draft PPD calculations are only applicable for relative air velocity is below 0.2 m/s,
   **   ~~~   ** and the subject’s metabolic rate and clothing level should be kept below 1.3 met and 0.7 clo.
   **   ~~~   ** PPD at ankle draft will be set to -1.0 if if these conditions are not met.

These limits should be mentioned in the I/O Reference for the ANKLEDRAFTASH55 report option and mentioned again in the description of "Zone Thermal Comfort ASHRAE 55 Ankle Draft PPD". If it's documented, the warning isn't necessary. If you want to keep the warning, it should list the current values of the air velocity, metabolic rate, and clothing level in the first warning, and then generate recurring warnings to count how often this occurs.

The documents were updated, and recurring warnings were also added.

  1. The I/O Reference for People field "Thermal Comfort Model Type" could use more details about the new options. It would be good to reformat this using the description method.
\begin{description}
  \item[OptionA] Stuff about option A.
  \item[OptionB] Stuff about option B
\end{description}

Descritions with items were added to the I/O Reference for People field "Thermal Comfort Model Type".

  1. These new output variables need descriptions in the I/O Ref.
  Zone,Average,Zone Thermal Comfort ASHRAE 55 Elevated Air Speed Cooling Effect {[}C{]}
  Zone,Average,Zone Thermal Comfort ASHRAE 55 Elevated Air Speed Cooling Effect Adjusted PMV {[]}
  Zone,Average,Zone Thermal Comfort ASHRAE 55 Elevated Air Speed Cooling Effect Adjusted PPD {[]}
  Zone,Average,Zone Thermal Comfort ASHRAE 55 Ankle Draft PPD {[]}

Fixed.

  1. Declarations of constants in ThermalComfort.cc (lines 798:814) - can these be constexpr?
    Real64 const CloFac(0.25);

Fixed.

  1. Add a figure explanation to the engineering reference describing the range of ankle draft risk.

Modified in the EngRef.

Pull Request Author

Add to this list or remove from it as applicable. This is a simple templated set of guidelines.

  • Title of PR should be user-synopsis style (clearly understandable in a standalone changelog context)
  • Label the PR with at least one of: Defect, Refactoring, NewFeature, Performance, and/or DoNoPublish
  • Pull requests that impact EnergyPlus code must also include unit tests to cover enhancement or defect repair
  • Author should provide a "walkthrough" of relevant code changes using a GitHub code review comment process
  • If any diffs are expected, author must demonstrate they are justified using plots and descriptions
  • If changes fix a defect, the fix should be demonstrated in plots and descriptions
  • If any defect files are updated to a more recent version, upload new versions here or on DevSupport
  • If IDD requires transition, transition source, rules, ExpandObjects, and IDFs must be updated, and add IDDChange label
  • If structural output changes, add to output rules file and add OutputChange label
  • If adding/removing any LaTeX docs or figures, update that document's CMakeLists file dependencies

Reviewer

This will not be exhaustively relevant to every PR.

  • Perform a Code Review on GitHub
  • If branch is behind develop, merge develop and build locally to check for side effects of the merge
  • If defect, verify by running develop branch and reproducing defect, then running PR and reproducing fix
  • If feature, test running new feature, try creative ways to break it
  • CI status: all green or justified
  • Check that performance is not impacted (CI Linux results include performance check)
  • Run Unit Test(s) locally
  • Check any new function arguments for performance impacts
  • Verify IDF naming conventions and styles, memos and notes and defaults
  • If new idf included, locally check the err file and other outputs

@xuanluo113 xuanluo113 added Defect Includes code to repair a defect in EnergyPlus Documentation Related primarily on the LaTeX-based EnergyPlus documentation labels Feb 25, 2021
@xuanluo113 xuanluo113 added this to the EnergyPlus 9.5.0 milestone Feb 25, 2021
@xuanluo113 xuanluo113 self-assigned this Feb 25, 2021
@xuanluo113 xuanluo113 linked an issue Feb 25, 2021 that may be closed by this pull request
3 tasks
@xuanluo113 xuanluo113 requested a review from mjwitte February 25, 2021 02:06
@xuanluo113
Copy link
Contributor Author

@mjwitte This bug fixing branch is ready for review.

This equation is only applicable for \(v_{r} < 0.2 m/s\) . And the subject’s metabolic rate and clothing level should be kept below 1.3 met and 0.7 clo, respectively. Warnings would be thrown if these conditions are not met.
This equation is only applicable for \(v_{r} < 0.2 m/s\) . And the subject’s metabolic rate and clothing level should be kept below 1.3 met and 0.7 clo, respectively. PPD at ankle draft will be set to -1.0 if if these conditions are not met.

It should be noted that the metrics only measures the predicted percentage dissatisfied on the sensation of draft. PPD_AD levels at various air speeds and thermal sensations are depicted in Figure~\ref{fig:ankle-draft-ppd}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Look here at the files page in the pull request. There are some LaTeX warnings. Another subscript that needs \( ... \).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mjwitte Thanks! Fixed.

@@ -1165,11 +1165,11 @@ \subsubsection{Description of the model and algorithm}\label{description-of-the-

\subsection{ASHRAE 55 Elevated Air Speed Cooling Effect Model}\label{elevated-air-speed-ce-model}

ASHRAE Standard 55-2017 Section 5.3 requires that the Elevated Air Speed Comfort Zone Method be used when average air speed Va is greater than 0.10 m/s. The method provides cooling credit for elevated air velocity in the space. The method can be used to evaluate passive cooling technologies such as natural ventilation, ceiling fan, and portable fan.
ASHRAE Standard 55-2017 Section 5.3 requires that the Elevated Air Speed Comfort Zone Method be used when average air speed \(V_{a}\) is greater than 0.10 m/s. The method provides cooling credit for elevated air velocity in the space. The method can be used to evaluate passive cooling technologies such as natural ventilation, ceiling fan, and portable fan.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very minor question. Here Va is upper case for air speed, but the other air speeds below are all lower-case v. Is that intentional?


\paragraph{Zone Thermal Comfort ASHRAE 55 Elevated Air Speed Cooling Effect Adjusted PMV}\label{zone-thermal-comfort-ashrae55-elevated-air-speed-cooling-effect-adjusted-pmv}

This field is the \"predicted mean vote\" (PMV) calculated using the Fanger PMV model, adjusted by the ASHRAE 55 Elevated Air Speed Cooling Effect. The Cooling Effect adjusted PMV for an environment with elevated average air speed is calculated using the adjusted average air temperature, the adjusted radiant temperature, and still air (0.1 m/s).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

predicted is rendering as p̈redicted . Use the smart-quote characters (see existing entries further up): ``predicted mean vote'' (2 characters before and after). Same problem in the next two descriptions.

ShowContinueError(state,"PPD at ankle draft will be set to -1.0 if if these conditions are not met.");
state.dataThermalComforts->FirstTimeAnkleDraftWarning = false;
if (RelAirVel >= 0.2) {
ShowRecurringWarningErrorAtEnd(state, "Relative air velocity is above 0.2 m/s in Ankle draft PPD calculations. PPD at ankle draft will be set to -1.0.",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for adding these warnings. If I'm following correctly, all of these triggers (air velocity, metabolic rate, and clothing level) are user inputs, correct? So, maybe these warnings aren't so important, because this is likely the user's intent. How about wrapping all of these with if (state.dataGlobal->DisplayExtraWarnings) ? Sorry to keep changing my mind here.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just to be clear, my suggestion is to have one if (state.dataGlobal->DisplayExtraWarnings) statement before line 1215 that skips all three of these warning checks.

@mjwitte mjwitte marked this pull request as ready for review February 26, 2021 18:26
Copy link
Contributor

@mjwitte mjwitte left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@xuanluo113 Doc changes look good. Assuming CI comes back green, this is ready to merge.

@jmythms
Copy link
Contributor

jmythms commented Mar 1, 2021

Tested locally, everything looks good. There will be an .err diff in the upcoming CI result, which is expected due to silencing the warnings. Tried merging latest develop branch to this and built it locally, no conflicts. Thanks @xuanluo113, @mjwitte.

@Myoldmopar

@jmythms jmythms merged commit b9bfac2 into develop Mar 1, 2021
@jmythms jmythms deleted the pmv-follow-up branch March 1, 2021 23:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Defect Includes code to repair a defect in EnergyPlus Documentation Related primarily on the LaTeX-based EnergyPlus documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

PMV Improvements Follow-up
7 participants