Re: [EnergyPlus_Support] Re: Call for IDF Editor Suggestions

On Wed, Apr 27, 2016 at 4:43 PM, Karen Walkerman kwalkerman@xxxxxxxxx [EnergyPlus_Support] <EnergyPlus_Support@xxxxxxxxxxxxxxx> wrote:

Â
Hi Jason,

it would be useful if blank lines in list objects could be automatically ignored when saving and creating the IDF file.Â In the image below, there is a blank line in the "Corridors" Zonelist.

This translates in the text file to:

ZoneList,
Â Â Corridors, Â Â Â Â Â Â Â !- Name
Â Â 1 07 North Entry, Â Â Â Â !- Zone 1 Name
Â Â , Â Â Â Â Â Â Â Â Â Â Â Â !- Zone 2 Name
Â Â 1 11 Elevator, Â Â Â Â Â !- Zone 3 Name
Â Â 1 18 Corridor, Â Â Â Â Â !- Zone 4 Name
Â Â 2 06 Corridor, Â Â Â Â Â !- Zone 5 Name
Â Â 2 14 Corridor, Â Â Â Â Â !- Zone 6 Name
Â Â 1 09 Main Entry; Â Â Â Â !- Zone 7 Name

... and throws an error.Â It would be desirable for the program to simply do the following:

ZoneList,
Â Â Corridors, Â Â Â Â Â Â Â !- Name
Â Â 1 07 North Entry, Â Â Â Â !- Zone 1 Name
Â Â 1 11 Elevator, Â Â Â Â Â !- Zone 2 Name
Â Â 1 18 Corridor, Â Â Â Â Â !- Zone 3 Name
Â Â 2 06 Corridor, Â Â Â Â Â !- Zone 4 Name
Â Â 2 14 Corridor, Â Â Â Â Â !- Zone 5 Name
Â Â 1 09 Main Entry; Â Â Â Â !- Zone 6 Name

This would be useful for pretty much any list-type object, and especially Schedule:Compact.

... and for Schedule:Compact - how about being able to insert a line?

For Schedule:Compact, at least, it might be possible to simply display a textbox type input, instead of a line-by-line input.

All this can be easily done in a text file, but that requires closing, re-opening and interrupts the workflow.

Thanks!

Karen
On Wed, Apr 27, 2016 at 8:59 AM, Jason Glazer jglazer@xxxxxxxx [EnergyPlus_Support] <EnergyPlus_Support@xxxxxxxxxxxxxxx> wrote:
Â
Chandan, Thanks, that is a good suggestion and I added it to the list. https://github.com/NREL/EnergyPlus/issues/5606 Jason
On 4/27/2016 7:16 AM, Chandan Sharma chandangsharma@xxxxxxxxx [EnergyPlus_Support] wrote:

Jason,

If you are still taking inputs, here is one more request. Can IDFEditor sort EMS programs in a different way (the way we actually write IF-ELSE ,nested loops statements etc) than rest of the objects?

For example, if the idf has following EMS program

Â Â IF ABS_QdotReq < ABS_FullTotCapSens, Â !- <none>

Â Â Â Â Â Set PLR = (ABS_QdotReq - FanPowerToAir)/ (ABS_FullTotCapSens - FanPowerToAir), Â !- <none>

Â Â Â Â Â Set ErrorTol = 0.0005, Â !- <none>

Â Â Â Â Â Set Iter = 0, Â Â Â Â Â Â !- <none>

Â Â Â Â Â Set MaxIter = 30, Â Â Â Â !- <none>

Â Â Â Â Â Set Relax = 0.8, Â Â Â Â !- <none>

Â Â Â Â Â Set ABS_Error = 0.002, Â !- <none>

Â Â Â Â Â WHILE (ABS_Error > ErrorTol) && (Iter < MaxIter), Â !- <none>

Â Â Â Â Â Â Â Â Set OutAir_H = (PLR*FullLoadOutAirEnth) + Â ((1.0-PLR)* FanOut_H), Â !- <none>

Â Â Â Â Â Â Â Â Set OutAir_W = (PLR*FullLoadOutAirHumRat) + ((1.0-PLR)*FanOut_W), Â !- <none>

Â Â Â Â Â Â Â Â Set OutletAirTemp = @TdbFnHW OutAir_H OutAir_W, Â !- <none>

Â Â Â Â Â Â Â Â Set TotCapTest = AirSupMdotDesign * (DesiredZone_H - OutAir_H), Â !- <none>

Â Â Â Â Â Â Â Â Set Error = (ABS_QdotReq - TotCapTest)/ABS_QdotReq, Â !- <none>

Â Â Â Â Â Â Â Â Set ABS_Error = @ABS Error, Â !- <none>

Â Â Â Â Â Â Â Â IF (ABS_Error > ErrorTol), Â !- <none>

Â Â Â Â Â Â Â Â Â Â Â Set DelPLR = (ABS_QdotReq - TotCapTest) / ABS_FullTotCapSens, Â !- <none>

Â Â Â Â Â Â Â Â Â Â Â Set PLR = PLR + Relax * DelPLR, Â !- <none>

Â Â Â Â Â Â Â Â Â Â Â Set PLR = @min PLR 1.0, Â !- <none>

Â Â Â Â Â Â Â Â ENDIF, Â Â Â Â Â Â Â Â Â !- <none>

Â Â Â Â Â Â Â Â Set Iter = Iter + 1, Â Â !- <none>

Â Â Â Â Â Â Â Â If (Iter == 16), Â Â Â Â !- <none>

Â Â Â Â Â Â Â Â Â Â Â Set Relax = 0.5, Â Â Â Â !- <none>

Â Â Â Â Â Â Â Â ENDIF, Â Â Â Â Â Â Â Â Â !- <none>

Â Â Â Â Â ENDWHILE, Â Â Â Â Â Â Â Â !- <none>

Â Â ELSE, Â Â Â Â Â Â Â Â Â Â !- <none>

Â Â Â Â Â Set PLR = 1.0, Â Â Â Â Â !- <none>

Â Â Â Â Â Set OutAir_H = FullLoadOutAirEnth, Â !- <none>

Â Â Â Â Â Set OutAir_W = FullLoadOutAirHumRat, Â !- <none>

Â Â Â Â Â Set OutletAirTemp = FullLoadOutAirTemp, Â !- <none>

Â Â ENDIF, Â Â Â Â Â Â Â Â Â !- <none>

after sorting from IDF Editor, it becomes as follows

Â Â IF ABS_QdotReq < ABS_FullTotCapSens, Â !- A68

Â Â Set PLR = (ABS_QdotReq - FanPowerToAir)/ (ABS_FullTotCapSens - FanPowerToAir), Â !- A69

Â Â Set ErrorTol = 0.0005, Â !- A70

Â Â Set Iter = 0, Â Â Â Â Â Â !- A71

Â Â Set MaxIter = 30, Â Â Â Â !- A72

Â Â Set Relax = 0.8, Â Â Â Â !- A73

Â Â Set ABS_Error = 0.002, Â !- A74

Â Â WHILE (ABS_Error > ErrorTol) && (Iter < MaxIter), Â !- A75

Â Â Set OutAir_H = (PLR*FullLoadOutAirEnth) + Â ((1.0-PLR)* FanOut_H), Â !- A76

Â Â Set OutAir_W = (PLR*FullLoadOutAirHumRat) + ((1.0-PLR)*FanOut_W), Â !- A77

Â Â Set OutletAirTemp = @TdbFnHW OutAir_H OutAir_W, Â !- A78

Â Â Set TotCapTest = AirSupMdotDesign * (DesiredZone_H - OutAir_H), Â !- A79

Â Â Set Error = (ABS_QdotReq - TotCapTest)/ABS_QdotReq, Â !- A80

Â Â Set ABS_Error = @ABS Error, Â !- A81

Â Â IF (ABS_Error > ErrorTol), Â !- A82

Â Â Set DelPLR = (ABS_QdotReq - TotCapTest) / ABS_FullTotCapSens, Â !- A83

Â Â Set PLR = PLR + Relax * DelPLR, Â !- A84

Â Â Set PLR = @min PLR 1.0, Â !- A85

Â Â ENDIF, Â Â Â Â Â Â Â Â Â !- A86

Â Â Set Iter = Iter + 1, Â Â !- A87

Â Â If (Iter == 16), Â Â Â Â !- A88

Â Â Set Relax = 0.5, Â Â Â Â !- A89

Â Â ENDIF, Â Â Â Â Â Â Â Â Â !- A90

Â Â ENDWHILE, Â Â Â Â Â Â Â Â !- A91

Â Â ELSE, Â Â Â Â Â Â Â Â Â Â !- A92

Â Â Set PLR = 1.0, Â Â Â Â Â !- A93

Â Â Set OutAir_H = FullLoadOutAirEnth, Â !- A94

Â Â Set OutAir_W = FullLoadOutAirHumRat, Â !- A95

Â Â Set OutletAirTemp = FullLoadOutAirTemp, Â !- A96

Â Â ENDIF, Â Â Â Â Â Â Â Â Â !- A97

Thanks for asking for inputs.

On Tue, Apr 12, 2016 at 9:08 PM, Jason Glazer jglazer@xxxxxxxx [EnergyPlus_Support] <EnergyPlus_Support@xxxxxxxxxxxxxxx> wrote:

Â

Thanks for all the suggestions I received on this thread. I
compiled them here:

https://github.com/NREL/EnergyPlus/issues/5606

Please let me know if you have additional suggestions or
clarifications.

Jason

On 3/31/2016 3:42 PM, Jason Glazer wrote:
> If you use IDF Editor extensively and have ideas on how it
> can be made easier to use please let me know. I am
> especially interested in ideas on how to reduce
> time-consuming repetitive actions that would be simple for
> me to program. Here are the current GitHub issues related
> to IDF Editor:
>
> https://github.com/NREL/EnergyPlus/issues?q=is%3Aopen+is%3Aissue+label%3AIDFEditor
>
>
> Please email me directly and I will compile a list of
> suggestions and post a summary.
>
> Thanks
>
> Jason
>

--
Jason Glazer, P.E., GARD Analytics, 90.1 ECB chair
Admin for onebuilding.org building performance mailing lists

--

Chandan Sharma

Principal,Â Convergent Solutions

LinkedInÂ |Â Website
-- 
Jason Glazer, P.E., GARD Analytics, 90.1 ECB chair
Admin for onebuilding.org building performance mailing lists

James V Dirkes II, PE, BEMP, LEED AP
CEO/President
The Building Performance Team Inc.
1631 Acacia Dr, GR, Mi 49504

Direct: 616.450.8653
jim@xxxxxxxxxxxxxxxxxxxxxxxxxxx

Website l Â LinkedIn

Guitar strings are in constant tension against the guitar's neck during their entire life. The tension doesnâ??t discourage the guitarâ??s neck. Rather, it allows beautiful music to be made. May it be so with our lives and their tensions.