Early this morning, we released a patch and a couple of new additions that apply to both Smashrun and Smashrun Pro users. Let’s start with the new stuff!
Hide data before a certain date.
If you’ve ever taken an extended break from running or if you’ve ever used an app/device for a period of time that was uncalibrated/had erroneous data, hiding your runs before a certain date will help you “clean up” the stats displayed on your dashboard. You can set the date from your settings > profile page.
For example: the dashboard on the left shows long gaps in “Miles per month”. By setting a minimum date to display stats, the revised dashboard on the right zooms in on the consistent data and automatically updates all the summary details.
If you’re a Smashrun Pro user, hiding data before a certain date will also flow through to the Analyze pages so it will affect your Pace Trends graph and the Training Bands. It’s tremendously useful if you’ve got suspicious data in the past that you’d like to ignore.
For example: these Training Bands reflect 6 years of training history. It includes training gaps, periods of training while injured, uncalibrated footpod data, etc.
Here are the same Training Bands that only include data from 2013 to today, which is more representative of current fitness level and more pertinent to more recent training periods.
Enter Resting Heart Rate to calculate Heart Rate Reserve (HRR).
We’ve had a few Smashrun Pro users point out that looking at heart rate distribution based on max HR is far less accurate as a measure of training intensity than using heart rate reserve. As a result, we’ve added a field for resting heart rate within the settings > profile page. For many, the changes could be quite significant depending on the accuracy of your resting heart rate and max heart rate but, you can always edit both fields since they’re likely to change over time.
HRR will be reflected in all heart rate distribution buckets both within the pro maps and in the Training Bands.
SSL for login and account pages.
In addition to Smashrun’s existing security measures, SSL has been added to logins, new registrations, and account settings pages.
Updated the Garmin Importer.
Recent changes to Garmin Connect revised their authentication procedures so we had to update the way Garmin data is being imported.
Fixed goal setting for subsequent months.
There was a weird caching issue that was causing January’s mileage to appear as part of the mileage for February’s goals. That should no longer happen.