Results 18 issues of Phillip

With #469 coming in and fixing an important bug with significant downstream (--> diffsims --> pyxem) implication it seems likely we will need a new release of orix. Given what's...

dev

A couple of things jump out 1) How we handle the direct beam - One option would be to assign a fixed proportion of the total intensity (say 50%) into...

**Checklist** - [x] implementation steps - [ ] update the Changelog - [ ] mark as ready for review Another one from the broader discussion in #996, these are fairly...

status: stalled

`pxyem 0.13.0-rc.1.dev #(from pip)` It's not currently clear to me why this is.

Hello, apologies for my absence, it sounds like things went well at NTNU. I've got a little bit of time over the coming weeks so I'm going to go back...

dev

v0.20.0 would mainly serve to make use of the fact that with #1103 & orix v0.13.1 (orix-base) we would (in theory) be numpy 2.0.0 compatible. This would help our install...

dev

Related to #1098 At present, pyxem has too many dependencies that will not play nicely with numpy 2. In the short term I think we should pin ourselves to 1.x...

discussion
dev

Building on the thoughts expressed in by @CSSFrancis in https://github.com/pyxem/pyxem/issues/1106#issuecomment-2324717110 Having two, similar, but no identical sets of "Tutorials" creates a lot of maintenance issues for a basically unstaffed team....

dev