{"action":"created","issue":{"url":"https://api.github.com/repos/ClimbsRocks/auto_ml/issues/247","repository_url":"https://api.github.com/repos/ClimbsRocks/auto_ml","labels_url":"https://api.github.com/repos/ClimbsRocks/auto_ml/issues/247/labels{/name}","comments_url":"https://api.github.com/repos/ClimbsRocks/auto_ml/issues/247/comments","events_url":"https://api.github.com/repos/ClimbsRocks/auto_ml/issues/247/events","html_url":"https://github.com/ClimbsRocks/auto_ml/issues/247","id":236641069,"number":247,"title":"create feature_responses only for the top 100 features","user":{"login":"ClimbsRocks","id":7017045,"avatar_url":"https://avatars3.githubusercontent.com/u/7017045?v=3","gravatar_id":"","url":"https://api.github.com/users/ClimbsRocks","html_url":"https://github.com/ClimbsRocks","followers_url":"https://api.github.com/users/ClimbsRocks/followers","following_url":"https://api.github.com/users/ClimbsRocks/following{/other_user}","gists_url":"https://api.github.com/users/ClimbsRocks/gists{/gist_id}","starred_url":"https://api.github.com/users/ClimbsRocks/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ClimbsRocks/subscriptions","organizations_url":"https://api.github.com/users/ClimbsRocks/orgs","repos_url":"https://api.github.com/users/ClimbsRocks/repos","events_url":"https://api.github.com/users/ClimbsRocks/events{/privacy}","received_events_url":"https://api.github.com/users/ClimbsRocks/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-06-17T05:44:50Z","updated_at":"2017-06-25T16:58:42Z","closed_at":null,"body":"hmmmm... this becomes difficult for deep learning, where we don't even know which features are the top ones..."},"comment":{"url":"https://api.github.com/repos/ClimbsRocks/auto_ml/issues/comments/310914302","html_url":"https://github.com/ClimbsRocks/auto_ml/issues/247#issuecomment-310914302","issue_url":"https://api.github.com/repos/ClimbsRocks/auto_ml/issues/247","id":310914302,"user":{"login":"ClimbsRocks","id":7017045,"avatar_url":"https://avatars3.githubusercontent.com/u/7017045?v=3","gravatar_id":"","url":"https://api.github.com/users/ClimbsRocks","html_url":"https://github.com/ClimbsRocks","followers_url":"https://api.github.com/users/ClimbsRocks/followers","following_url":"https://api.github.com/users/ClimbsRocks/following{/other_user}","gists_url":"https://api.github.com/users/ClimbsRocks/gists{/gist_id}","starred_url":"https://api.github.com/users/ClimbsRocks/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ClimbsRocks/subscriptions","organizations_url":"https://api.github.com/users/ClimbsRocks/orgs","repos_url":"https://api.github.com/users/ClimbsRocks/repos","events_url":"https://api.github.com/users/ClimbsRocks/events{/privacy}","received_events_url":"https://api.github.com/users/ClimbsRocks/received_events","type":"User","site_admin":false},"created_at":"2017-06-25T16:58:42Z","updated_at":"2017-06-25T16:58:42Z","body":"For deep learning, i think we'll probably still create feature_responses for everything. \r\nlonger-term, we can certainly modify this. in fact, i think we've already defaulted to cutting the number of rows we use for deep learning by 75%. \r\n\r\nfor other algorithms:\r\nwe'll need to move where we calculate the feature responses\r\nwhile still having the fallback that works for deep learning, and other models we don't have other analytics for\r\n\r\n"}}
{"actor":{"display_login":"ClimbsRocks"}}