Improved Documentation for COR and Tilt Usage #2459
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue
Closes #2359
Description
While some improvements were already made to the documentation (see issue #2414), not all questions from the issue were fully addressed. This PR extends the improvements to ensure all questions are fully resolved:
Specifically:
What COR and Tilt do exactly:
Already explained as COR ensures alignment, and Tilt adjusts COR linearly across slices.
No changes were needed, as these sections were clear.
What order should I apply them?
Previously outlined that Tilt depends on COR of slice 0 but did not emphasize the sequence.
Added a new "Order" subsection to clarify the sequence: determine COR for slice 0 first, then apply Tilt.
What does refining do?
Already detailed as a manual process to improve accuracy, especially for noisy data.
No changes were made, as this section was comprehensive.
Examples?
Added practical tips subsection