-
Notifications
You must be signed in to change notification settings - Fork 28
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
Error starting EEMS #26
Comments
This is a problem in the sense that both the prior and the likelihood should be finite numbers. eems generates some output at the start, mostly related to the grid and how the samples are assigned to demes in the grid. Looking at a plot of just the grid before any parameters are estimated might help. For example, it would be a problem if in the .coord file locations are specified as (latitude, longitude) and in the .outer file locations are specified as (longitude, latitude).
I will probably start here. |
The next step might be to generate a .diffs matrix and use that together with the real coordinates, so that you can check whether the problem might be in the dissimilarity matrix. (I have an R script to generate a dissimilarity matrix.) |
Thanks for such a quick reply!
Both the .outer and .coord file are in 'long, lat' format, and all samples
are assigned to demes according to the initial output from the program.
To clarify your next suggestion, should I create the .diffs matrix and run
eems_snps, or will eems_sats accept a .diffs file instead of a .sites file
as well?
Thanks again,
Emma
…On Tue, May 1, 2018 at 11:34 AM Desislava Petkova ***@***.***> wrote:
The next step might be to generate a .diffs matrix and use that together
with the real coordinates, so that you can check whether the problem might
be in the dissimilarity matrix. (I have an R script to generate a
dissimilarity matrix.)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#26 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AlFYK-QvdqGO76MPvN8eqr1aYfJqN5Leks5tuHJ-gaJpZM4Tt-ZN>
.
|
Hello Emma, Sorry about not getting back to your question sooner. If you still have this issue and are interested in looking into it, my suggestion is to use simulated diffs matrix with the real coordinates, and simulated coordinates with the real matrix. [Hopefully, this will help to find more precisely where the problem with the likelihood is.] It is easy to simulate coordinates -- they don't need to be actual latitudes/longitudes to run eems and make the plots. The runeems_sats version won't work with a .diffs matrix but you can use the runeems_snps version with that. I suspect that computing the likelihood ends up in an Inf, though I don't know why. How many individuals and how many microsatellites do you have? It might also be interesting to use subset(s) of your actual data to check if a particular subset of individuals and/or microsatellites causes the problem. |
I'm going to add to this here, as I'm having the same issue. My population I've attached my directory of input files, as well as the output files generated, with the screenshot of the error below. I'm using a standard run with the starting code Let me know if there is anything else I can provide, and thank you! |
Hi Dr. Petkova,
I'm trying to run eems_sats. I've got it working with one set of data, so it seems to be running fine, but not with the other set. All my input files and input parameters read in properly but then I see:
Initial log prior: 97.3
Initial log llike: inf
[RunEEMS] Error starting EEMS.
I realize this might be difficult to disentangle without my files, but I've compared the inputs with those that have worked and do not see any differences. The genotype files look very similar, the size of the .sites matrix and .coord file matches the parameters, and the .outer is a simple rectangle. Is there perhaps something with the data itself that is causing this problem? Is 'initial log llike: inf' a problem? In runs that have worked for me this number has been a large negative number.
Any help would be greatly appreciated.
Many Thanks,
Emma
The text was updated successfully, but these errors were encountered: