-
Notifications
You must be signed in to change notification settings - Fork 11
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
Disable extra fields #54
Comments
@redhog , I expect that these are all the values that get used in computing the fishing score. I don't see any reason they need to be output at the end of that stage. Is there a way to strip them at the output, or only insert them in a copy of the pipeline data so they don't get output at the end of the stage? |
I don't think the vessel-scoring library should remove them, but feel free to strip anything starting with measure_* apart from measure_new_score in an iterator filter in the pipeline itself. This would be the place: https://github.com/SkyTruth/benthos-pipeline/blob/master/benthosp/pipe_classify.py#L59 |
@redhog I disagree. It it not a question of whether the scoring library On Mon, Aug 1, 2016, 18:36 Egil Möller [email protected] wrote:
|
@redhog I agree with @pwoods25443 from a design standpoint. |
@bitsofbits @redhog: Vessel scoring adds a bunch of extra information to the output messages that the pipeline doesn't need and increases the output file size by
50%
. Can we get an option to turn it off, or ideally leave it off by default?here is the same day at 3 different points in the pipeline.
The text was updated successfully, but these errors were encountered: