Error reporting does not capture when a user applies LowTempRad to a non-building:Detailed surface

[BobHenninger]

User has a surface list with sub-surfaces (type door), which he was referencing in his
ZoneHVAC:LowTemperatureRadiant object. The simulation ran without
errors, but no heating of the expected base-surface was happening.
Furthermore, the base-surface had no Construction:InternalSource
construction type (but he had one in another unrelated surface). The
documentation accurately says that ZoneHVAC:LowTemperatureRadiant is
only to be used with base-surfaces (BuildingSurface:Detailed), but
should it not be, it should be captured in the .err file.

MJW response:
That is not good. Thanks for letting us know. I will put this on the issues list to get fixed.

Helpdesk Ticket 9111

User idf file
beheizt.idf

[mjwitte]

Working on addressing this issue. The subsurfaces are heating as expected, and the other surfaces with internal source which are not connected to any equipment are not heated as expected. I am planning to change the documentation to state that door subsurfaces are valid, because it can be useful when only a portion of the floor or ceiling is heated (or cooled).

Asking the user who originated the issue if would be helpful to add warnings for surfaces which have a construction:internalsource that is not attached to any equipment?

[mjwitte]

From the user: . . . had the correct impression that internalsource
could be used in a subsurface. We had a client that made an input
error where it seemed that it was not working. The documentation at
the time suggested that it cannot work, but since our various
communications and numerous test, it works perfectly.

I have noticed that the reverse construction has to also have the
internal source layers, but is obviously not referenced by the
lowtempradiant object, so it won't be helpful to issue a warning for
non-used internalsource in that case.

We mainly use the subsurface to exactly draw out the active areas on
the base surface. It would be nice to have a dedicated object for this
which inherents the construction from the parent base surface as an
alternative option. It would make things less confusing for the enduser.

[mjwitte]

Have tested this with door and internal mass and both work find with internal source. Also tested window and glassdoor and these a caught with an error
** Severe ** Windows are not allowed to have embedded sources/sinks
So, will update I/O Ref to indicate that base surfaces, doors, and internal mass are all valid surface types. Also will update the IDD object-lists accordingly.