-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running figaro fails on 16S V4 data #36
Comments
Interesting... I would be willing to bet that causes it to crash. I definitely built around optimizing for much longer amplicons (like V1V2 or V3V4) |
Is it because of the length of the amplicon or because the reads are longer than the length of the sequenced amplicon? In any case, would this be an easy fix? Do you accept pull requests? |
Yes I do. Can you email my Zymo research.com email address?
…Sent from my iPad
On May 12, 2021, at 9:36 PM, dean0358 ***@***.***> wrote:
Is it because of the length of the amplicon or because the reads are longer than the length of the sequenced amplicon?
In any case, would this be an easy fix? Do you accept pull requests?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Hi, I would like to try Figaro on my V4 Illumina paired libraries but I am getting an error. I am running the code: I am getting the following error - any suggestions appreciated. Thanks-A The above exception was the direct cause of the following exception: Traceback (most recent call last): |
This is a problem I haven't seen before. Can we move this to a new issue? I will need to check out your data quickly to see how this might be happening. |
@michael-weinstein yes, please. Although wondering if Figaro must be a perfect match for F and R libraries as I am running on demultiplexed data that is not a perfect match? If that is not possible, then may be why the error is pulling? |
Can you reach out to Zymo tech support? They'll give you my contact info and I will set up a chat. |
Thanks Michael,
I am working with non-perfect paired libraries if that makes a difference?
Does Figaro only work on perfect pairs?
I will reach out to help @ Zymo to set a chat. I am a volunteer post-doc
working on this on evening and weekends so depends on time zone and if I
can find space. I will also see if my supervisor is up for the task of
getting Figaro going as he might have different environments to try it on.
Overall I was pretty happy I got that far with the install because
installing packages is not my best skill. The instructions on how to
install and get Figaro up and running were very nicely done and easy to
follow.
Thanks for your offer to help investgate the errors.
-A
…On Wed., Sep. 1, 2021, 6:26 a.m. Michael Weinstein, < ***@***.***> wrote:
Can you reach out to Zymo tech support? They'll give you my contact info
and I will set up a chat.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#36 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AN75GE7DEGK7WXGTMSTS4W3T7YSXLANCNFSM44S2IB2A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
I wanted to check back if you were able to reach tech support. I haven't heard from them yet, but once I do, I will set us up a quick zoom call. |
Hi Michael,
My apologies. I am swamped at my normal job (doing microbiome on a
voluntary basis). What time zone are you in, I did want to follow-up.
thanks
-A
…On Wed, Sep 8, 2021 at 10:29 AM Michael Weinstein ***@***.***> wrote:
I wanted to check back if you were able to reach tech support. I haven't
heard from them yet, but once I do, I will set us up a quick zoom call.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#36 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AN75GE7ZU7L4ACEVH6A2MRDUA6MQHANCNFSM44S2IB2A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
I am running Figaro on 16S V4 libraries sequenced on an Illumina MiSeq Instrument (MiSeq Reagent Kit v3; 2x300 bp). The length of the sequenced amplicon is ~250bps. The reason why I chose to use a 2x300 kit is because it was cheaper and produced more reads on a single run compared to the traditional MiSeq Reagent Kit v2; 2x250 bps.
When I run Figaro with the following parameters:
The program throws the following error:
However, when I change the length of the amplicon (e.g., 300 bps), the program completes successfully. It seems that Figaro is having trouble with this particular dataset because the reads are longer than the sequenced amplicon. This could probably be resolved by trimming the trailing 30 or so base pairs from each read, as these are not biologically relevant, and then rerunning Figaro on the trimmed reads. Has this issue been discussed previously?
Best,
Chris
The text was updated successfully, but these errors were encountered: