rPIE tweaks, comment out rPIE scan position correction as it's not doing things correctly (I'll fix later). #333
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
(a) rPIE probe update is now strictly ePIE as the parameter which makes ePIE and rPIE different is irrelevant for the probe updates, (b) rPIE scan position correction has been commented out for now as it is incorrect and not effective, (c) renamed/removed some redundant variables in multislice rPIE
Approach
I'll fix the rPIE scan position correction code later or simply remove it from rPIE and LSTSQ code so that both ptycho updates schemes for the sample/probe use the same scheme for scan position updates. Also, from a recent publication of mine that thoroughly benchmarks rPIE and ePIE, we concluded that for the probe updates that rPIE and ePIE are equally effective. Since ePIE is simpler to compute, we use this now for the probe updates (rPIE is still used for the sample updates).
Pre-Merge Checklists
Submitter
Reviewer