{"action":"created","issue":{"url":"https://api.github.com/repos/CalTRACK-2/caltrack/issues/71","repository_url":"https://api.github.com/repos/CalTRACK-2/caltrack","labels_url":"https://api.github.com/repos/CalTRACK-2/caltrack/issues/71/labels{/name}","comments_url":"https://api.github.com/repos/CalTRACK-2/caltrack/issues/71/comments","events_url":"https://api.github.com/repos/CalTRACK-2/caltrack/issues/71/events","html_url":"https://github.com/CalTRACK-2/caltrack/issues/71","id":293489456,"number":71,"title":"Building qualification using baseline model fit","user":{"login":"hshaban","id":13769526,"avatar_url":"https://avatars2.githubusercontent.com/u/13769526?v=4","gravatar_id":"","url":"https://api.github.com/users/hshaban","html_url":"https://github.com/hshaban","followers_url":"https://api.github.com/users/hshaban/followers","following_url":"https://api.github.com/users/hshaban/following{/other_user}","gists_url":"https://api.github.com/users/hshaban/gists{/gist_id}","starred_url":"https://api.github.com/users/hshaban/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hshaban/subscriptions","organizations_url":"https://api.github.com/users/hshaban/orgs","repos_url":"https://api.github.com/users/hshaban/repos","events_url":"https://api.github.com/users/hshaban/events{/privacy}","received_events_url":"https://api.github.com/users/hshaban/received_events","type":"User","site_admin":false},"labels":[{"id":853057243,"url":"https://api.github.com/repos/CalTRACK-2/caltrack/labels/building-qualification","name":"building-qualification","color":"020987","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":32,"created_at":"2018-02-01T11:07:11Z","updated_at":"2018-03-28T21:38:43Z","closed_at":null,"author_association":"COLLABORATOR","body":"Buildings with usage patterns that are not correctly captured using Caltrack models end up with low signal-to-noise ratio, poor model fits and tend to default to the intercept-only model. These buildings are not suitable for Caltrack/regression modeling and are recommended to be handled using alternate methods.\r\n\r\nWe propose the following:\r\n1. Identify metrics to determine the suitability of the Caltrack baseline model for calculating payable savings.\r\n2. Variance of monthly or daily usage on intercept-only models relative to mean usage be used to judge the quality of intercept-only models (in lieu of R-squared)"},"comment":{"url":"https://api.github.com/repos/CalTRACK-2/caltrack/issues/comments/377046102","html_url":"https://github.com/CalTRACK-2/caltrack/issues/71#issuecomment-377046102","issue_url":"https://api.github.com/repos/CalTRACK-2/caltrack/issues/71","id":377046102,"user":{"login":"mcgeeyoung","id":4206880,"avatar_url":"https://avatars1.githubusercontent.com/u/4206880?v=4","gravatar_id":"","url":"https://api.github.com/users/mcgeeyoung","html_url":"https://github.com/mcgeeyoung","followers_url":"https://api.github.com/users/mcgeeyoung/followers","following_url":"https://api.github.com/users/mcgeeyoung/following{/other_user}","gists_url":"https://api.github.com/users/mcgeeyoung/gists{/gist_id}","starred_url":"https://api.github.com/users/mcgeeyoung/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mcgeeyoung/subscriptions","organizations_url":"https://api.github.com/users/mcgeeyoung/orgs","repos_url":"https://api.github.com/users/mcgeeyoung/repos","events_url":"https://api.github.com/users/mcgeeyoung/events{/privacy}","received_events_url":"https://api.github.com/users/mcgeeyoung/received_events","type":"User","site_admin":false},"created_at":"2018-03-28T21:38:43Z","updated_at":"2018-03-28T21:38:43Z","author_association":"CONTRIBUTOR","body":"I think we all kind of want the same thing here. Consistency, improvement, specificity. At a general level, CalTRACK creates consistency; the CalTRACK process allows for ongoing improvement; the testing and discussion around the methods creates the specificity. I would hope that as we make progress, we continually reflect on our basic assumptions and adapt them. For example, monthly methods started out with a fixed balance point temperature. Now we're agreed to allow for a search grid. The evidence points to this being an improvement in the quality of the savings calculation. And if someone is following the methods specified by CalTRACK 2.0 for analyzing billing data, we can be confident that they are following the temperature set point rules, which where the specificity comes in. I know it's a bit frustrating to be working in such an incremental fashion, but in the long run we will really benefit from being so diligent."}}
{"actor":{"display_login":"mcgeeyoung"}}