Question-and-Answer Resource for the Building Energy Modeling Community
 | 1 | initial version |
The measure crashes here, as it's trying to access an uninitialized variable. The measure does log 2 prior messages: one error (dark red), one warning (pinkish). Both messages are reporting that the measure is unable to locate the meter "Electricty:HVAC". Double-check the OSM?
Should the measure crash this way? IMHO, no: it should have returned false right after logging the first error message. I would label this as a minor bug, but it doesn't change the fact that it's unable to locate the requested meter. There are safer ways around this, such as offering users a drop-down list of available meters found in the OSM file, but that's another topic.
| | 2 | No.2 Revision |
The measure crashes here, as it's trying to access an uninitialized variable. The measure does log 2 relevant prior messages: one error (dark red), (in dark red in the screenshot), one warning (pinkish). Both messages are reporting that the measure is unable to locate the meter "Electricty:HVAC". Double-check the OSM?
Should the measure crash this way? IMHO, no: it should have returned false right after logging the first error message. I would label this as a minor bug, but it doesn't change the fact that it's unable to locate the requested meter. There are safer ways around this, such as offering users a drop-down list of available meters found in the OSM file, but that's another topic.
| | 3 | No.3 Revision |
The measure crashes here, as it's trying to access an uninitialized variable. The measure does does however log 2 prior messages that are relevant prior messages: here: one error (in dark red in the screenshot), one warning (pinkish). Both messages are reporting that the measure is unable to locate the meter "Electricty:HVACElectricity:HVAC". Double-check the OSM?
Should the measure crash this way? IMHO, no: it should have returned false right after logging the first error message. message (which forces the measure to stop without crashing). I would label this as a minor bug, but it doesn't change the fact that it's the measure remains unable to locate the requested meter. There are safer ways around this, such as offering users a drop-down list of available meters actually found in the OSM file, but that's another topic.
| | 4 | No.4 Revision |
The measure crashes here, as it's trying to access an uninitialized variable. The measure does however log 2 prior messages that are relevant here: one error (in dark red in the screenshot), one warning (pinkish). Both messages are reporting that the measure is unable to locate the meter "Electricity:HVAC". Double-check the OSM?
Should the measure crash this way? IMHO, no: it should have returned false right (right after logging the first error message (which forces message), forcing the measure to stop safely exit without crashing). crashing. I would label this as a minor frontend bug, but it doesn't change the fact that the measure remains unable to locate the requested meter. There are safer ways around this, such as offering users a drop-down list of available meters actually found in the OSM file, but that's another topic.
