Viewing a single comment thread. View all comments

thiru_2718 t1_iwlth7x wrote

You can add "velocity" and "time" as separate features, but if there's a known physical relationship between the two, you can encode that relationship more efficiently by combining them into a single feature. So for example, you can capture the kinematics of the data by adding a "position" feature where "position_i+1 = velocity_i+1 * (time_i+1 - time_i) + position_i".

2

snairgit OP t1_iwlw6g3 wrote

This is an interesting thought. They do have some inherent relationship but defining it would be a problem. But I'll look into it, thanks for your input.

1