Question-and-Answer Resource for the Building Energy Modeling Community
Get started with the Help page
Ask Your Question

How to use BEopt idf output in E+?

asked 2020-05-25 16:26:01 -0600

steppmay's avatar

updated 2020-05-26 16:31:09 -0600

Hello, I would like to use the E+ idf file generated by BEopt to run simulations directly in E+. However, even after updating the IDF file to the most current version, E+ comes up with >40 errors trying to simulate it. How can I use the BEopt output file in E+ without the errors? -Stepp

Errors: Program Version,EnergyPlus, Version 9.3.0-baff08990c, YMD=2020.05.26 14:0

There are a multiple errors with format: * Warning * Meter:Custom="HEATING:GAS_1", no items assigned * ~~~ * ...will not be shown with the Meter results. This may be caused by a Meter:Custom be assigned to another Meter:Custom.

There are also multiple errors with format: * Warning * Output:Meter: invalid Key Name="HEATING:ELECTRICITY_1" - not found.

There is a fatal error: * Fatal * UpdateMeterReporting: Previous Meter Specification errors cause program termination. ...Summary of Errors that led to program termination: ..... Reference severe error count=1 ..... Last severe error=GetStandardMeterResourceType: Illegal OutResourceType (for Meters) Entered=FUELOILNO1

Error Message in Entirety:

Program Version,EnergyPlus, Version 9.3.0-baff08990c, YMD=2020.05.26 14:00

** Warning ** Sizing:Parameters: note Timesteps in Averaging Window entered value=[1] is less than 1 hour (i.e., 6 timesteps).

** Warning ** ManageSizing: For a zone sizing run, there must be at least 1 Sizing:Zone input object. SimulationControl Zone Sizing option ignored.

************* Beginning Plant Sizing Calculations

** Warning ** Weather file location will be used rather than entered (IDF) Location object.

** ~~~ ** ..Location object=LOS ANGELES INTL ARPT CA

** ~~~ ** ..Weather File Location=Los Angeles Intl Arpt CA USA TMY3 WMO#=722950

** ~~~ ** ..due to location differences, Latitude difference=[0.00] degrees, Longitude difference=[0.00] degrees.

** ~~~ ** ..Time Zone difference=[1.0] hour(s), Elevation difference=[3.20E-006] percent, [9.60E-007] meters.

** Warning ** ProcessScheduleInput: Schedule:File="CLOTHESWASHER_1" 51880 records had errors - these values are set to 0.

** ~~~ ** Use Output:Diagnostics,DisplayExtraWarnings; to see individual records in error.

** Warning ** ProcessScheduleInput: Schedule:File="DISHWASHER_1" 51729 records had errors - these values are set to 0.

** ~~~ ** Use Output:Diagnostics,DisplayExtraWarnings; to see individual records in error.

** Warning ** ProcessScheduleInput: Schedule:File="SHOWERS_1" 51587 records had errors - these values are set to 0.

** ~~~ ** Use Output:Diagnostics,DisplayExtraWarnings; to see individual records in error.

** Warning ** ProcessScheduleInput: Schedule:File="SINKS_1" 45293 records had errors - these values are set to 0.

** ~~~ ** Use Output:Diagnostics,DisplayExtraWarnings; to see individual records in error.

** Warning ** No floor exists in Zone="DUMMY", zone floor area is zero. All values for this zone that are entered per floor area will be zero.

** Warning ** CalculateZoneVolume: 2 zones are not fully enclosed. For more details use: Output:Diagnostics,DisplayExtrawarnings;

** Warning ** CheckUsedConstructions: There are 14 nominally unused constructions in input.

** ~~~ ** For explicit details on each unused construction, use Output:Diagnostics,DisplayExtraWarnings;

** Warning ** The Standard Ratings is calculated for Coil:Cooling:DX:SingleSpeed = DX COOLING COIL_1 but not at the AHRI test condition due to curve out of bound.

** ~~~ ** Review the Standard Ratings calculations in the Engineering Reference for this coil type. Also, use Output:Diagnostics, DisplayExtraWarnings for further guidance.

** Warning ** Check input. Pump nominal power ... (more)

edit retag flag offensive close merge delete


Can you edit your question to include the error messages?

shorowit's avatar shorowit  ( 2020-05-26 12:47:53 -0600 )edit

Updated with full error message.

steppmay's avatar steppmay  ( 2020-05-26 16:12:58 -0600 )edit

3 Answers

Sort by ยป oldest newest most voted

answered 2020-05-28 12:31:45 -0600

EBEdwards's avatar


I am far from an expert in either EnergyPlus or BEopt, but I did take a stab at trying to compare internal BEopt results with an identical* EnergyPlus-native IDF. You may already know that BEopt v2.0 generates E+ v8.0 IDFs. I found that these will run in E+ v8.0 with no problems. BEopt v2.8 generates E+ v8.8 IDFs. There appears to be considerably more pre-processing and a more customized implementation of the E+ engine. The BEopt-generated v8.8 IDFs would not run in E+ v8.8 for me. Your upconversion to E+ v9.x likely carried that incompatibility forward. Depending on your objective, you might make your base model in BEopt v2.0 and convert the v8.0 IDF to the current E+ version. From my experience, the geometry, assemblies, equipment, and BEopt defaults would carry forward and have basic functionality.

I realize this solution requires you to repeat some work, and you should test with a basic model to see if you get acceptable results, but it might be a workaround until someone with more knowledge can weigh in. Good luck!


*My investigations were comparing the PNNL single-family prototype model to an equally-specified BEopt model in both v2.0/8.0 and v2.8/8.8. We found dramatically different end uses and performance trends, even attempting to change/align with NREL's default schedules and equipment assumptions. Check other posts here to get a better understanding of the challenges when converting HVAC systems into or out of E+; it isn't straightforward.

edit flag offensive delete link more


Ben, Thank you, this is very helpful and good to know. It's a pity that new versions of BEopt are not creating EnergyPlus compatible IDFs, as that capacity is crucial when running large numbers of simulations. Different end use breakdowns between E+ and BEopt are also very concerning as this is one of the more useful components of these programs. Thanks again for the help! -Stepp

steppmay's avatar steppmay  ( 2020-05-29 15:49:36 -0600 )edit

answered 2020-05-26 16:50:17 -0600

It's possible there is a bug in the EnergyPlus version translation program. In the meantime, you can open up the IDF and replace "FuelOilNo1" with "FuelOil#1" in any Output:Meter objects.

edit flag offensive delete link more


Thanks for the help! I will give this a try.

steppmay's avatar steppmay  ( 2020-05-27 15:48:10 -0600 )edit

Hi again,

After making the replacement suggested, I got the following error message:

[Meter:Custom][FuelOil:Unit_1][fuel_type] - "FuelOil#1" - Failed to match against any enum values.

Any idea what's going on here?


steppmay's avatar steppmay  ( 2020-05-27 15:55:28 -0600 )edit

Looks like this was indeed a bug in EnergyPlus:

shorowit's avatar shorowit  ( 2020-07-02 15:47:28 -0600 )edit

answered 2020-06-09 17:34:05 -0600

Jyothis's avatar

updated 2020-06-09 17:35:38 -0600

Valid fuel types used in energyplus are Electricity, NaturalGas, Propane, FuelOilNo1, FuelOilNo2, Diesel, Gasoline, Coal, Steam, DistrictHeating, District-Cooling, OtherFuel1, and OtherFuel2.

However, using FuelOilNo1, FuelOilNo2 leads to severe/fatal error. But the other fuel types are working perfectly, as far as I know. So use other fuel types instead of FuelOilNo1., if the use of FuelOilNo1 is not critical.

For example: Under Meter:Custom change "FuelOil#1" or "FuelOilNo1" with "OtherFuel1".

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer


Question Tools

1 follower


Asked: 2020-05-25 16:26:01 -0600

Seen: 454 times

Last updated: Jun 09 '20