Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
sens.spec should be able to use a count file #225
Comments
pschloss
added the
Enhancement
label
Apr 14, 2016
pschloss
added this to the
Version 1.38.0
milestone
Apr 14, 2016
pschloss
changed the title from
sen.spec should be able to use a count file to sens.spec should be able to use a count file
Apr 14, 2016
|
I don't think we need the count file, do we? The name file is used to preprocess the list file to remove the dups, but when you create a list file with a count file it doesn't contain dups. |
|
That's right - then I guess we need to turn off the requirement that a names file be provided? Can you double check that we get the same result generating a list file with and without using a count file? |
|
I think we want to leave the names file. So right now you can cluster in 2 ways:
If you clustered with a names file then you would need to provide it so we can remove the duplicate sequences. If you clustered with a count file then the list file is already unique. The list files are different based on whether you cluster with a name or count file, but the shared file generated by the list and group or list and count are the same. Make sense? |
|
But this command doesn't use a shared file - it uses a list file, dist file, and currently a count file |
|
I thought it used a list, dist and names?? What the command is looking for is a unique list, correct? |
|
right sorry - list, dist, and names Sent frim my iPhone, expext more typos then nirmal
|
mothur-westcott
added a commit
that referenced
this issue
Jul 12, 2016
|
|
mothur-westcott |
67b1fa5
|
|
Added count file to work with opti method results |
pschloss commentedApr 14, 2016
Currently it takes in a names file, but not a count file. Also, to run this the user will need a distance file. If they run cluster.split, a composite distance file is not generated so we need to concatenate the distance files for each split.