2

EnergyPlus version transition

Hi, I am trying to change the version of my Energyplus from V8.5 to 8.6. After changing the version I am facing the following problem. I am wondering if anyone can provide me some suggestions:

C:\fakepath\Error.PNG

Thanks!

mfath's avatar
659
mfath
asked 2018-05-16 10:09:53 -0500
__AmirRoth__'s avatar
4.4k
__AmirRoth__
updated 2018-05-17 07:35:13 -0500
edit flag offensive 0 remove flag close merge delete

Comments

add a comment see more comments

2 Answers

3

From the error message, it looks like you've got an uninitialized EMS variable. You'll need to provide an initialization. Uninitialized variables were previously allowed, but that was changed for version 8.6. Here's the issue that was raised:

https://github.com/NREL/EnergyPlus/is...

And the pull request that made the change is here:

https://github.com/NREL/EnergyPlus/pu...

That link is failing to load for me right now (the dreaded GitHub angry unicorn), but the change is listed in the changelog here. It's listed under "Defects Repaired".

Jason DeGraw's avatar
2.2k
Jason DeGraw
answered 2018-05-16 10:34:53 -0500, updated 2018-05-16 14:18:05 -0500
edit flag offensive 0 remove flag delete link

Comments

I appreciate you help. If I figured that out correctly, I need to add W-AHZONE (which is applied in the program section) to the sensor section? Do you have any suggestion about the

a) Meter Index Key Name c) Meter name

which I need to complete in the sensor section?

mfath's avatar mfath (2018-05-16 16:00:53 -0500) edit

Based upon the naming, that looks like a BEopt EMS program, and in one of the files I have that variable is connected to a "Zone Mean Air Humidity Ratio" sensor in the zone where the duct is. Assuming this is a BEopt file, @shorowit would probably know for sure.

Jason DeGraw's avatar Jason DeGraw (2018-05-16 16:20:45 -0500) edit

@M 108014 If this is a file originally generated from BEopt, it might be easiest to grab the latest version of BEopt and see what the new objects it writes are.

shorowit's avatar shorowit (2018-05-16 16:56:08 -0500) edit
1

Also, if this is a BEopt file, the variable I see in the file I have is AHZONE_W, not W_AHZONE. Is it possible that the name got changed in one place and not the other?

Jason DeGraw's avatar Jason DeGraw (2018-05-16 16:57:54 -0500) edit

I really appreciate all your helps. This file is created originally in BEopt and then the first E+ version that we used for this one was in the version 7 range. Then I changed the version to 8.5 and it worked well. However, when I am changing the version to 8.6, I am facing the aforementioned problem. @Jason DeGraw I also have AHZone_W in my idf. Is that correct to have both?

I checked the W_AHZone and it is only used in the following expression: Set LatentLeakageToAHZone = f_sup * AH_MFR * h_fg * (AH_Wout - W_AHZone)

mfath's avatar mfath (2018-05-16 18:54:02 -0500) edit
add a comment see more comments
1

I changed the W_AHZone to AHZone_W and it worked. The simulation is successful. Thanks @shorowit and @Jason DeGraw. My final goal is to reach v8.9. The simulation is successful with the same approach till 8.8. Bu when I am trying to transit from 8.8 to 8.9, I am getting the following error message before warm up. Could you please also help me with that. I compared the idf of V8.8 and v8.9. Nothing unless the version is different!

C:\fakepath\New Warning.PNG

mfath's avatar
659
mfath
answered 2018-05-16 21:04:09 -0500
edit flag offensive 0 remove flag delete link

Comments

The simulation encountered a fatal error and did not indicate the reason. The "node connection errors not checked" tells you that node connections were not tested yet. So there is no indication of the failure in these messages. The input file is needed in order to diagnose.

rraustad's avatar rraustad (2018-05-17 06:51:20 -0500) edit

This sounds like something different to me, so please create a separate question.

Jason DeGraw's avatar Jason DeGraw (2018-05-17 08:03:15 -0500) edit
add a comment see more comments