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
Edge trimming not depositing UCEs into folder #166
Comments
It looks like you have <3 taxa in your alignments. You should have 4. |
Uncertain how this is possible, as the "Exploding the monolithic FASTA file" step returns stats for all four species... |
I can't see what sort of setup you are running or the exact command that you ran or the exact output that was generated in the included screenshot. Are you sure the phyluce environment is activated and that mafft is in your $PATH? That can also cause the same problem. Also, i've tested all of these steps w/ the tutorial data, so it is usually a setup problem that causes these errors rather than a problem w/ phyluce or the tutorial. |
Hi Brant - apologies for not including enough information. I'll now try to give all possible information! My setup is on a computing cluster, running the most recent version of phyluce installed to a subdirectory folder ( The exact command I ran, in the
Here is the full output log file: phyluce_align_seqcap_align.log The phyluce environment is activated ( Also, on the previous step ("Exploding the monolithic FASTA file"), when entering:
it returns:
So, I do have all four species, and also the "Too few taxa (N <3)." section in the log file is also in the Tutorial 1: UCE Phylogenomics output for the Edge trimming step ("WARNING - DROPPED locus uce-6169. Too few taxa (N < 3)." followed by "[many more loci dropped here]"). So, the only unusual thing, as I see it, is why, after "Writing output files", it for some reason is dropping all remaining uce-### "from output", and I end with an empty mafft-nexus-edge-trimmed directory. Any thoughts on the possible issue here? |
Hi Brant, Just checking in on this! Any thoughts, based on this information, on what potential setup (or other) problem might be resulting in this failure to output trimmed sequences? Is there any other information I can provide? |
Not really. I would try to run this locally - on your laptop. If you copy over the Can you also add a link here to your `all-taxa-complete.fasta? |
Sure, I had to change it to a .txt file to upload here: |
try to add the
|
It runs with that option, and deposits nexus-formatted UCE sequences into the folder. What does this mean? Based on the tutorial, this would suggest that for some reason it is able to do internal trimming but not edge trimming, is this correct? |
It just means that the internal trimming for this set of alignments is turned off. You could run Gblocks or Trimal against the alignments and that should work reasonably well. You can actually also still run the edge trimming separately from the alignment (phyluce_align_get_trimmed_alignments_from_untrimmed), but I suspect that will have the same result for your set of alignments. |
I see, thanks! I wonder why this happening... In any case, I'll explore these other options as well - thanks again. |
I’m not sure why this is occurring with your alignments (and don’t have time to check at the moment). If you pick one of the other options, you should be able to move forward. |
Hello Dr. Faircloth, This is an edited version of my log:
2021-01-05 14:25:06,918 - phyluce_align_seqcap_align - INFO - ============== Starting phyluce_align_seqcap_align ============== Many thanks. |
I would try with the |
Well, good news is Mafft is working with the --no-trim function activated. Bad news is I am still finding the same problem, after running phyluce_align_get_trimmed_alignments_from_untrimmed. So my question is, is there something else I can try with this code? or should I use alternatives like Gblocks or Trimal to do the edge trimming? (phyluce) ncortes@vortex:~/Novogene_Data/Afrater-set1$ phyluce_align_get_trimmed_alignments_from_untrimmed \
2021-01-06 13:42:32,255 - phyluce_align_get_trimmed_alignments_from_untrimmed - INFO - == Starting phyluce_align_get_trimmed_alignments_from_untrimmed = |
You can try those other options... but what's happening suggests there may be something concerning with your alignments (causing them to be trimmed so much). Basically, sequences get trimmed a ton when the alignments are not very good, resulting in them being trimmed to nothing. So, I would very closely check your alignments (and maybe the alignments produced by Gblocks/trimAL) to ensure the results are reasonable. |
Thank you, I will definitely keep an eye on those alignments. If something is wrong, it's for sure concerning. |
During the Edge trimming step of the UCE tutorial, the following happens, which seems to differ from the output expected according to the tutorial:
The "Dropped uce-#### from output" list isn't shown in the tutorial... and the output ends with:
With no sequences deposited into the mafft-nexus-edge-trimmed folder.
The text was updated successfully, but these errors were encountered: