Klaus 65 integrate bout stats

[SkepticRaven]

Integrates newly added bout statistics into nextflow pipeline.
Depends on KumarLabJax/JABS-postprocess#51 and KumarLabJax/JABS-postprocess#50

JABS feature tables will now include:

• bout count
• average bout length
• sum of distance traveled (leaves "average" as another column)
• latency first prediction
• latency last prediction
• distance_cm_threshold: distance calculated only when motion is > 5cm/s
• distance_cm_seg: distance calculated from segmentation prediction (distance_cm is from keypoint convex hull)

New JABS heuristic classifiers:

• Locomotion in periphery -- activity bouts in periphery
• Locomotion in corner -- activity bouts in corner

Additional tweaks:

• time column name changed from "avg" to "sum" to properly indicate that the operation is a sum

[keithshep]

curious because _stats_sample_count is not like the rest. Is this intentional?

[bergsalex]

It's supposed to signify pseudo private.

[SkepticRaven]

Yes. _stats_sample_count is an internal value that should not be used as a feature by the end-user. The difference in style is intended to add caution to the reader (and hopefully those familiar with pythonic style an indicator to not touch it).

[keithshep]

I feel like it would be good to make a configurable param (defaulted to 5) or if not appropriate to be a param, a constant (well... as close as python gets to constants anyway)

[SkepticRaven]

Agreed. The actual change is to make is detect-able from the input table data (and not a param). Right now, there is implied coupling of this script where the input summary table is 5-minute bins.