-
Notifications
You must be signed in to change notification settings - Fork 18
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
Clarify descriptions of --normalize-by-specimen
flag functionality in scripts/classif_rect.py
#312
Conversation
I've realized this functionality was only in the the |
…rminology to be more intuitive
…, and more consistent. Everything forks on whether or not specimen map is specified.
This task ballooned a bit into a bit of an overhaul for increased consistency and ease of understanding what the output/input options are. See branch 312-classif-rect-average-frequency for the current status. @nhoffman - There are a few other things we chatted about that would be nice, but these might have to wait. I can open up separate ticket(s) for those though. |
…d, tax_name or rank (this could break things, and would be silly anyway).
@metasoarous - thanks for this - is this ready for a pull request? I'm updating the pipeline (depends on changes already in dev) and it would be nice to start using this. If not, no problem - I can always grab the script and use it standalone. |
@matsen - Noah and I just chatted about this. While these changes are ready to be merged, they are breaking changes. Since we've also renamed the script (as |
Sounds great! On Thu, Nov 21, 2013 at 1:40 PM, Christopher Small <notifications@github.com
Frederick "Erick" Matsen, Assistant Member |
Good to merge? |
@nhoffman shall I just click on the big green button? |
Yes! On Mon, Feb 3, 2014 at 10:14 AM, Erick Matsen notifications@gh.neting.ccwrote:
|
Clarify descriptions of `--normalize-by-specimen` flag functionality in scripts/classif_rect.py
The functionality in question is much easier to understand if "normalized tally" for a specimen is described as the "frequency" of some taxon for that specimen. As such, the "normalized_tally" output in by_taxon can be described as an "average_frequency".