{"action":"closed","issue":{"url":"https://api.github.com/repos/UCL/STIR/issues/7","labels_url":"https://api.github.com/repos/UCL/STIR/issues/7/labels{/name}","comments_url":"https://api.github.com/repos/UCL/STIR/issues/7/comments","events_url":"https://api.github.com/repos/UCL/STIR/issues/7/events","html_url":"https://github.com/UCL/STIR/issues/7","id":120015006,"number":7,"title":"Wierd order of 3d values in python","user":{"login":"adler-j","id":2202312,"avatar_url":"https://avatars.githubusercontent.com/u/2202312?v=3","gravatar_id":"","url":"https://api.github.com/users/adler-j","html_url":"https://github.com/adler-j","followers_url":"https://api.github.com/users/adler-j/followers","following_url":"https://api.github.com/users/adler-j/following{/other_user}","gists_url":"https://api.github.com/users/adler-j/gists{/gist_id}","starred_url":"https://api.github.com/users/adler-j/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/adler-j/subscriptions","organizations_url":"https://api.github.com/users/adler-j/orgs","repos_url":"https://api.github.com/users/adler-j/repos","events_url":"https://api.github.com/users/adler-j/events{/privacy}","received_events_url":"https://api.github.com/users/adler-j/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-12-02T19:15:51Z","updated_at":"2015-12-02T19:48:25Z","closed_at":"2015-12-02T19:48:25Z","body":"When creating a `FloatVoxelsOnCartesianGrid` with [this](https://github.com/odlgroup/odl/blob/67087d232b238a0a4dbee0e8ad03b631faaf4fbc/examples/tomo/data/stir/initial.hv) input file, we get\r\n\r\n```python\r\n>>> volume = stir.FloatVoxelsOnCartesianGrid.read_from_file('initial.hv')\r\n>>> volume.shape()\r\n(15, 64, 64)\r\n```\r\n\r\nBut the file says that the shape should be `x = 64`, `y = 64`, `z = 15`.\r\n\r\nSome testing shows that almost all STIR methods give the results in [z, y, x] order. Is this intended?"}}