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

rationalize column headers across CSV output files #1555

Open
ctb opened this issue May 26, 2021 · 5 comments
Open

rationalize column headers across CSV output files #1555

ctb opened this issue May 26, 2021 · 5 comments
Labels
5.0 issues to address for a 5.0 release
Milestone

Comments

@ctb
Copy link
Contributor

ctb commented May 26, 2021

prefetch and gather use different CSV column headers for their output, and I'm sure so does search and other commands.

Would be good to fix this in v5.

@ctb ctb added the 5.0 issues to address for a 5.0 release label Jan 6, 2022
@ctb
Copy link
Contributor Author

ctb commented Jan 6, 2022

might want to include duplicate columns for backwards compat... everything in genome-grist and charcoal will break if we swizzle the names 😆

specific example: gather output has name, prefetch output has match_name. Grr.

@ctb
Copy link
Contributor Author

ctb commented Mar 12, 2022

I was thinking that a ~clean way to do this would be to add two options, one to use current column names (default in v4.x) and one to switch column names (new); then swizzle the defaults for v5, and deprecate the current column names in 5; and then remove the old column names in v6.

@ctb
Copy link
Contributor Author

ctb commented Sep 8, 2022

starting to work on this: https://hackmd.io/EdrdrkByQ7a2GuyiN5oyGQ and #2274

@ctb
Copy link
Contributor Author

ctb commented Jan 8, 2023

note, docs requested for ANI columns 😓 #2367 (comment)

@bluegenes
Copy link
Contributor

note that we should now also update these in the rust layer, e.g. https://github.com/sourmash-bio/sourmash/blob/latest/src/core/src/index/mod.rs#L57-L64

bluegenes added a commit that referenced this issue Mar 12, 2024
…stead of name (#3078)

This PR enables loading from gather lineages files that contain
'match_name' instead of name. Rationale:
- we generally plan to replace 'name' with 'match_name' in gather output
(#1555)
- branchwater plugin's fastmultigather already uses 'match_name'

---------

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
5.0 issues to address for a 5.0 release
Projects
None yet
Development

No branches or pull requests

3 participants