Skip to content
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

Issues with prior and scenario checking using DNA sequence data #143

Open
jaktykusuma opened this issue Dec 1, 2022 · 2 comments
Open
Labels
bug Something isn't working to investigate user feedback Issue filled by user

Comments

@jaktykusuma
Copy link

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

@gdurif
Copy link
Collaborator

gdurif commented Jan 16, 2023

Hi,
Sorry for the (very) late reply. I will investigate and get back to you. Thank you for the report and the attached files.
Best,

@gdurif gdurif added bug Something isn't working to investigate user feedback Issue filled by user labels Jan 16, 2023
@gdurif
Copy link
Collaborator

gdurif commented Aug 30, 2024

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,
Best regards

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working to investigate user feedback Issue filled by user
Projects
None yet
Development

No branches or pull requests

2 participants