{"action":"created","issue":{"url":"https://api.github.com/repos/numenta/nupic/issues/2802","labels_url":"https://api.github.com/repos/numenta/nupic/issues/2802/labels{/name}","comments_url":"https://api.github.com/repos/numenta/nupic/issues/2802/comments","events_url":"https://api.github.com/repos/numenta/nupic/issues/2802/events","html_url":"https://github.com/numenta/nupic/issues/2802","id":121262941,"number":2802,"title":"AnomalyScore and multiStepPredictions.N in OPF do not have correct (strict) data type (can be None)","user":{"login":"breznak","id":2166111,"avatar_url":"https://avatars.githubusercontent.com/u/2166111?v=3","gravatar_id":"","url":"https://api.github.com/users/breznak","html_url":"https://github.com/breznak","followers_url":"https://api.github.com/users/breznak/followers","following_url":"https://api.github.com/users/breznak/following{/other_user}","gists_url":"https://api.github.com/users/breznak/gists{/gist_id}","starred_url":"https://api.github.com/users/breznak/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/breznak/subscriptions","organizations_url":"https://api.github.com/users/breznak/orgs","repos_url":"https://api.github.com/users/breznak/repos","events_url":"https://api.github.com/users/breznak/events{/privacy}","received_events_url":"https://api.github.com/users/breznak/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/numenta/nupic/labels/subject:opf","name":"subject:opf","color":"c7def8"},{"url":"https://api.github.com/repos/numenta/nupic/labels/type:bug","name":"type:bug","color":"fc2929"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-12-09T14:56:32Z","updated_at":"2015-12-14T23:18:03Z","closed_at":null,"body":"* `anomalyScore` is defined as a float in range [0..1], while in OPF results file it has type \"string\" (because a few 1st values can be `None`)\r\n* that is because `(multistep)prediction models` predict the 1st N values as `None`, instead of desired data type again. \r\n\r\nThis could be easily fixed, anomalyScore should be `0.5` during burn-in, predictions could be eg `0.0`. \r\nThat is a more correct approach, supports strict typing, and some applications could be easier. \r\n\r\nOur simple use-case is in https://github.com/nupic-community/nupic.visualizations/issues/30 \r\n"},"comment":{"url":"https://api.github.com/repos/numenta/nupic/issues/comments/164591241","html_url":"https://github.com/numenta/nupic/issues/2802#issuecomment-164591241","issue_url":"https://api.github.com/repos/numenta/nupic/issues/2802","id":164591241,"user":{"login":"rhyolight","id":15566,"avatar_url":"https://avatars.githubusercontent.com/u/15566?v=3","gravatar_id":"","url":"https://api.github.com/users/rhyolight","html_url":"https://github.com/rhyolight","followers_url":"https://api.github.com/users/rhyolight/followers","following_url":"https://api.github.com/users/rhyolight/following{/other_user}","gists_url":"https://api.github.com/users/rhyolight/gists{/gist_id}","starred_url":"https://api.github.com/users/rhyolight/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rhyolight/subscriptions","organizations_url":"https://api.github.com/users/rhyolight/orgs","repos_url":"https://api.github.com/users/rhyolight/repos","events_url":"https://api.github.com/users/rhyolight/events{/privacy}","received_events_url":"https://api.github.com/users/rhyolight/received_events","type":"User","site_admin":false},"created_at":"2015-12-14T23:18:03Z","updated_at":"2015-12-14T23:18:03Z","body":"@subutai @scottpurdy I tend to agree with @breznak here."}}