Rasterization changes the max-slew-rate to an effective max slew rate

In SystemSpecs, when calculating

minmax_risetime = self.get_shortest_rise_time(self.max_grad)
max_slew = self.max_grad / minmax_risetime
>> max_slew < self.max_slew

This is intentional as the rasterization makes sure the slew rate is not exceed. Consequtive calculations should allways use the effective slew rate. Would it make sense to define SystemSpec.max_slew as shown above?

@mcgrathc