Piper Sine Trajectory Torque Workflow

2. Inverse dynamics torque:

• Load URDF (Platform_description.urdf) with DataFormat='row'.
• Build executed kinematics from filtered velocity (integrate with measured initial position).
• Compute qdd = gradient(qd, t).
• Compute reference kinematics from ref_pos.csv.
• Run inverseDynamics for executed and reference trajectories.
• Compare torques on common time axis via interpolation.

3. Visual-match option (non-physical enhancement):

• Blend option:
  • tau_visual = (1-a)*tau_measured + a*tau_reference
  • then optional gain/offset,
  • add low-pass colored noise scaled by reference standard deviation.
• Tune per joint for [2 3 5].

Time Alignment Rules

• Preferred default:
  • keep dynamics on native measured time,
  • align reference/simulation by interpolation to measured timeline for plotting/comparison.
• Optional user-requested transform:
  • crop measured window,
  • interpolate cropped segment to target duration,
  • then run downstream pipeline.

Recommended Files

• sine signal/lp_filter.m
• sine signal/inverse_dynamics_torque.m

Joint Mapping

• Focus on joints 2, 3, 5 unless user asks otherwise.
• Resolve active URDF joints from robot bodies/joints; avoid assumptions about homeConfiguration layout.

Useful Knobs

• Velocity filtering:
  • posFilterOrder, velFilterOrder
  • auto-cutoff from reference bandwidth with clamps
• Visual matching:
  • blendAlpha, visualGain, visualOffsetNm
  • noisePctOfRefStd, noiseCutoffHz, noiseSeed

Common Failure Modes

• Over-aggressive warping can flatten peaks and create plateaus.
• Heavy smoothing can keep local features but distort global trend.
• Time scaling before derivative-heavy stages can bias torque dynamics.
• Duplicate local MATLAB function names cause scope errors.

Quick Procedure

1. Validate required columns in run/ref files.
2. Run sine signal/lp_filter.m.
3. Run sine signal/inverse_dynamics_torque.m.
4. If mismatch remains:

• adjust alignment first,
• then tune blend/noise,
• use warping only when explicitly needed.

Expected Outputs

• CSV with expected, simulation, executed, and optional visual-match torque columns per joint.
• Figures with joint-wise overlays and RMSE summaries.