mtex icon indicating copy to clipboard operation
mtex copied to clipboard

ODFs plotting differently

Open zmichels opened this issue 6 years ago • 4 comments

Hello,

I have a wealth of data saved that were calculated in previous versions of MTEX (prior to 5.x).

Today I imported some quartz ODF's that I made in MTEX 4.5, and when I plotted them they looked completely different than previous plots. It seems like maybe they are plotted in the crystal reference frame (?) rather than the specimen reference frame. Is there something I can do to force 5.x versions of MTEX to plot older ODFs the same, or do these all need to be recalculated using 5.x in order to use 5.x exclusively (rather than reverting to 4.5 every time I want to reliably plot these ODFs)?

Thanks for any help, Zach

zmichels avatar Mar 03 '18 04:03 zmichels

Hi Zach, could you add a little example image and the lines of code you use for plotting?

Cheers, Rüdiger

kilir avatar Mar 03 '18 15:03 kilir

Thanks for any help!

I import a preexisting variables ‘odf’, and ‘h’ for quartz (computed earlier using mtex 4.5)

Use something like the following for plotting: plotPDF(odf, h, ‘antipodal’, ‘lower’, ‘smooth’, ‘colorrange’, ‘equal’)

And get these different results (same data imported for both): Image Image

zmichels avatar Mar 03 '18 16:03 zmichels

That's indeed the case and starts with https://github.com/mtex-toolbox/mtex/commit/bf65f760c2a1009f38e2f1628d5870f206897b33 related to the switch in using NFFT. A temporary workaround could be to use the "old" affected functions under a different name and call them if a certain switch is given? Maybe there's a way to convert ODFs calculated with the old binaries, but I don't see how to do this - which totally doesn't mean that it wouldn't be super easy. Sorry not be of greater help for this one.

Cheers, Rüdiger

kilir avatar Mar 03 '18 18:03 kilir

Rüdiger,

Thank you much for helping to confirm!! Just good to know.

Cheers, Zach

On Mar 3, 2018, at 12:04 PM, Rüdiger Kilian <[email protected]mailto:[email protected]> wrote:

That's indeed the case and starts with bf65f76https://github.com/mtex-toolbox/mtex/commit/bf65f760c2a1009f38e2f1628d5870f206897b33 related to the switch in using NFFT. A temporary workaround could be to use the "old" affected functions under a different name and call them if a certain switch is given? Maybe there's a way to convert ODFs calculated with the old binaries, but I don't see how to do this - which totally doesn't mean that it wouldn't be super easy. Sorry not be of greater help for this one.

Cheers, Rüdiger

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/mtex-toolbox/mtex/issues/320#issuecomment-370167389, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AIXQU7X8CTkCjxDwa3DMlx8PAf1OZynyks5tatsUgaJpZM4Sax2W.

zmichels avatar Mar 03 '18 18:03 zmichels