parse_gctx: don't sort returned values about cmappy HOT 6 OPEN

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?

from cmappy.

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.

from cmappy.

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:

1. got just the row metadata back
2. identified the overlap between the genes I wanted an those that were present
3. identified the indices of the genes I wanted in the row metadata
4. attempted to load using the ridx option, got a completely different set of genes
5. realized that the row metadata had been sorted, rather than returned as it appears in the file

from cmappy.

@oena Has this been taken up? I was thinking of working on this.

from cmappy.

@dllahr did you follow up on this? No worries if not, just checking

from cmappy.

Sorry I'm late replying, I did not get to doing anything with this.

from cmappy.