-
Notifications
You must be signed in to change notification settings - Fork 43
[WIP] Indexing along axes #2
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
Merged
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
757b614
First cut at adding plug-in axes indexing; includes indexing vectors of
tshort 84358be
First pass at implementing axis indexing with traits
mbauman 6777ad5
Fix tests by specializing CartesianIndexes
mbauman f278efd
Add vector indexing on Categorical axes; add some tests.
tshort 5f22f49
Fix ambiguity warnings
mbauman 9dc578c
Remove type parameter for the axes element types
mbauman cb03d44
Check axis invariants in constructor
mbauman fbbf674
Add CartesianIndexing specialization
mbauman 77013eb
Check that all indices match
mbauman File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,6 @@ | ||
module AxisArrays | ||
|
||
export AxisArray, Axis | ||
export AxisArray, Axis, Interval | ||
|
||
include("core.jl") | ||
|
||
|
This file contains hidden or 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
This file contains hidden or 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It'd be nice to have another method that indexes on an array of elements. Here's a start at that (untested):
Edit: fix typo. I actually tried it. It works, but note that with
findin
, columns are selected, but they are given in the original order, not the order specified inidx
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems reasonable. You can go ahead and add it to this branch. I'll work tonight on fixing the getindex ambiguities. It's a bit of a mess.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay. (Probably not til tonight.)
On Tue, Feb 17, 2015 at 9:12 AM, Matt Bauman [email protected]
wrote: