Austin Gerlt

> @anderscmathisen, feel free to question my comments. > > From [#400 (comment)](https://github.com/pyxem/orix/discussions/400#discussioncomment-3826033): > > > This would be a super helpful function for me as well, as parent/child orientation...

> I'm happy with this PR now, great work @anderscmathisen! > > Before merging, I'd like to wait for @harripj or @argerlt to give their take on my question at...

hmmmmm......... I didn't know about this. I might try wrapping a part of this into a generator. My fear is that drastic changes are going to break some part of...

I believe codecov costs money, whereas coveralls is free as long as the repo is public. Other than that though, I believe they are functionally identical. (as in, if there...

> Codecov is actually free for open source projects. Oh, Neat, I'll try that then. It makes more sense to fit to what you are used to than what I...

Coming back to this after a long break. Quick recap: 1) Long vertical Class dependencies relying on function overwrites can make code break easily. 2) Cannot to the MTEX-style `o1*o2=m12`...

Sort of. I actually sidestepped the problem after posting this in 2022, but I came up with a better solution just now. I'll list both here. Quick background first though,...

Coming back to this after a break. As part of this and as a precursor to #345, and #254, best path forward seems to be to add the following jit-accelerated...

Just a comment on this: > they plot filled hexagons and calculate the verticies for each. So if you have 1e6 datapoints, you have to draw 6e6 verticies, many of...

(continuing the conversation from #392) @hakonanes you are right, this is close to what I was wanting to do with spatial decomp. Only difference is I planned on storing feature...