{"action":"opened","issue":{"url":"https://api.github.com/repos/thunder-project/thunder/issues/358","repository_url":"https://api.github.com/repos/thunder-project/thunder","labels_url":"https://api.github.com/repos/thunder-project/thunder/issues/358/labels{/name}","comments_url":"https://api.github.com/repos/thunder-project/thunder/issues/358/comments","events_url":"https://api.github.com/repos/thunder-project/thunder/issues/358/events","html_url":"https://github.com/thunder-project/thunder/issues/358","id":174076826,"number":358,"title":"Slow saving/loading of binary files","user":{"login":"boazmohar","id":9434009,"avatar_url":"https://avatars.githubusercontent.com/u/9434009?v=3","gravatar_id":"","url":"https://api.github.com/users/boazmohar","html_url":"https://github.com/boazmohar","followers_url":"https://api.github.com/users/boazmohar/followers","following_url":"https://api.github.com/users/boazmohar/following{/other_user}","gists_url":"https://api.github.com/users/boazmohar/gists{/gist_id}","starred_url":"https://api.github.com/users/boazmohar/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/boazmohar/subscriptions","organizations_url":"https://api.github.com/users/boazmohar/orgs","repos_url":"https://api.github.com/users/boazmohar/repos","events_url":"https://api.github.com/users/boazmohar/events{/privacy}","received_events_url":"https://api.github.com/users/boazmohar/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-08-30T17:23:14Z","updated_at":"2016-08-30T17:23:14Z","closed_at":null,"body":"We are dealing with a long but small volumetric data set (~50k-100k time points, ~200Kb per time point).\r\nCurrently saving this `images` object using `tobinary()` produces a large number of small files, which is slow to read, write and especially delete using our storage back-end.\r\nI suggest to add a parameter that would group `n` time points in order to reduce the number of files written to disk.\r\nA few points to think about are:\r\n\r\n1. What grouping to use: would a list work or we will need to stack the n dimensional data in the n+1 dimension. \r\n2. What would be the equivalent series implementation: a grouping factor for each axis?\r\n3. How to retrieve the original `images` or `series` object: change the `conf.json` file to include this parameter, have a similar parameter in `frombinary()`, maybe both.\r\n\r\n@freeman-lab, @jwittenbach would like to hear what you think before starting to play around with this.\r\n"}}
{"actor":{"display_login":"boazmohar"}}