You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to report an issue in prior and scenario checking. So after running the simulations, I need to check if my observed data is located within the cloud of priors. Using SSR data, the analysis works fine. But when I use DNA sequence and a combination of SSR and DNA sequence, the analysis did not work. Even if I used the provided dataset (toy example), it did not work as well.
Any suggestion?
Please find attached the necessary files to diagnose the problem.
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.
Hello,
I would like to report an issue in prior and scenario checking. So after running the simulations, I need to check if my observed data is located within the cloud of priors. Using SSR data, the analysis works fine. But when I use DNA sequence and a combination of SSR and DNA sequence, the analysis did not work. Even if I used the provided dataset (toy example), it did not work as well.
Any suggestion?
Please find attached the necessary files to diagnose the problem.
Many thanks for your help.
Best,
Jakty
(Data)DIYABC - Fragmented_both_reduced.mss.txt
(Data)DIYABC - Fragmented_cpDNA.mss.txt
(log_toy)diyabc_prior_check_call.log.txt
(toy)headerRF.txt
(real_data)headerRF.txt
(log_real)diyabc_prior_check_call.log
The text was updated successfully, but these errors were encountered: