-
Notifications
You must be signed in to change notification settings - Fork 4
More harmonized coordinate operations #36
Copy link
Copy link
Open
Labels
InternalChanges how internal components are implemented/interact with minimal effect on APIChanges how internal components are implemented/interact with minimal effect on APIapi breakingWill change how codes invoking a part of polymerist will be writtenWill change how codes invoking a part of polymerist will be writtenpriority:mediumModerate urgency, issue has major impacts on some but not most parts of the codebaseModerate urgency, issue has major impacts on some but not most parts of the codebase
Metadata
Metadata
Assignees
Labels
InternalChanges how internal components are implemented/interact with minimal effect on APIChanges how internal components are implemented/interact with minimal effect on APIapi breakingWill change how codes invoking a part of polymerist will be writtenWill change how codes invoking a part of polymerist will be writtenpriority:mediumModerate urgency, issue has major impacts on some but not most parts of the codebaseModerate urgency, issue has major impacts on some but not most parts of the codebase
Representations and operations on collections of coordinates crop up in a handful of places in polymerist, often with significant overlap. It is intended to pull out and reduce redundant facility where possible, and to make coordinate operations as dependency-agnostic and class-agnostic as possible, ideally operating on (as close to) pure numpy array as possible. Namely, the following changes are proposed: