Reverse Translator - Remove remaining UIDs

[GoogleCodeExporter]

Describe the translation issue or enhancement:
The EPlus IDFs generated for from CBECC runs include UIDs in a few areas.  
Please see preliminary list below.  THis issue is for tracking progress on 
eliminating these UIDs so CBECC generated IDFs do not have them.

- ZoneHVAC:EquipmentConnections
- ZoneHVAC:AirDistributionUnit
- NodeList
- Schedule:Week:Daily schedule names for the following schedules:
     Default "Always On"
     HVAC constant setpoint schedules
- ScheduleTypeLimits for what looks like all schedules
- AirLoopHVAC:ControllerList
- AvailabilityManagerAssignmentList
- AirLoopHVAC:OutdoorAirSystem:EquipmentList
- OutdoorAir:Mixer
- AirLoopHVAC:SupplyPath
- AirLoopHVAC:ReturnPath
- Misc node names of plant loops
- SetpointManager:Scheduled
- New materials created by OS in reverse translation.  Fixing this is already 
covered under issue 400.

Please provide any additional information below.

Original issue reported on code.google.com by da...@360-analytics.com on 15 Mar 2014 at 1:45

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I think I have these covered:

- ZoneHVAC:EquipmentConnections
- ZoneHVAC:AirDistributionUnit
- NodeList
- AirLoopHVAC:ControllerList
- AvailabilityManagerAssignmentList
- AirLoopHVAC:OutdoorAirSystem:EquipmentList
- OutdoorAir:Mixer
- AirLoopHVAC:SupplyPath
- AirLoopHVAC:ReturnPath
- SetpointManager:Scheduled

Need more time for these:

- Misc node names of plant loops
- Schedule:Week:Daily schedule names for the following schedules:
     Default "Always On"
     HVAC constant setpoint schedules
- ScheduleTypeLimits for what looks like all schedules

Original comment by kbe...@gmail.com on 12 Apr 2014 at 3:44

[GoogleCodeExporter]

Thanks Kyle, these updates help.

One that missed my original list:
ZoneHVAC:EquipmentConnections, including it's Zone Air Node Name

Also, for the nodes that specify specific points in the system that we have 
added for debugging:
Output:Variable,*,System Node Temperature, 
Output:Variable,*,System Node Mass Flow Rate

it would be really helpful for navigatng the results files if they inherited 
names of the system, such as:
AirSys/ZnSys:Name&" SA Node"
AirSys/ZnSys:Name&" RA Node"
AirSys/ZnSys:Name&" MA Node"

Am I getting too greedy with the requests. Changing this to low priority for 
now, but will keep it on the radar for the the next round.

Original comment by da...@360-analytics.com on 14 Apr 2014 at 6:24

• Changed state: Discussion
• Added labels: Priority-Low
• Removed labels: Priority-High

[GoogleCodeExporter]

Well these are things that everyone wants.  The changes I made so far are 
appreciated by all consumers of OS.  I will keep chipping away at these.

Original comment by kbe...@gmail.com on 14 Apr 2014 at 6:27

[GoogleCodeExporter]

https://github.com/NREL/OpenStudio/commit/2f86595a9cfb0c521c3c878f19f9af39e4ae83
02

Original comment by kbe...@gmail.com on 8 Jul 2014 at 6:11

[GoogleCodeExporter]

Hi Kyle,
The node naming strategy is a big improvement.  However, there are some names 
of a few key nodes that are a bit misleading that I am hoping we can revise:

AirLoopHVAC
!- Supply Side Inlet Node Name = <AirLoopHVAC:Name> + "Supply Side (Return Air) 
Inlet Node"
!- Demand Side inlet Node Name = <AirLoopHVAC:Name> + "Demand Side (Supply Air) 
Inlet Node"

Finally, there are few other remaining UIDs found in these objects. These are 
the higher priority items:
ZoneHVAC:EquipmentList
ZoneHVAC:EquipmentConnections

The following are low priority: 
AvailabilityManager:Scheduled
ScheduleTypeLimits
Schedule:Day:Interval
Schedule:Week:Daily
Branchs/BranchLists

Original comment by da...@360-analytics.com on 20 Jul 2014 at 10:25

[GoogleCodeExporter]

https://github.com/NREL/OpenStudio/commit/e9bfd3bfc1bf11ec6ed6e7981c8aa4969ea5a4
88

Original comment by kbe...@gmail.com on 25 Jul 2014 at 9:07