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.

Sign up for GitHub

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

Jump to bottom

Use separate pipeline for extraction of features from training samples. #367

Open
damellis opened this issue Sep 9, 2016 · 3 comments
Open

Use separate pipeline for extraction of features from training samples. #367

damellis opened this issue Sep 9, 2016 · 3 comments
Labels
bug component-live stream component-pipeline component-training data core

Comments

@damellis
Copy link
Owner

damellis commented Sep 9, 2016

Currently, when in "feature view" (i.e. displaying live data and training samples as features), the features are dynamically calculated from the training samples when navigating between training samples. This uses the live pipeline, which creates glitches in the plot of the features of the live data. We should probably clone the pipeline and use the clone from calculating features of the training samples (and reset it before use).
@damellis damellis added this to the Post-Workshop Cleanup milestone Sep 9, 2016
@damellis
Copy link
Owner Author

@nebgnahz this was fixed by d99dbf7 right?

@nebgnahz
Copy link
Collaborator

I don't think so. It was planned but not fixed.

@damellis
Copy link
Owner Author

Sorry, my mistake! I was confusing this with #337

@damellis damellis removed this from the Post-Workshop Cleanup milestone Sep 30, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug component-live stream component-pipeline component-training data core
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@damellis @nebgnahz