Issue Tracking for 0.18.0 Release

[CSSFrancis]

Release 0.18.0 (The Orientation Mapping Overhaul)

@viljarjf we are finally going to make Orientation Mapping easy!

My hope is that this is the last release before the 1.0.0 release! There are still some changes/ deprecations that need to be done and then we can really start to purge some of the code.

To Do List:

• Fix Azimuthal Integration
  • Azimuthal Example #1009
  • Azimuthal 1D Addition #1008
  • Refactor Azimuthal Integrator Cleanup #1000
  • PyFAI dependency issues  #987
  • Testing out Some Caking Methods  #989
• Refactor Orientation Mapping (finally)
  • Make a Class to hold Orientation Mapping Results Refactor Orientation Mapping #1018
  • Make Orientation mapping a function of Polar2D Refactor Orientation Mapping #1018
  • Add in Templatematching interactive result plot #967
• Other things that need doing
  • Refactor Subpixel Refinement #980
  • Problem with Calibration #901
  • Center of Mass --> Map function #1005
  • Fix up Radial/ ellipse tools Deletion Candidate: Radial Utils #1002 Potentially changing our approach to affine transforms #1011
  • Clean up VDF Deprecate Virtual Imaging #1014

---

• Diffsims (Merge Use phase class diffsims#201)
• Make a 0.6.0 Release

[pc494]

Things I'm working on

For 0.18.0

• Tidy up the utils per Reorganisation of utils #996
• Bump to sensible versions of our dependencies Getting our dependencies sensibly versioned #1021
• Tidy up our deprecations Bring all deletions forward to 0.19.0 #1050

In the pipe for 1.0.0

• Return coverage to 100%
• Set up a functional cron job
• Get rid of all the warnings from our testing code.

[CSSFrancis]

In the pipe for 1.0.0

• Return coverage to 100%
• Set up a functional cron job

@pc494 What exactly do you mean by a functional cron job?

[pc494]

In the pipe for 1.0.0

• Return coverage to 100%
• Set up a functional cron job

@pc494 What exactly do you mean by a functional cron job?

as far as I can tell we don't currently run the testing suite at some fixed time interval. In the past (when we still used TravisCI) this used to happen once a week or so. The main purpose is to spot downstream changes so that they can be corrected for when they arise, rather than making an (unrelated) PR at some point in the future fail.

[CSSFrancis]

as far as I can tell we don't currently run the testing suite at some fixed time interval. In the past (when we still used TravisCI) this used to happen once a week or so. The main purpose is to spot downstream changes so that they can be corrected for when they arise, rather than making an (unrelated) PR at some point in the future fail.

@pc494 ahh makes sense. I just wasn't thinking... The tutorials do this at the moment (however they are failing 😬).

[CSSFrancis]

@pc494 What do you think about trying to push for the 0.18.0 release soon. What is still needed to be done (besides the large and daunting pyxem/diffsims#201 (and #1018)

[pc494]

@pc494 What do you think about trying to push for the 0.18.0 release soon. What is still needed to be done (besides the large and daunting pyxem/diffsims#201 (and #1018)

I am keen. I am out-of-office until early the middle of next week though. Is a target of March 22nd to far out?

[CSSFrancis]

@pc494 that sounds good! It might be nice to get this done before the end of March :) these things always take a bit longer than anticipated.

[pc494]

Status update. I'm grinding along with #996 (see #1030) and am happy to review stuff but that'll be me for this release.

[pc494]

I think it would be nice to deal with #950 and #967 while before 0.18.0 as well.

[pc494]

@pc494 What do you think about trying to push for the 0.18.0 release soon. What is still needed to be done (besides the large and daunting pyxem/diffsims#201 (and #1018)

If I'm following correctly pyxem/diffsims#201 now needs an orix patch fix? In which case I'm going to focus some attention there as it's probably our blocker now.

[CSSFrancis]

If I'm following correctly pyxem/diffsims#201 now needs an orix patch fix? In which case I'm going to focus some attention there as it's probably our blocker now.

That is correct!