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

thoughts on adding more details to search, gather, and lca gather output. #410

Open
ctb opened this issue Feb 20, 2018 · 0 comments
Open

Comments

@ctb
Copy link
Contributor

ctb commented Feb 20, 2018

I've been trying to think about how to allow people (including ourselves :) to dig into results more - in part because I think it helps them understand what's going on.

We're making some progress, e.g. the latest sourmash lca gather output includes some annotation of duplicate hits. But I'd like more details, esp in this situation - right now it's hard to figure out what duplicate hits mean, are, etc.

So I brainstormed a bit today and here are a few thoughts.

  • by default, we could enable --details, which would automatically and silently output details to a text file perhaps via a details() logging function.
  • this text file could be named something unique (maybe using a uuid?) so as to avoid append conflicts when multiple things are being run in the same directory;
  • then this file could contain all of the gory details around what is being loaded, etc;
  • maybe put it in a .sourmash-output directory or something?

cc #271 (long running queries UX improve), #258 (output stuff to disk)

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

1 participant