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
I would like to get the raw data for ANI distributions of reads in the provided plot. I don't think this is accessible through the existing raw files that are outputted with the API. Is inStrain filtering the BAM file based on the PID flag with something like bedtools (I think that's how I've done it before)? I just want to parse the same information that is given in the readANI plot to do downstream things with the data for multiple samples to the same genome.
The text was updated successfully, but these errors were encountered:
Yes, you're right that at the moment this information isn't accessible through the public API. The next big inStrain upgrade will be adding functionality to parse the raw_data to create tables like this on-demand, but unfortunatley that won't be ready for a while.
The information for this plot is generated using the function prepare_read_ani_dist_plot, in the file inStrain/plotting/mapping_plots.py (
The method takes in an inStrain profile object and loads the covT and scaffold2length objects from raw_data to create this information. You should be able to either import and call this method, or copy the code into a new python notebook and run it yourself. That said, I realize that this isn't a very straightforward process and I'm happy to help when you run into snags.
I would like to get the raw data for ANI distributions of reads in the provided plot. I don't think this is accessible through the existing raw files that are outputted with the API. Is inStrain filtering the BAM file based on the PID flag with something like bedtools (I think that's how I've done it before)? I just want to parse the same information that is given in the readANI plot to do downstream things with the data for multiple samples to the same genome.
The text was updated successfully, but these errors were encountered: