{"action":"created","issue":{"url":"https://api.github.com/repos/nexpy/nexpy/issues/95","repository_url":"https://api.github.com/repos/nexpy/nexpy","labels_url":"https://api.github.com/repos/nexpy/nexpy/issues/95/labels{/name}","comments_url":"https://api.github.com/repos/nexpy/nexpy/issues/95/comments","events_url":"https://api.github.com/repos/nexpy/nexpy/issues/95/events","html_url":"https://github.com/nexpy/nexpy/issues/95","id":166826316,"number":95,"title":"projection bug","user":{"login":"jpcastell","id":6791845,"avatar_url":"https://avatars.githubusercontent.com/u/6791845?v=3","gravatar_id":"","url":"https://api.github.com/users/jpcastell","html_url":"https://github.com/jpcastell","followers_url":"https://api.github.com/users/jpcastell/followers","following_url":"https://api.github.com/users/jpcastell/following{/other_user}","gists_url":"https://api.github.com/users/jpcastell/gists{/gist_id}","starred_url":"https://api.github.com/users/jpcastell/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jpcastell/subscriptions","organizations_url":"https://api.github.com/users/jpcastell/orgs","repos_url":"https://api.github.com/users/jpcastell/repos","events_url":"https://api.github.com/users/jpcastell/events{/privacy}","received_events_url":"https://api.github.com/users/jpcastell/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2016-07-21T13:59:34Z","updated_at":"2016-07-29T15:50:02Z","closed_at":null,"body":"When taking a cut from a 2d data set using the projection menu there is a small axis bug.\r\nIn a xy,Counts type plot if you take a slice along x for a particular y you can run into an error.\r\n\r\n\r\nsay you take y[1] and the entire x range.  This works fine.  If you take x[5] to the end; also fine.  \r\nyou get an axis size error when you shorten x from the x[max].  This will still plot however you will not be able to fit the data as len(Counts) no longer equals len(x).\r\n\r\nx will have one extra element causing the fit function to fail.\r\n"},"comment":{"url":"https://api.github.com/repos/nexpy/nexpy/issues/comments/236217526","html_url":"https://github.com/nexpy/nexpy/issues/95#issuecomment-236217526","issue_url":"https://api.github.com/repos/nexpy/nexpy/issues/95","id":236217526,"user":{"login":"rayosborn","id":1193959,"avatar_url":"https://avatars.githubusercontent.com/u/1193959?v=3","gravatar_id":"","url":"https://api.github.com/users/rayosborn","html_url":"https://github.com/rayosborn","followers_url":"https://api.github.com/users/rayosborn/followers","following_url":"https://api.github.com/users/rayosborn/following{/other_user}","gists_url":"https://api.github.com/users/rayosborn/gists{/gist_id}","starred_url":"https://api.github.com/users/rayosborn/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rayosborn/subscriptions","organizations_url":"https://api.github.com/users/rayosborn/orgs","repos_url":"https://api.github.com/users/rayosborn/repos","events_url":"https://api.github.com/users/rayosborn/events{/privacy}","received_events_url":"https://api.github.com/users/rayosborn/received_events","type":"User","site_admin":false},"created_at":"2016-07-29T15:50:02Z","updated_at":"2016-07-29T15:50:02Z","body":"NeXus, and therefore NeXpy, allows axes to be stored as bin boundaries rather than bin centers, i.e., with one more value than the signal array. I believe I have fixed the fit function failure by ensuring that the axes are converted to bin centers when the FitDialog is initiated. What to return from the Projection Menu is more subtle, and I'm still working on that. I think it is appropriate to maintain bin boundaries where possible, because the translation from centers back to boundaries is not necessarily unique. However, the existing Projection Menu wasn't consistent in what it returned, so I am trying to fix that now. Hopefully, there will be a new release soon with both fixes. "}}
{"actor":{"display_login":"rayosborn"}}