Implement texture components (in Elasticipy)

[DorianDepriester]

Dear community,

As part of the Elasticipy package, I have started implementing crystallographic texture support. This work naturally relies heavily on Orix for orientation handling.

Common texture components (Goss, Copper, fibres, etc.) are already available. At this stage, the implementation is limited to ideal texture components (i.e. no angular spread around the theoretical orientation), as well as combinations of such components. An example is provided here. This feature can, in terms, be moved from Elasticipy to Orix.

Any feedback or suggestions would be very welcome!

[CSSFrancis]

@DorianDepriester looks very nice!

I guess for now the first thing I'd recommend is adding it to the related projects. If you want to edit the docs you can otherwise I can as well.

I just did a quick glance at the package, one thing that I'd recommend is using sphinx-gallery. You have lots of nice examples but they aren't run/ part of the documentation from what I can tell. It would be easy to convert those into examples like this -->this and have them be run as part of building the docs.

[CSSFrancis]

It also might be good to discuss at some point if there are any changes to orix that would help. I'm not sure how much development time people have, but there are a lot of people who could point you in the right direction.

[argerlt]

Honestly, less lack of time, more lack of developers. @hakonanes and I are the only ones submitting and reviewing PR's lately, so if either of us have a busy month and need to put ORIX on hold, nothing gets added to main.

I'm always happy to talk through new feature requests though, and I have dedicated time at work each week to help with open source software development. It might just be a bit before a useful feature in a branch gets fully bug tested and added to ORIX proper.

[DorianDepriester]

Actually, the Example folder is (at this point) more a sandbox than a real public example. In the near future, I could indeed convert its content into "runnable" documentations. In the meantime, I use another repo to host a Jupyter Notebook, which can be run interactively on Binder.

About the "related projects" page, should I make a PR to add mine to the list?

[argerlt]

First off, thank you for commenting, and I'm glad you're finding ORIX useful. A few comments:

This feature can, in terms, be moved from Elasticipy to Orix.

There has been talk for a long time about adding texture components to ORIX. If this is something you would be interested in contributing to, we should talk more, it would be great to get some help.

... I'd recommend using sphinx-gallery.

I will absolutely second @CSSFrancis. It's a lot of work up front, but more maintainable in the long run. The resulting ReadtheDocs galleries are also (In my opinion ) much easier for outsiders to use than Binder. That said, it's also a feature you can add later, like in the examples Carter linked above.

About the "related projects" page, should I make a PR to add mine to the list?

I'd say go for it.

[argerlt]

Oh, it also just occurred to me: if you elasticipy depends on orix (and it looks like it does), adding it to the related projects tab via a PR helps lower the chances we accidentally break a feature in your package while ironing out mistakes in ours.

[DorianDepriester]

Dear all,
Just to mention that, as (originaly) suggested by @CSSFrancis, I have added an Example gallery with the aid of sphinx-gallery. Check it out here!
Thanks for the tip!