{"action":"created","issue":{"url":"https://api.github.com/repos/stnava/ANTsR/issues/75","labels_url":"https://api.github.com/repos/stnava/ANTsR/issues/75/labels{/name}","comments_url":"https://api.github.com/repos/stnava/ANTsR/issues/75/comments","events_url":"https://api.github.com/repos/stnava/ANTsR/issues/75/events","html_url":"https://github.com/stnava/ANTsR/issues/75","id":128701914,"number":75,"title":"dynamic radius in mrvnrf?","user":{"login":"dorianps","id":9083517,"avatar_url":"https://avatars.githubusercontent.com/u/9083517?v=3","gravatar_id":"","url":"https://api.github.com/users/dorianps","html_url":"https://github.com/dorianps","followers_url":"https://api.github.com/users/dorianps/followers","following_url":"https://api.github.com/users/dorianps/following{/other_user}","gists_url":"https://api.github.com/users/dorianps/gists{/gist_id}","starred_url":"https://api.github.com/users/dorianps/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dorianps/subscriptions","organizations_url":"https://api.github.com/users/dorianps/orgs","repos_url":"https://api.github.com/users/dorianps/repos","events_url":"https://api.github.com/users/dorianps/events{/privacy}","received_events_url":"https://api.github.com/users/dorianps/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-01-26T02:20:36Z","updated_at":"2016-01-26T13:35:37Z","closed_at":null,"body":"I want to propose an idea for mrvnrfs. Specifically, allowing dynamic radius neighborhood for each layer. For example, train RFs at one resolution with rad=2, and at the next resolution with rad=1. This would also allow for running same resolution but with different radiuses, e.g., mr=c(1,1) ) rad=c(2,1).\r\n\r\nThis is rather easy to implement. Question is, what do you think it is worth it?\r\n\r\nAlso, I want to remove the current request for radius to have the dimensions of the image, and have a single number indicating omnidirectional neighborhood. For example, rad=1 should mean, of course, radius=c(1,1,1) for 3D images.\r\n\r\nIn sum, the new radius parameter is a vector the same length as resolutions, not the same length of dimensions. This would mean that existing scripts will not work (although I can adapt it as a new parameter and play inside to see which parameter was selected by the user).\r\n\r\nI think this is a worth change if not many people have started using mrvnrfs (I know only me and Brian).\r\n\r\nQuestion 2: @stnava do you think running mrvnrfs with a final layer with radius=0 can bring something good? I.e. mr=c(6,4,2,1,1) with radiuses=c(1,1,1,1,0). This means the last RF has no neighborhood information, the voxel would still be strongly influenced by the features carried over from previous steps, but without the strong neighborhood information, perhaps allowing more small spatial deviations of a lesion prediction."},"comment":{"url":"https://api.github.com/repos/stnava/ANTsR/issues/comments/175014676","html_url":"https://github.com/stnava/ANTsR/issues/75#issuecomment-175014676","issue_url":"https://api.github.com/repos/stnava/ANTsR/issues/75","id":175014676,"user":{"login":"stnava","id":324222,"avatar_url":"https://avatars.githubusercontent.com/u/324222?v=3","gravatar_id":"","url":"https://api.github.com/users/stnava","html_url":"https://github.com/stnava","followers_url":"https://api.github.com/users/stnava/followers","following_url":"https://api.github.com/users/stnava/following{/other_user}","gists_url":"https://api.github.com/users/stnava/gists{/gist_id}","starred_url":"https://api.github.com/users/stnava/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/stnava/subscriptions","organizations_url":"https://api.github.com/users/stnava/orgs","repos_url":"https://api.github.com/users/stnava/repos","events_url":"https://api.github.com/users/stnava/events{/privacy}","received_events_url":"https://api.github.com/users/stnava/received_events","type":"User","site_admin":false},"created_at":"2016-01-26T13:35:37Z","updated_at":"2016-01-26T13:35:37Z","body":"the ability to have a non-uniform radius i.e. ` rad=c(1,1,0) ` is valuable because of the commonality of anisotropic images.\r\n\r\nyour idea could be implemented in a  backward-compatible way but it would add some complexity to the code.   in general, it's not a good idea to replace valuable functionality with functionality that has no clear benefit.\r\n\r\nre: Q2 - worth testing empirically but i do not think the accuracy of \"ground truth\" data would be able to measure any change in performance.\r\n\r\nyou can test both ideas empirically to see if they help/matter."}}