Hi Keyur,
This is a very interesting question. I'd say that there's no reason that salmon shouldn't work with this data. However, it would be very interesting to see how different the "estimated" counts you get from salmon are compared to the "raw" counts you get from mapping isoseq reads to transcripts. The reason I mention this is that I'd expect most isoseq reads to be long enough that they map uniquely, so that the multi-mapping that is prevalent in "traditional" short-read sequencing should pose much less of a problem. Nonetheless, there still may be some differences if reads originate from very similar transcripts. Likewise, there is nothing about the quasi-mapping procedure (what salmon does when you run it directly on the fasta file) that is specific to short reads, and so it should work on the pacbio reads as well. That being said, IsoSeq is rather new (and expensive), and we've not tested on this type of data yet. Given the nature of the IsoSeq data (far fewer, far longer reads), the time difference between quasi-mapping and a traditional aligner (like STAR) is likely to be much smaller than for e.g. Illumina reads. Personally, my approach would be to align the reads and then quantify the BAM, and then to compare the results you get thorough that approach to the results you get from using salmon to quantify the abundances directly from the fasta file. Just be certain that when you generate the alignments you either (a) align directly to the transcriptome and not the genome or (b) have the aligner "project" the alignments into transcriptomic coordinates (I know that STAR and HISAT2 have options for this). I'd be very interested in hearing how things work out, as this is a use case we haven't consider much to this point.
Best,
Rob