Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DM-35530: Fix typo in persisted scarlet model data #57

Merged
merged 2 commits into from Jul 12, 2022
Merged

Conversation

fred3m
Copy link
Contributor

@fred3m fred3m commented Jul 12, 2022

No description provided.

@@ -130,7 +130,7 @@ def asDict(self) -> dict:
return {
"xy0": self.xy0,
"extent": self.extent,
"center": self.extent,
"center": self.center,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because of the mix-n’-match of conventions, it wouldn’t hurt to be explicit about (y, x) vs. (x, y) in the variable doc strings (in addition to your comment in the class description above). I got nervous looking at your test…!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point, I'll make it clear in the docs.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's actually more confusing than you think. To be consistent with xy0 and the rest of the stack, the center in the persistence model is in (x, y) format, it's just scarlet that uses the C++ (y, x) format. But I am clarifying in the docs.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤪

@fred3m fred3m merged commit 9630dc6 into main Jul 12, 2022
@fred3m fred3m deleted the tickets/DM-35530 branch July 12, 2022 15:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants