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

dfit aggregated results #16

Open
fgvieira opened this issue Dec 6, 2023 · 1 comment
Open

dfit aggregated results #16

fgvieira opened this issue Dec 6, 2023 · 1 comment

Comments

@fgvieira
Copy link
Collaborator

fgvieira commented Dec 6, 2023

When the option --nodes is specified, dfit aggregates the results. Don't think it makes much sense to be here, since dfit should just optimize the matrices it gets as input.

On the other hand, if LCA bdamage prints matrices for non-specific levels (see #14), these might be being counted twice.

@fgvieira fgvieira changed the title dfit dfit aggregated results Dec 8, 2023
@ANGSD
Copy link
Collaborator

ANGSD commented Dec 18, 2023

I do not have a problem with the internal mismatch matrices being in memory solely. Is it because you want to observe the internal mismatch matrices?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants