-
Notifications
You must be signed in to change notification settings - Fork 74
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
cli: tskit populations blah.ts
fails
#2050
Comments
Any chance you can attach the |
Sure. Github made me change the extensions so they could be uploaded. SLiM script. initialize() {
initializeMutationRate(1e-7);
initializeMutationType("m1", 0.5, "f", 0.0);
initializeGenomicElementType("g1", m1, 1.0);
initializeGenomicElement(g1, 0, 99999);
initializeRecombinationRate(1e-8);
initializeTreeSeq();
}
1 {
sim.addSubpop("p1", 500);
p1.name = "awesomepop";
}
2000 late() { sim.treeSeqOutput("/tmp/slim.ts"); } Msprime command:
|
Also related: MesserLab/SLiM#254
But actually, all of the tskit subcommands fail if they correspond to tables with metadata.
|
This is a dupe of #1860 - those commands are doing a text dump of the tables, and the text dump is broken for tables with decodeable metadata. Should be an easy fix, it's just a question of priorities - would you like to see this fixed for 0.4.0? |
I wonder if there isn't a second bug here. The SLiM case in my opening comment indicates a different error to #1860. @bhaller says this metadata is cool and normal (MesserLab/SLiM#254 (comment)), so that suggests there's some additional problem in tskit (separate to the
It's not a high priority for me. |
Actually fixing this may not be urgent, but let's be sure that there is nothing wrong with the .trees that SLiM is now emitting, in terms of its metadata etc., before SLiM 3.7 ships – i.e., pretty much now. :-> So it would be great to have a complete understanding of @grahamgower's "second bug" here, ASAP. |
What's the second bug @grahamgower? Sorry I'm not following. |
The two exceptions in my first post are different. I don't have enought insight to decide if they're one or two bugs (but one is certainly the same as #1860). |
I think that the SLiM message is different because SLiM puts in "empty" metadata for some populations. So - same problem, I think (although the tests should probably include situations like this, where NULL is allowed). |
I can confirm that the msprime file's error is resolved. How ever the SLiM file still errors, this is because its populations define a JSON metadata schema but some of the entries are |
The schema for SLiM's populations have |
The discussion about whether |
Specifying |
Closing this as #2064 is the discission of if/how to accommodate sllim's |
I'm not sure what
tskit populations
cli subcommand is supposed to do. I expected it to show the populations or something. Instead I get:For a SLiM (bleeding edge version) tree sequence
For an msprime tree sequence:
This was from:
But the output is the same with tskit 0.3.7
The text was updated successfully, but these errors were encountered: