# Additional statistics (linear regression)

**URL:** https://discourse.flucoma.org/t/additional-statistics-linear-regression/562
**Category:** New Ideas
**Created:** [July 10, 2020, 10:53pm UTC](https://discourse.flucoma.org/t/additional-statistics-linear-regression/562 "2020-07-10T22:53:03Z")
**Posts on this page:** 1
**Showing post:** 8

<div class="post-metadata">

### Author: ![rodrigo.constanzo](https://discourse.flucoma.org/user_avatar/discourse.flucoma.org/rodrigo.constanzo/32/12_2.png) [@rodrigo.constanzo](https://discourse.flucoma.org/u/rodrigo.constanzo)
#### Post date: [July 11, 2020, 11:38am UTC](https://discourse.flucoma.org/t/additional-statistics-linear-regression/562/8 "2020-07-11T11:38:11Z")

</div>

> [@b.hackbarth](#):
>
> Yeah, omitting part of the array as a time in seconds (rather that a percentage) might make more sense here.

Or maybe a combination where it’s a fixed % unless the segment is above (or below) a certain duration, in which case it defaults to time values.

Or to get even fancy-pants-er can have it automagically find the “steady state” via a piecewise linear approximation, so if there are extreme(ish) trajectory changes at the edges, those get disregarded, and if there aren’t, it takes all the frames.

> [@b.hackbarth](#):
>
> I cannot see some of the links you posted in your initial post (“Oops! That page doesn’t exist or is private”). Maybe the discoursebot is still getting to know me. However can I earn its trust?

I guess @tremblap bumped you into the dev group, which is where some of those point (as it turns out).

---

_[View the full topic](https://discourse.flucoma.org/t/additional-statistics-linear-regression/562)._