We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
At the moment we have the alignment and the SETS block all in one file. But this is annoying in terms of utility.
If we go ahead and make the partitions, loci, and genomes into a csv file, it would be better to have:
partitions.nex, loci.nex, and genomes.nex all have CHARSETS only, which list the relevant sites for each element.
E.g. partitions.nex would look like:
begin SETS; CHARSET COI_1stpos = 1-1592\3; CHARSET COI_2ndpos = 2-1592\3; CHARSET COI_3rdpos = 3-1592\3; CHARSET 16S = 1593-3037; end;
and loci.nex would look like:
begin SETS; CHARSET COI = COI_1stpos: 1-1592\3, COI_2ndpos: 2-1592\3, COI_3rdpos: 3-1592\3; CHARSET 16S = 16S: 1593-3037; end;
etc
This lets people easily do whatever kind of analysis they are interested in.
The text was updated successfully, but these errors were encountered:
All of these files can be automatically built from the csv file
Sorry, something went wrong.
No branches or pull requests
At the moment we have the alignment and the SETS block all in one file. But this is annoying in terms of utility.
If we go ahead and make the partitions, loci, and genomes into a csv file, it would be better to have:
partitions.nex, loci.nex, and genomes.nex all have CHARSETS only, which list the relevant sites for each element.
E.g. partitions.nex would look like:
and loci.nex would look like:
etc
This lets people easily do whatever kind of analysis they are interested in.
The text was updated successfully, but these errors were encountered: