Open davised opened 4 years ago
I can provide the original files, but any -p prefix.nex file with the * syntax works to produce this output.
Thanks Ed, for the report! Indeed this is a bug in writing .best_scheme.nex file. IQ-TREE just concatenate the string “” together in the merged partitions, which caused this unwanted behaviour. To fix this for now, you can ignore all , in case you want to use all alignment positions. Thaat means, e.g.:
begin sets; charset PA0005 = aligned/PA0005.aln; charset PA0008 = aligned/PA0008.aln; charset PA0308 = aligned/PA0308.aln; charset PA0373 = aligned/PA0373.aln; charset PA0375 = aligned/PA0375.aln; ...
And the problem should be gone.
Cheers Minh
On 5 Nov 2020, at 11:00 am, Ed Davis notifications@github.com wrote:
I can provide the original files, but any -p prefix.nex file with the * syntax works to produce this output.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Cibiv/IQ-TREE/issues/178#issuecomment-722039125, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADRTPU5E74TASSMGLUM65RDSOHTIDANCNFSM4TKVIYAQ.
Thanks! I'll remove the * from now on.
Background
I generated a tree using the
-p prefix.nex
syntax with alignment files provided using the * syntax to include the entire sequence. e.g.:I want to use the prefix.nex.best_scheme.nex file in another analysis. Here is the file:
Error log file
When I specify this file to a new run, I get this message:
This can be resolved by editing the
prefix.nex.best_scheme.nex
file to only include a single , instead of having a per file.