{"action":"closed","issue":{"url":"https://api.github.com/repos/CalTRACK-2/caltrack/issues/80","repository_url":"https://api.github.com/repos/CalTRACK-2/caltrack","labels_url":"https://api.github.com/repos/CalTRACK-2/caltrack/issues/80/labels{/name}","comments_url":"https://api.github.com/repos/CalTRACK-2/caltrack/issues/80/comments","events_url":"https://api.github.com/repos/CalTRACK-2/caltrack/issues/80/events","html_url":"https://github.com/CalTRACK-2/caltrack/issues/80","id":297208894,"node_id":"MDU6SXNzdWUyOTcyMDg4OTQ=","number":80,"title":"Better specificity in data sufficiency requirements documentation.","user":{"login":"philngo","id":2687443,"node_id":"MDQ6VXNlcjI2ODc0NDM=","avatar_url":"https://avatars1.githubusercontent.com/u/2687443?v=4","gravatar_id":"","url":"https://api.github.com/users/philngo","html_url":"https://github.com/philngo","followers_url":"https://api.github.com/users/philngo/followers","following_url":"https://api.github.com/users/philngo/following{/other_user}","gists_url":"https://api.github.com/users/philngo/gists{/gist_id}","starred_url":"https://api.github.com/users/philngo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/philngo/subscriptions","organizations_url":"https://api.github.com/users/philngo/orgs","repos_url":"https://api.github.com/users/philngo/repos","events_url":"https://api.github.com/users/philngo/events{/privacy}","received_events_url":"https://api.github.com/users/philngo/received_events","type":"User","site_admin":false},"labels":[{"id":837536929,"node_id":"MDU6TGFiZWw4Mzc1MzY5Mjk=","url":"https://api.github.com/repos/CalTRACK-2/caltrack/labels/documentation-update","name":"documentation-update","color":"abffa0","default":false}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-02-14T19:02:08Z","updated_at":"2018-07-26T16:12:54Z","closed_at":"2018-07-26T16:12:54Z","author_association":"CONTRIBUTOR","body":"In the monthly methods, the checks for sufficiency in the reporting period should only apply to annualized/weather normalized methods, and not to methods which use reporting period estimated or actual use. Stated another way, you should not need to know anything about the reporting period to fit a baseline model. The checks for sufficiency in the reporting period are of course necessary for annualized/weather normalized methods, because these methods also require fitting a reporting period model.\r\n\r\nMy suggestion is separately address baseline period data sufficiency and reporting period data sufficiency, then indicate carefully which methods require a baseline model only, or a baseline model and a reporting period model. I think this was the intention, but the docs are written in an ambiguous way."}}
{"actor":{"display_login":"hshaban"}}