Repository navigation
parse_gctx: don't sort returned values #36
Description
I was thinking about doing a pull request where I modified parse_gctx to not return the dataframes sorted by index/column. The reason I propose this is if you read them out and get them in the order that they appear in the file, you can then choose the ones you are interested in, figure out their index id, and then use the ridx/cidx option to load them, which is much faster.
Also, could make it an option to do the sort. What do you think?
Activity
oena commentedon Apr 2, 2018
Hi @dllahr! Not sure I totally follow. Do you mean just for the metadata only options? Otherwise the IDs are subsetted before hyperslab selection occurs.
dllahr commentedon Apr 9, 2018
Sorry, no I mean that right now when you get the metadata back (and I think when you get it all back) all of the ID's have been sorted. The use-case I ran into was:
oena commentedon Apr 9, 2018
Ok, gotcha. That does seem like a useful thing to do. Maybe we can start with having it as an option and see how things go?
saksham219 commentedon Jun 1, 2019
@oena Has this been taken up? I was thinking of working on this.
oena commentedon Jun 3, 2019
@dllahr did you follow up on this? No worries if not, just checking
Merge pull request #58 from saksham219/issue_36