bje- / phpp-issues Goto Github PK
View Code? Open in Web Editor NEWPHPP issue tracker
PHPP issue tracker
The design temperature for the window comfort criterion ('Windows'.BR17) is not documented anywhere that I can see in chapter 17. It should at least be mentioned in section 17.6 (Window surface temperature indicator), I think.
SummVent!AC73 has the cell value formatted to 2 decimal places. The other cells for opening width in the adjacent columns are formatted to 3 decimal places. They should be consistent.
Currently, the Windows worksheet includes various sanity checks, eg. the left frame width plus the right frame width is less than the total window width. If these checks fail, column CG gets the value FALSE
and lots of computations are not performed. Anything like this error that leads to a full calculation not being completed for a given window should produce an error in the Error(s) column.
The auxiliary calculation for shower drain water heat recovery contains an spelling error: Connexion should be Connection in cells E91 and E92. I haven't seen connexion written this way in about 300 years. ;-)
If there are any errors in the Verification sheet, the Check worksheet shows Fehler, not Error(s).
The Climate worksheet includes 17 user-defined locations. The first location is labelled Muster. In the English version of the spreadsheet, it should be Template, I think? Related to issue #2
The manual contains a simple typo: "the minimum temperature is 0oC". The degree symbol is not formatted correctly.
In Chapter 40 (HP worksheet), the manual refers to source and drain temperatures for heat pumps. I wonder if this is a translation error? I would have expected to see reference to the source and sink temperatures.
The first paragraph says, can be calculated with this The following
. It should read can be calculated with this worksheet. The following
.
There are no plausibility checks for the HP
worksheet, but there really should be -- there is a lot of scope for getting things wrong with the unit entries and test points. For example, warnings could be issued for not conforming to the guidelines in Section 40.1 of the PHPP manual:
Section 32.3.7 (Lighting) lists typical luminous efficacy figures for various lamp technologies (incandescent, fluorescent, etc). The LED numbers are much too conservative (75--100). LED lamps and tubes sold at my local hardware shop have an efficacy over 120 lm/W.
The header for Chapter 44 (p. 248) says "Daten" instead of "Data".
The first shading plausibility check reads: is there any horizontal shading for these alignments?
The wording horizontal is confusing and should read horizon. Furthermore, the word alignments could be replaced with orientations.
It should be in English for the English version of PHPP.
In Section 17.6, "If a window has an extreme highly U-value" should read, "If a window has an extremely high U-value".
Chapter 31 (PV) contains an error. It refers to open-circuit current (about halfway down the page). This should be open-circuit voltage. Open circuit current is, by definition, zero!
In the Verification worksheet, cell E82 is not labelled on the worksheet. That cell is named Nachweis_Zertifikats_ID
which gives a clue as to its purpose.
Figure 16 shows the four points of the compass. East is labelled with 'O' from 'Osten', not 'E'.Likewise, 'S-O' should be 'S-E'.
The combo boxes to select the country of the mechanical engineer and certifier are wrong in the Verification
worksheet. Instead, we see:
1-Residential building
2-Non-residential building
and:
1-Standard (only for residential buildings)
2-User determined
respectively.
For more complex lateral reveals (for example, a one-sided reveal due to an adjacent wing wall), it is necessary to calculate the average reveal depth and the average distance to the reveals. It is clearer if these details can be entered as observed from the plans and then the o_reveal
and d_reveal
values calculated. Some hidden columns could be added to PHPP allowing the user to add left and right side reveals explicitly.
For now, I am using a side calculator I developed myself. See https://github.com/bje-/PHPP-issues/raw/master/LateralReveals.ods
The fran pressurization test should be fan pressurization test.
PV inverters may be installed inside the thermal envelope for various reasons (phsyical security, reduced exposure to the harsh elements, ease of monitoring). Even at 97% efficiency, PV inverters emit heat and should be included as an internal heat gain as DHW tanks are.
I would suggest adding a drop down list (1-Inside, 2-Outside) in the PV worksheet under the heading "Further specifications".
The PV worksheet allows a PV system to specify the building element that it is attached to. The worksheet currently calculates the area of the module field and shows the free area on the selected building element. It would be nice if this worksheet could perform a side-calculation for the expected reduction factor due to the PV array so that this can be manually included in the Reduction shading factor column in the Areas worksheet.
The Climate
tab in PHPP 9.6 (EN) includes 17 user-defined locations. By default, the locations are labelled Standort 1
to Standort 16
. In the English version of the spreadsheet, it should be Location
, not Standort
.
Each category of plausibility check on the Check worksheet has a link to the corresponding worksheet (column A). The links are in German and so do not work. For example, the link for "Climate" in Check.A73 is to #Klima.A1
.
On page 176, the manual states that, "The dehumidification output which is not yet covered by the air cooling unit is then met by the dehumidifier". I think it would be clearer if it was referred to as the dehumidification load.
Section 19.1 states, "the indoor air then tends to get to dry". This should read, ".. too dry".
PHPP should warn if any floor areas have the same angle of inclination as the ceiling. If the floor and ceiling have the same inclination angle, PHPP warns in another plausibility check that there is a large difference between the ceiling area and the floor area, but does not directly tell the user why!
One of the columns of the Heat recovery DHW component table appears to be labelled incorrectly as it doesn't make sense: Nominal air flow rate (cell Components!MH13) should just be Nominal flow rate (likewise for the tool tip help for that cell).
This plausibility check is flagged if a glazing U-value less than or equal to 0.5 is entered. There are high performance glazing units with U-values ~0.5 available on the market now and so this warning should perhaps be relaxed a bit. Perhaps use 0.45?
At the end of Section 19.1.2, the word "und" appears instead of "and".
Throughout the manual, the term emission is used where the accurate term in English is emissivity. For example, coefficient of emissivity. Global search and replace required.
There is a sentence on p126 that says,
"Please note, that the air exchange volume Vv
must not necessarily equal the reference volume Vn50
."
I think that Vv
and Vn50
should be swapped around here.
Some of the drop-down lists don't work in PHPP 9.6a, eg: U-Values "Orientation of building element", U-Values "Adjacent to" and Ventilation 'Ventilation type'. This appears to be due to a bug in the Excel importing from an older version of OpenOffice/LibreOffice. Opening the Excel version of PHPP and saving it as an .ods
file using LO version 6.2.0.3 does not have this problem.
Am I right to assume that the .ods
version of PHPP is just loaded into OpenOffice/LibreOffice and saved as an .ods
file"?
The PHI supporting tool for heat pumps is used for, among other things, estimating heating power and COPs for DHW heat pumps, which are often tested with only one test point per EN 16147. In Australia, stand-alone DHW heat pumps are more common because hydronic space heating systems are not common. Hence, it is common to want to enter a DHW heat pump into PHPP.
I would like to suggest that either the EF to COPs
worksheet be adapted into a side calculator for the HP
worksheet, or that a new heat pump unit entry be added at the bottom of the HP
worksheet that only requires the user to enter:
This would be clearer and more convenient than having to use the external tool and copy the table data into one of the custom heat pump unit entries.
The error checking formula in cell Z29 reports missing data if the average ambient temperature is not filled out when I have one indoor DHW tank and an indoor buffer storage tank selected.
The check includes a logical OR on the following conditions:
In the Storage heat losses section, it is possible to designate whether the buffer storage tank is inside or outside the thermal envelope, but the error check does not test this. I suggest that the formula should be changed from P326 > 0
to IF(P326>0,P330=2)
so that the location of the buffer storage tank is taken into account.
The text "tank are define in" is a typo. It should be "tank are defined in".
It is often necessary to define a wall between a heated and an unheated basement as a wall adjacent to temperature zone B, but then add the U*A value for the loss to the ground in the Ground
worksheet as a thermal bridge associated with the basement ceiling. This procedure is documented in the PHPP manual in example 15.6.1. When following this procedure, PHPP complains in the plausibility checks that there is a discrepancy between the total ground area and the total area assigned to temperature zone B in the Areas
sheet.
Jürgen advises that there is a mistake in the plausibility check. Ask me for more details, if required.
The tab "Addl vent" should be in bold on line 4, page 97 like Areas, Windows, Ventilation and Compact. When it is not in bold, it is not clear that it is the name of a worksheet.
"for a Passive House buildings" should read "for Passive House buildings".
The default value for HP!J21
("Selection of heat pump") is in German in the English version of PHPP. It says, "1-Standard Luft/Wasser-Waermepumpe".
The examples in section 15.6 (Example 1, Example 2, Example 3) were very confusing until I realised that Uwand and Awand are the U-value and area of the wall and not the wand. :-) Needs translation!
In the Ground worksheet, cell D33 should have a space between "above" and "ground".
The plausibility check for winter shading (Check.B112) is a warning and an unconditional one. This seems a bit too strict, as it is not testing the values for plausibility before warning. Should it just be informational ("Information:") instead?
Warning: reduction factor for shading in winter: minimum X%, maximal Y%, average Z%
Also, note that maximal is not the right word here, either. It should be maximum.
The drop-down lists for the country in the address of the certifier and the mechanical engineer are both incorrect. The data validation source for the country of the architect, by contrast, is PHPP_Daten_Laender, whereas for the certifier and mechanical engineer, it is shown as PHPP_Daten_Nachweis_Gebaeudetyp and PHPP_Daten_Nachweis_Personenzahl, respectively.
It would be very useful if the Verification worksheet had a free-form field for notes. These could be used by the designer to leave notes for themselves, or notes for the certifier.
Cell M25 of the Verification worksheet contains the following entries in the drop-down list instead of the list of countries:
1-Standard (only for residential buildings)
2-User determined
The PV worksheet requests Imp
and Vmp
but does not state whether these should be under Standard Test Conditions (STC) or Normal Operating Cell Temperature (NOCT). Likewise, the manual could be clearer.
Change
such rooms are have a larger height
to:
such rooms have a greater height (remove are).
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.