Output cannot be found in CSV

edit

@Manny, there are 13 Output:Variable requests in the IDF you shared. But as a few are redundant entries, there are really only 10 unique requests:

Output:Variable,
    *,                       !- Key Value
    Zone Thermal Comfort Fanger Model PMV,  !- Variable Name
    hourly,                  !- Reporting Frequency
    Always On Discrete;      !- Schedule Name

Output:Variable,
    *,                       !- Key Value
    Zone Thermal Comfort Fanger Model PPD,  !- Variable Name
    hourly,                  !- Reporting Frequency
    Always On Discrete;      !- Schedule Name

Output:Variable,
    *,                       !- Key Value
    Zone Heating Electricity Energy,  !- Variable Name
    hourly,                  !- Reporting Frequency
    Always On Discrete;      !- Schedule Name

Output:Variable,
    *,                       !- Key Value
    Zone Cooling Electricity Energy,  !- Variable Name
    hourly,                  !- Reporting Frequency
    Always On Discrete;      !- Schedule Name

Output:Variable,
    *,                       !- Key Value
    InteriorLights:Electricity,  !- Variable Name
    hourly,                  !- Reporting Frequency
    Always On Discrete;      !- Schedule Name

Output:Variable,
    RefPoint_Center,         !- Key Value
    Daylighting Reference Point 1 Illuminance,  !- Variable Name
    Hourly,                  !- Reporting Frequency
    Always On Discrete;      !- Schedule Name

Output:Variable,
    *,                       !- Key Value
    Facility Total Purchased Electric Energy,  !- Variable Name
    hourly;                  !- Reporting Frequency

Output:Variable,
    *,                       !- Key Value
    Facility Total Purchased Gas Energy,  !- Variable Name
    hourly;                  !- Reporting Frequency

Output:Variable,
    *, Lights Electric Energy, Hourly;

Output:Variable,
    *, Zone Lights Illuminance at Reference Point, Hourly;

The IDF also hold 8 Output:Meter requests - some are also redundant (e.g. 3 separate "Electricity:Facility" requests). In the end, the following 4 variables/meters are successfully being reported in the eplusout.eso file:

• Zone Thermal Comfort Fanger Model PMV
• Zone Thermal Comfort Fanger Model PPD
• Electricity:Facility
• InteriorLights:Electricity

The reported "Electricity:Facility" and "InteriorLights:Electricity" are in fact Output:Meter instances - not Output:Variable instances. For instance, there are 2 "InteriorLights:Electricity" entries in the IDF:

• 1x Output:Variable
• 1x Output:Meter

In the end, it's the Output:Meter "InteriorLights:Electricity" that's being reported in the ESO file - not the Output:Variable of the same name. Search the eplusout.err file for remaining (failed) ones, e.g.:

The following Report Variables were requested but not generated -- check.rdd file
Either the IDF did not contain these elements, the variable name is misspelled, or the
requested variable is an advanced output which requires
Output : Diagnostics, DisplayAdvancedReportVariables;
   ************* Key=*, VarName=ZONE HEATING ELECTRICITY ENERGY, Frequency=Hourly
   ************* Key=*, VarName=ZONE COOLING ELECTRICITY ENERGY, Frequency=Hourly
   etc.

Heating & Cooling: The single zone in the model ("Thermal Zone 1") is served by an IdealLoadsAirSystem. As such, there is neither electric heating nor electric cooling energy use in your model. With ideal loads, zone heating and cooling requirements are instead reported as District Heating and District Cooling (see "end uses" in the eplustbl.htm file). Search the generated eplusout.rdd file for:

• Zone Ideal Loads Zone Total Heating Energy
• Zone Ideal Loads Zone Total Cooling Energy

... probably pick these instead.

Daylighting: I simply replaced "RefPoint_Center" with an " * ". Now getting realistic numbers in the eplusout.eso file. The eplusout.err holds additional warnings on daylighting parameters - these should help in pinpointing underlying issues with your model vis-à-vis daylighting.

EDIT

Utility Costs: Hadn't taken a deeper dive on the Utility:Cost issues, as reported in the generated eplusout.err file ... (more)