-
Notifications
You must be signed in to change notification settings - Fork 161
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
Failed to find variable AFlo in EnergyPlus.fmu #3945
Comments
When simulating an EnergyPlus model with the Spawn coupling, EnergyPlus will create an
If you unzip this file, you can see the You could also simulate the model with the debug flag set in |
Hi @mwetter , Thanks so much for getting back to me. My .fmu file currently does not seem to be able to unzip. I have seen online that adding a certain .reg file to the Windows Registry Editor fixes this issue, but importing the .reg file to the Registry Editor requires elevated admin rights. Do you know if there is another way to unzip the FMU without adding a new .reg file to the Registry Editor? |
That I don't know, that is a Windows issue. On Linux or OS X you can simply unzip the fmu as it is a zip file. Perhaps you need to change the extension do this on Windows? |
Hi @mwetter , A few updates and more questions: First, I was able to figure out the first issue. I embarrassingly was not typing the Zone name correctly into the Zone model, which was causing the error. Additionally, I found that the software 7 zip was able to unzip the FMU. Second, I am back to being unable to simulate the model but with a different error. The error is coming from the
I compared the Thanks again. |
@kbenne : Do you have some insight into the reported issue above regarding the SpaceList? |
I'm sorry, Spawn does not support EnergyPlus Space. At least not yet. Perhaps this is a feature we should discuss moving forward. |
Okay. Thanks for the help!
|
Hi @kbenne , this might be more of an EnergyPlus issue, but per your answer I am trying to get rid of all EnergyPlus Spaces in my model so I can run it in Spawn. I cannot figure out how to get rid of them while keeping the model's geometry information. I am using OpenStudio and FloorplanJS, but creating and modifying geometries seem to require space definitions. Do you know how I can avoid defining spaces but still define building geometries? And how did you create your EnergyPlus models for the Spawn examples in the MBL library? Thanks so much. |
Hi Spawn and MBL developers,
I am trying to run the
Buildings.ThermalZones.EnergyPlus_9_6_0.Examples.SingleFamilyHouse.Unconditioned
model (which I have duplicated and renamed tomyUnconditioned
) with my own .idf file. I have chosen to simulate the zone GYM ZONE, one of four zones in my EnergyPlus model. I keep getting the following error message saying that the variable AFlo (the floor area of the zone) cannot be found. I have compared the example MBL idf file with my idf file for inconsistencies and still can't find the source of the error. I originally expected the error to be that I hadn't defined the floor area in my EP model, but the MBL idf file actually has blank inputs for Floor Area (Thermal Zones and Surfaces:Zone:Floor Area). I tested my idf file with blanks and 'autocalculate' in the Floor Area field, but got the same error. I also tried to trace where the model was reading Aflo from, and found a comment saying it was reading it from a modelDescription.xml file. However, I cannot find this file in the folder the Spawn model generates (spawn-myUnconditioned) or the EnergyPlus outputs that I run independently (and which simulate successfully).My questions are: do you know where I can specify the floor area so that Spawn recognizes it? And are there any fields that must always be filled in an idf file for Spawn to simulate?
Both idf files are version 9.6.0. I am running Dymola v2023 with Modelica Buildings Library v10.0.0. I am using Windows 11.
Thank you so much. I would appreciate any insight.
Note: I have removed the full path from the error message.
The text was updated successfully, but these errors were encountered: