I changed the function name to better match the camelCase, but left the
function in so that anyone wanting to develop filter coefficients might use
Matlab to analyse the change in frequency content of their trajectories. I
found it useful. Perhaps I should just rip it out along with all references
to it. Although, I find it reassuring to plot the trajectory both before
and after the filter. Please let me know what you suggest. I feel strongly
both ways:)


On Fri, May 30, 2014 at 1:48 AM, G.A. vd. Hoorn <notifications@github.com>
wrote:

> In industrial_trajectory_filters/src/smoothing_trajectory_filter.cpp:
>
> > + *********************************************************************/
> > +
> > +/* Author: Chris Lewis */
> > +
> > +#include <industrial_trajectory_filters/smoothing_trajectory_filter.h>
> > +#include <console_bridge/console.h>
> > +#include <moveit/robot_state/conversions.h>
> > +#include <stdio.h>
> > +
> > +#include <ros/ros.h>
> > +#include <ros/console.h>
> > +
> > +namespace industrial_trajectory_filters
> > +{
> > +  namespace{
> > +void  print_tragectory_to_matlab_format(std::string filename, std::string mat_name, robot_trajectory::RobotTrajectory& rob_trajectory)
>
> Typo?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/ros-industrial/industrial_core/pull/77/files#r13218363>
> .
>