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 was reviewing transcriptomev3.1-BLAST-to-GOslim.ipynb and noticed that there appeared to be some SPIDs in the BLAST results that were not present in the output of the join command (In [28]: ):
#joining blast with uniprot annoation file and reducing to three columns UniprotID, Query, All GO terms
join -t $'\t' \
_blast-sort.tab \
uniprot-SP-GO.sorted \
| cut -f1,2,14 \
> _blast-annot.tab
I ran a quick comparison and identified 209 SPIDs in the _blast-sort.tab file that don't have corresponding SPIDs in the uniprot-SP-GO.sorted file.
If someone can/wants to double-check, here's how I compared the two files:
I was reviewing
transcriptomev3.1-BLAST-to-GOslim.ipynb
and noticed that there appeared to be some SPIDs in the BLAST results that were not present in the output of thejoin
command (In [28]:
):I ran a quick comparison and identified 209 SPIDs in the
_blast-sort.tab
file that don't have corresponding SPIDs in theuniprot-SP-GO.sorted
file.If someone can/wants to double-check, here's how I compared the two files:
Grab unique SPIDs
Use
comm
to only show entries present inblast-sort-unique.txt
$ comm -13 uniprot-SP-GO.sorted-unique.txt blast-sort-unique.txt | wc -l 209
Should an updated version of
uniprot-SP-GO.sorted
be produced and then used to re-run the analysis?The text was updated successfully, but these errors were encountered: