Closed laninsky closed 4 years ago
This is probably the most useful and best documented issue submitted by a non-developer, and the single most selfless gesture by any ipyrad user ever. Thank you for taking the time to contribute. -isaac
On Thu, May 7, 2020 at 12:48 PM Alana Alexander notifications@github.com wrote:
Closed #402 https://github.com/dereneaton/ipyrad/issues/402.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/dereneaton/ipyrad/issues/402#event-3312315042, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABNSXP6SRTNYS32ONTGO4G3RQKGZDANCNFSM4M3G2DSQ .
No worries Isaac! Least I can do given you guys make such an amazing package freely available to us!
@Pointyhead documented this in the gitter back in November 2019 with a KeyError: 66, but I just got tripped up by it again (KeyError: 86), so I thought I'd make and close an issue just so it is documented in the issues for the next person who runs into it.
Getting a
KeyError: some number
during step 7 immediately following the build arrays step is likely due to ambiguity sites in your reference sequence.You can solve this by using maskambignuc from the emboss package to replace the ambiguous sites from the reference with Ns before running ipyrad.
Here's what the error looks like. Calling ipyrad:
Output:
But after converting the ambiguous sites in the reference to Ns: