-
Notifications
You must be signed in to change notification settings - Fork 1
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
Document CSV export format #257
Labels
Milestone
Comments
Merged
|
gaurav
added a commit
that referenced
this issue
Feb 28, 2024
gaurav
added a commit
that referenced
this issue
Jun 22, 2024
- Added note that definition should include qualifiers (closes #168) - Documented the CSV export format (related to #257, but I won't close that until I like to it from somewhere in the interface) as [a Markdown file](https://github.com/phyloref/klados/blob/bfae34e42e954920191e3e473f31ee2ae49ffdde/docs/ExportFormats.md). - Fixed a bug in which we were providing all the expected resolutions before all the actual resolution in the CSV file, despite the header saying that they should be interleaved (i.e. `expected 1, actual 1, expected 2, actual 2`). - The Open Tree of Life lookup code was previously recording the provenance of the phylogeny in the phylogeny description field, but since this field is no longer used, I've moved it into the phylogeny curator notes field (see example below). - I accidentally turned on "reformat file on save", and so my IDE changed a bunch of file formatting without me noticing. That shouldn't change any functionality and should be easier to read/maintain in the future, but it's still annoying. This PR also closes #300 by modifying the summary table to make it clear that the final columns refer to phylogenies and replacing phylogeny descriptions (which are no longer displayed in Klados) with phylogeny curator notes.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The CSV export format is designed to mimic the summary table we show the user, but it would be good for downstream applications to have this format documented on the website or docs somewhere.
The text was updated successfully, but these errors were encountered: