There are currently two classes for FSR ("FSR" and "FSR_Regressed"). FSR_Regressed seems to be specialized for the toe in instances of ankle controllers that seek to estimate the proportional ankle joint moment (PJMC). However, currently there are only two objects for FSRs (_heel_fsr & _toe_fsr), which is unideal if you want to run multi-joint (simultaneous hip and ankle control) or a non-ankle based control scheme that relies on _toe_fsr (i.e., for % gait cycle estimation).

Would it be possible to add a third object specific for FSR_Regressed (i.e., _toe_fsr_regressed) so that there is access to the raw fsr signal for the toe (FSR _toe_fsr) and the regressed version (FSR_Regressed _toe_fsr_regressed) to avoid confusion and maximize flexibility?