Update write_kallisto_hdf5
function and add ability to subset kallisto object (address #131)
#150
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.
Hi @pimentel,
Thanks to the work of @agropyron and small tweaks, we have a working write function. I've added some S3 methods (with updated documentation and
NAMESPACE
) to subsetkallisto
objects (or the collection ofkallisto
objects within a sleuth object). This should address issue #131.When I did a checkout of the recent commit on the
devel
branch, there were several miscellaneous things related to the documentation andNAMESPACE
forgene_for_gene
that need to be fixed, so I'll be including those here too.Only issue right now is that if a user subsets kallisto objects within a sleuth object, there isn't a way for the user to know to rerun
sleuth_prep
, and there will now be mismatch between theobj$kal
and the rest of the object. There isn't an easy way to rerunsleuth_prep
with just theobj$kal
list, so should we implement that?