Open imaa9 opened 1 year ago
Yes, ambig bases in the reference will cause problems, so it's good you found that and fixed it. By the time of step 7 all the formal assembly has been completed, so fixing the reference sequence will require to roll back and re-run from at least step 3 (including the -f flag) in order for the change in reference fix this error at step 7. Let me know how it goes....
cool, many thanks for the quick reply! I'll run it again from the start, I think that should fix it. Just wanted to make sure this was the issue before I submit this big job again.
Hi Isaac,
I'm running ipyrad [v.0.9.90] with maximum memory allocation (184G), 48 threads, and with the following (relevant) params:
Thus runs fine through part 2 of step 7:
Here is the traceback info:
I followed the suggestion of a previous issue about using a reference genome with masked ambiguous bases (I just converted each to one of the possible resolution options) and tried running step 7 again with that, but it failed as above. Do I need to run the entire pipeline again from the beginning using the unambiguated reference, or is there something else that's causing this error in step 7? any insights would be much appreciated!
Thanks, Inbar