-
Notifications
You must be signed in to change notification settings - Fork 2
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
Assignment of individuals to sample #139
Comments
Hi, could you elaborate your question ? potentially with an example. I am not sure to understand it. |
Ok, so my samples are named like this, with the third column describing the population. It is not clear to me does the program take the sample (population) info in an alphabetic order (K1,K2,K3) or by the order of appearance (K3,K1,K2). I cannot find in the output files any info which individual falls into which sample (population).
|
Hi, sorry for the very late reply. Could you tell me which type of data you are considering ? Thanks |
Hi, no problem, I'm working with SNPs. To be fair because I was not sure how the program works, I've sorted the data according to the population column. |
Hi, I am really sorry for the very late reply. Due to work overload, the development, support and maintenance for the project diyabcGUI is currently paused. Feel free to contact us (by submitting an issue) if you want to take over the development for this project. Pull request are also welcome to fix bug or implement missing functionalities. I have updated the README file to announce this. This is the official announcement to clarify a situation that has been going on for quite some time. You can still use the command line version of the software which is still maintained/supported. Check the documentation page here. All my apologies for the trouble, |
Where can I find the information which shows which individual fall into which sample or number of indivualass in each sample? Without this for me it can be quite confusing, especially when you have few thousand samples.
The text was updated successfully, but these errors were encountered: