performance curve object in OS

asked 2016-01-26 09:51:03 -0500

ngkhanh
2156 ●1 ●3 ●12

updated 2016-01-26 15:14:26 -0500

__AmirRoth__

4436 ●5 ●17 http://bleedinggreenna...

Hello, i try to use a create measure with a set defined performance curve. I want to use that set for many equipment in multi zones. so i create performance cure object as @@cooling_performance_curve and the loop over all zone and create new coil use same @@cooling_performance_curve in each zone. When i try it, it seems no problem , i get run and get result. I even get to change vaule in OS instead of measure. but there is strange problem: After one or two days, when i reopen it, it the performance cure was disappear and OSM file get fault when i try to re run it. Must i create one dedicated performance curve object for each new coil cooling object ?

answered 2016-01-26 10:30:03 -0500

ericringold

10552 ●31 ●8 https://www.nrel.gov/b...

updated 2016-01-26 11:49:09 -0500

Yes, prior to the 1.10.2 release, an individual curve object must be created for each HVAC component that references it. This is because curves inherit from ModelObjects, and are 'children' of the HVAC component (see the 'Relationships' section here), rather than inheriting from ResourceObjects, which can be defined once and referenced by other objects in the model.

This has been changed to redefine curves as ResourceObjects as of version 1.10.2. Thanks, @Kyle Benne!

edit flag offensive delete link

Comments

that work is done. It is in the 1.10.2 iteration package.

Kyle Benne ( 2016-01-26 11:29:37 -0500 )edit

Hi @Kyle Benne : It's really cool to have performance curve as resources. But the default performance curve come when we add equipment should be removed when equipments or all equipments using them get deleted. Otherwise, we will have tons of unused performance curve except we use measure to create equipment. Hope to see your good development

ngkhanh ( 2016-01-27 14:08:52 -0500 )edit

I am acutely aware of this situation. I'm probably over sharing here, but I was actually against curve as resource for this reason. But the users, and my fellow developers spoke loudly so we moved forward with it. See my comments on the PR that brought this feature in. We are probably going to need to do some kind of purge. It can be expensive to do that purge too often, so if we do some automated purging it is going to take some thought.

Kyle Benne ( 2016-01-27 14:30:51 -0500 )edit

add a comment

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.