Nitpicking, but wouldn't it be 300 Gs of deceleration? I know the math is basically the same, but technically the words a mean different things
And if you say “well one way I fly to the back of the tram and the other the front” You’re arbitrarily associating “front” with decelerate and “back” with accelerate.
300gs is 300gs regardless of the direction vector of the component.
> So for sure a system's design must consider more than just the magnitude of acceleration.
What else would you need to consider? Acceleration up? Down? Left? 20%x,30%y,40%z? There’s an infinite number of directions.
Deceleration is a useful but non-technical term, like vegetable. A tomato is a fruit which is a tightly defined concept, but it is in this loose category of things called vegetables. It's still useful to be able to call it a vegetable.
From a physics perspective all changes in motion (direction and magnitude) are acceleration, and it's correct to say the designers had to consider acceleration in most (all?) directions when designing the tram. This is including gravity's, as they tend to give you seats to sit on, rather than velcro panels and straps like on space ships.
It is useful to say to your friend in the pub that you got thrown out of your seat due to the tram's heavy deceleration, rather than give a precise vector.
It's not like you can tell whether you're going slow or fast, in one direction, the other direction, or even just standing still, if you close your eyes.
If acceleration can be negative, so can speed. A negative speed with negative acceleration would not imply deceleration?
If you measure the same object's velocity from a spaceship traveling through the solar system, you'll get a different answer from what we measure from Earth.
That's why physics doesn't distinguish between acceleration and deceleration. What looks like acceleration in one frame looks like deceleration in a different frame.