{"action":"created","issue":{"url":"https://api.github.com/repos/mostaphaRoudsari/Honeybee/issues/400","labels_url":"https://api.github.com/repos/mostaphaRoudsari/Honeybee/issues/400/labels{/name}","comments_url":"https://api.github.com/repos/mostaphaRoudsari/Honeybee/issues/400/comments","events_url":"https://api.github.com/repos/mostaphaRoudsari/Honeybee/issues/400/events","html_url":"https://github.com/mostaphaRoudsari/Honeybee/issues/400","id":114633704,"number":400,"title":"OpenStudio HVAC system 5 ","user":{"login":"antonszilasi","id":8773483,"avatar_url":"https://avatars.githubusercontent.com/u/8773483?v=3","gravatar_id":"","url":"https://api.github.com/users/antonszilasi","html_url":"https://github.com/antonszilasi","followers_url":"https://api.github.com/users/antonszilasi/followers","following_url":"https://api.github.com/users/antonszilasi/following{/other_user}","gists_url":"https://api.github.com/users/antonszilasi/gists{/gist_id}","starred_url":"https://api.github.com/users/antonszilasi/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/antonszilasi/subscriptions","organizations_url":"https://api.github.com/users/antonszilasi/orgs","repos_url":"https://api.github.com/users/antonszilasi/repos","events_url":"https://api.github.com/users/antonszilasi/events{/privacy}","received_events_url":"https://api.github.com/users/antonszilasi/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-11-02T16:41:36Z","updated_at":"2015-11-02T23:02:48Z","closed_at":"2015-11-02T23:02:48Z","body":"@chiensiTB  @chriswmackey \r\n\r\nWhen I am setting HVAC system 5. I am getting the error that the coolingairflow is not defined in the dictonary HVACdetails, please see the file I sent to you by email. (Cant attach GH files here)\r\n\r\n\r\nCan I also ask why is System 5 the only system that has this key in the dictionary along with 'heatingAirflow',and 'floatingAirflow'."},"comment":{"url":"https://api.github.com/repos/mostaphaRoudsari/Honeybee/issues/comments/153186174","html_url":"https://github.com/mostaphaRoudsari/Honeybee/issues/400#issuecomment-153186174","issue_url":"https://api.github.com/repos/mostaphaRoudsari/Honeybee/issues/400","id":153186174,"user":{"login":"chriswmackey","id":5567574,"avatar_url":"https://avatars.githubusercontent.com/u/5567574?v=3","gravatar_id":"","url":"https://api.github.com/users/chriswmackey","html_url":"https://github.com/chriswmackey","followers_url":"https://api.github.com/users/chriswmackey/followers","following_url":"https://api.github.com/users/chriswmackey/following{/other_user}","gists_url":"https://api.github.com/users/chriswmackey/gists{/gist_id}","starred_url":"https://api.github.com/users/chriswmackey/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/chriswmackey/subscriptions","organizations_url":"https://api.github.com/users/chriswmackey/orgs","repos_url":"https://api.github.com/users/chriswmackey/repos","events_url":"https://api.github.com/users/chriswmackey/events{/privacy}","received_events_url":"https://api.github.com/users/chriswmackey/received_events","type":"User","site_admin":false},"created_at":"2015-11-02T23:02:48Z","updated_at":"2015-11-02T23:02:48Z","body":"@antonszilasi ,\r\n\r\nThis is my fault.  Since we are now assigning these flow rates on the zone level (as opposed to the system level), there is no longer a need for these flow rates in the HVAC dictionary.  I switched this over for the other systems but forgot to do so for system 5.  This is fixed in this commit:\r\nhttps://github.com/mostaphaRoudsari/Honeybee/commit/cea133d6656f7fed74c065eed4092df4c4ec273a\r\n\r\n@chiensiTB was absolutely right that we need to do some general thinking about the issues and organization before doing any implementation of all the systems.  For example right now, there are 3 different places where you assign HVAC availability - on the \"Set Zone Schedules\" component, the AHU component, and the availability manager.  I know that we put each one of these in for ease of access but it makes it really confusing for the user to not have a consistent way of doing this.  We need to really understand what the best way to do this is before diving into code editing (or at least focus our efforts on making one common system good and then apply that template to the others).\r\n\r\n-Chris"}}