Feature/aggregation #116
Open
Feature/aggregation #116
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…sifications is failing
…ations from 01 notebook
…batch_aggregation function
…ication table but then commenting it out because we already have subject ID as an option
…ject ID indicating something has gone wrong internally
…aggregate classifications
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New notebook! 03 notebook will pull classifications from Zooniverse - I also modified utils.py
Notebook 01 will need to be rerun to send a subject set that has the appropriately anonymized objectIds now that utils has been modified.
I'm wondering if we want to obscure some of the functions in the 03 notebook into utils.py or if it's best to keep them exposed since they're doing the cool aggregation things.