-
Notifications
You must be signed in to change notification settings - Fork 389
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
Correction of Defect in Transition Program and Recent Bug Fix #8997
Correction of Defect in Transition Program and Recent Bug Fix #8997
Conversation
Correction to a problem in the transition that caused input files to be truncated inappropriately. Also, included another minor fix from a different defect resolution that got merged into develop already.
@@ -397,7 +397,9 @@ SUBROUTINE CreateNewIDFUsingRules(EndOfFile,DiffOnly,InLfn,AskForInput,InputFile | |||
CALL GetNewObjectDefInIDD(ObjectName,NwNumArgs,NwAorN,NwReqFld,NwObjMinFlds,NwFldNames,NwFldDefaults,NwFldUnits) | |||
nodiff=.false. | |||
OutArgs(1:3)=InArgs(1:3) | |||
CurArgs = CurArgs - 1 | |||
IF (CurArgs == 4) THEN | |||
CurArgs = 3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That looks good! I tested again on both a 4-line case and a 3-line case, it works fine on both cases.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small changes, looks good on paper. When CI comes back green, will merge.
…pTransitionAirLoopHVACOutdoorAirSystem
So, I realized that the transition changes to VCompareGlobalRoutines.f90 in the Space branch broke any transition prior to v9.6 when writing surface objects with grouped veritces (x,y,z on the same idf line) which is just about always. I added a fix to this branch to set the field numbers based on whether the transition version is <9.6. @jcyuan2020 @Myoldmopar I've tested locally, but a few random older transitions should be tested as well as the v9.6 transition to be sure this is all good. |
src/EnergyPlus/SizingManager.cc
Outdated
ReportTemperatureInputError( | ||
state, cCurrentModuleObject, 1, state.dataSize->ZoneSizingInput(ZoneSizIndex).CoolDesTemp, true, ErrorsFound); | ||
state, cCurrentModuleObject, 3, state.dataSize->ZoneSizingInput(ZoneSizIndex).CoolDesTemp, true, ErrorsFound); | ||
state.dataSize->ZoneSizingInput(ZoneSizIndex).HeatDesTemp = state.dataIPShortCut->rNumericArgs(3); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is also been tested to working using a defect file that contains a -20C supply temperature in a Sizing:Zone object.
In a quick summary it is working as expected and fixed the problem well---and actually in this defect file case, even though the Sizing:Zone has an input value of -20C for supply temperature, it should not cause a warning in the defect file as the defect file as the object actually specifies a "temperature difference" method---and this should also add to the point when it is a bug before. After the fix the problem is fixed; and no warning for the defect file on this zone (because it uses the temperature difference method):
A little bit complication about this test file is that with the difference method, the user specified a 11.11C temperature difference in Sizing:Zone and the zone thermostat is set to 2C---this means that the supply is around -9.11. I original thought that this is the reason why the warning is flagged.--but actually it should not be. According to the code's original intention, it should only flag the below zero supply temperature with SupplyAirTemperature
method. Therefore from this point it is also a bug.
I think the new fix nice fixed this and it is now clear that the warning is given only when a below-zero supply air temperature is inputted together with the "SupplyAirTemperature" method. If a user selects the "temperature difference", then even though a negative supply air temperature is inferred from the inputs, it would not (and also probably should not) give a warning.
@mjwitte I will try a few cases on the space-related new transition changes next. |
For the space-related transitions, I tried a few more cases with 9.4 version and it is confirmed working. Without the fix, it will have a long list of warnings complaining the geometry fields in the transition audit file when going to the point from 9.5->9.6---for example, like this:
Now with the fix, the transition results and audit reports will just come out clean:
|
I haven't looked at the diffs, but generally this seems fine. Anything else needed here outside of a bit more testing? |
@Myoldmopar Nothing more that I know of. |
I wouldn't expect any diffs here, so this may need a fresh regression to be sure. |
…ionAirLoopHVACOutdoorAirSystem
Pulled develop in, we'll see how it does |
Obviously CI looks much happier now. I will try to run a test this evening or in the morning and get this in. |
@@ -799,31 +808,32 @@ SUBROUTINE CheckSpecialObjects(DifUnit,ObjectName,CurArgs,OutArgs,FieldNames,Fie | |||
CALL WriteOutIDFLinesAsSingleLine(DifUnit,ObjectName,CurArgs,OutArgs,FieldNames,FieldUnits) | |||
|
|||
CASE('BUILDINGSURFACE:DETAILED') | |||
NVertFieldNum = 10 + SurfaceSpaceFieldShift | |||
IF (MakeUPPERCase(OutArgs(11)) == 'AUTOCALCULATE') THEN |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about this line? "11" has been replaced with NVertFieldNum and line 812 has OutArgs(11). For input files > V9.2 and < V9.6, this would be OutArgs(10), right? So OutArgs(NVertFieldNum) here as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rraustad Good catch. I can fix shortly, or feel free to push a fix yourself.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Try that same file with Number of Vertices = autocalculate.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure, I was just updating an UnmetHours file and saw that. I actually think it was an ill formed input file. I guess I should also open the transitioned file in IDFEditor for this test as well. Can't hurt to check everything we can think of.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Transition worked but opening transitioned file in IDF Editor shows an error.
Here is the transitioned OA Sys object. This is V9.4 -> V9.5.
AirLoopHVAC:OutdoorAirSystem,
Outside Air System, !- Name
Outside Air System Controllers, !- Controller List Name
Outside Air System Equipment, !- Outdoor Air Equipment List Name
Evap Cooler Availability List; !- Availability Manager List Name
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, was using V9.6 IDF Editor.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, the above issue is resolved using V9.5 IDF Editor and the transition above for V9.5 AirLoopHVAC:OutdoorAirSystem is correct.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't think of anything else to test so am committing this change.
…5CleanUpTransitionAirLoopHVACOutdoorAirSystem
@rraustad Anything left to do here? |
Well, I still see the ConvectionAdaptiveSmallOffice issue on this branch. I guess we could assume that is not related and get this merged. |
Pull request overview
NOTE: ENHANCEMENTS MUST FOLLOW A SUBMISSION PROCESS INCLUDING A FEATURE PROPOSAL AND DESIGN DOCUMENT PRIOR TO SUBMITTING CODE
Pull Request Author
Add to this list or remove from it as applicable. This is a simple templated set of guidelines.
Reviewer
This will not be exhaustively relevant to every PR.