You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The sleuth issues forum has received two separate reports from users that relate to an unexpected incompatibility between the hdf5 library version used in kallisto and that used in the rhdf5 library that underlies the read_kallisto_h5 and write_kallisto_h5 functions (pachterlab/sleuth#120 and pachterlab/sleuth#175).
Thus, I want to propose a feature request.
The incompatibility could be more easily identified in sleuth if kallisto included in the kallisto HDF5 output file an additional attribute to include the hdf5 library version used to construct the file, so that it could be easily accessed and checked against the hdf5 library version used by rhdf5 when reading the file. I think that would be the easiest solution from sleuth's end, though it could also work to use the run_info.json file. I think including the library version in both locations would be helpful to users.
I can't code in C++; otherwise, I would make the change myself.
The text was updated successfully, but these errors were encountered:
Hi @pimentel and @pmelsted,
The sleuth issues forum has received two separate reports from users that relate to an unexpected incompatibility between the hdf5 library version used in kallisto and that used in the
rhdf5
library that underlies theread_kallisto_h5
andwrite_kallisto_h5
functions (pachterlab/sleuth#120 and pachterlab/sleuth#175).Thus, I want to propose a feature request.
The incompatibility could be more easily identified in sleuth if kallisto included in the kallisto HDF5 output file an additional attribute to include the hdf5 library version used to construct the file, so that it could be easily accessed and checked against the hdf5 library version used by rhdf5 when reading the file. I think that would be the easiest solution from sleuth's end, though it could also work to use the
run_info.json
file. I think including the library version in both locations would be helpful to users.I can't code in C++; otherwise, I would make the change myself.
The text was updated successfully, but these errors were encountered: