-
Notifications
You must be signed in to change notification settings - Fork 3
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
doc: add documentation for the lineage_definitions format #652
Conversation
There is no change in the changelog. This PR will not produce a new releasable version. |
f00f6bb
to
8b96072
Compare
Linking GenSpectrum/LAPIS#978 for reference. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the scope of this? This is a very formal description. For a quick "let's pin down the schema", this is good. But it's not something that maintainers would understand, because it's not comprehensive enough (IMO). What does it mean to define those lineage? What consequences does it have on the data at runtime? How can users query it?
I wanted something that is at least one step above "ah, I found an example in the codebase" which is what happened now for Loculus ^^ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree, this is definitely better than nothing. I don't want to block here, we can improve it later.
8b96072
to
0983f88
Compare
Ok, fixed a typo in the commit message and will merge afterward |
Summary
Add documentation for the lineage definitions file, which is required for the specification of monophyletic sublineage queries.
PR Checklist