-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failing or hanging initialization with DOE reference building #2512
Comments
@kbenne The issue can be isolated to the Spawn binaries. See attached the idf epw and json and let me know if you can reproduce it. RefBldgMediumOfficeNew2004_v1.4_7.2_5A_USA_IL_CHICAGO-OHARE.idf.txt |
It turns out that there are other idf files that cause a crash. For example, model TestModel
extends Buildings.ThermalZones.EnergyPlus.Validation.OutputVariable.OneEnvironmentOutputVariable(
building(
idfName=Modelica.Utilities.Files.loadResource(
"file:////home/mwetter/test/mbl-2512/tmp_idf_files/ASHRAE9012016_OfficeSmall_Denver.idf")));
annotation (
experiment(
StopTime=86400,
Tolerance=1e-06));
end TestModel; causes
Note that the process had to be killed, it did not terminate on its own. In this case, EnergyPlus does not write output files:
The same happens for I will work further on a script that runs all EnergyPlus examples to check for errors. |
So, I've tracked down the issue, and it occurs when there are no You can go around this issue by adding any
Alternatively, any working example models will fail if you remove all
The fact that the error also occurs when the MBL |
@bravache : Thanks for the analysis.
The cases with "fatal error" are likely fine as confirmed by individual inspection of some files. These are typically cases where the idf becomes invalid, possibly because the HVAC system has been removed. |
Reminder: I have highlighted the necessity of having at least a single output variable listed on the idf "file" issue #2088 ,however the issue was closed "premature i guess". See also below the question I asked you and @kbenne 's reply regarding this issue and the comparative analysis I executed in : |
@bravache Thanks! Adding
to the idf solves the issue. |
The "idf preparation" which removes unsupported output variables (in an effort to prevent warnings) was accessing the array of output variables using unchecked methods. Here is the fix. Thank you @Helarga for originally reporting this. I think the reason we didn't reproduce this back when it was first reported, is because it requires both an idf file that does not request output variables, AND a spawn model that does not request output. Spawn will automatically inject output requests that are made from the Modelica side. That is my theory anyway. I'm pretty sure it is squashed now. ref lbl-srg/modelica-buildings#2088 ref lbl-srg/modelica-buildings#2512
* Added script to run all idf files For #2512 * Merge validation case that has no output variables (#2526) * Updated reference results and hash code of Spawn * Renamed E+ working directory to EnergyPlus-simulation * Updated reference results Co-authored-by: bravache <[email protected]>
The following model fails to initialize: Dymola stalls and OCT returns the attached error log.
https://github.com/AntoineGautier/ldrd/blob/master/LDRD/Examples/DebugRefMed.mo
oct.log
The model uses the DOE reference model for medium office at https://www.energy.gov/eere/downloads/reference-buildings-building-type-medium-office. Version v1-4_7-2 was selected and converted (on Windows) to EnergyPlus v9.5. Simulating the model with EnergyPlus v9.5 (on Linux) is successful, see attached error log.
eplusout.err.txt
There is no issue when using another reference building, for instance with the following parameter values in
LDRD.Loads.BaseClasses.BuildingSpawnRefMed1
.The text was updated successfully, but these errors were encountered: