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
In version 0.15.0 seqkit amplicon only keeps one amplicon (the largest) per primer pair. I don't always care about the largest amplicon.
Would it be possible to implement the feature of keeping all valid amplicons? A bed file with the start and end bases (columns 2 and 3) of all valid pairs would be fantastic. That would permit me to inspect the amplicons and keep the one I want (in my case, the smallest amplicon over a certain threshold).
In my case, the positions in the bed file would be enough. I would choose the amplicon I want and use the positions as trimming points for my fastq reads--but the sequences of the PCR products may be useful for other users.
Hi, I have the same issue here. Outputting the largest amplicon only was misleading in my case, as I was looking for an amplicon within repititive RNA genes of an eukaryotic genome. Instead of predicting a correct PCR amplicon of size around 400bp, seqkit amplicon produced an amplicon of ~50 Kb which does not make any sense in my case.
As a solution, I see that outputting all valid amplicons is the best option, or you may add an option expected_amplicon_size to give this length a priority or to make an upper limit for the amplicon prediction.
Activity
shenwei356 commentedon Feb 23, 2021
Right, PCR could produce all combinations of the forward and backward primers. We should output them too.
mlosilla commentedon Feb 23, 2021
yeah exactly.
In my case, the positions in the bed file would be enough. I would choose the amplicon I want and use the positions as trimming points for my fastq reads--but the sequences of the PCR products may be useful for other users.
Thank you for considering it!
shenwei356 commentedon Mar 1, 2021
Oh, you can use
seqkit loatefirst, which outputs BED format.zjhzxjm commentedon Nov 3, 2022
期待这个功能早日上线
magbio commentedon Apr 3, 2024
Hi, I have the same issue here. Outputting the largest amplicon only was misleading in my case, as I was looking for an amplicon within repititive RNA genes of an eukaryotic genome. Instead of predicting a correct PCR amplicon of size around 400bp,
seqkit ampliconproduced an amplicon of ~50 Kb which does not make any sense in my case.As a solution, I see that outputting all valid amplicons is the best option, or you may add an option
expected_amplicon_sizeto give this length a priority or to make an upper limit for the amplicon prediction.Here is a toy example