Skip to content
This repository has been archived by the owner on Mar 17, 2019. It is now read-only.

remove the option for "include gravity" from physics apps #1106

Open
AlanRosenthal opened this issue Jun 29, 2014 · 2 comments
Open

remove the option for "include gravity" from physics apps #1106

AlanRosenthal opened this issue Jun 29, 2014 · 2 comments

Comments

@AlanRosenthal
Copy link
Contributor

@fgmart @ivanrudnicki

We should remove the option for adding/removing gravity from physics apps. It's slightly confusing and endusers don't fully understand what it means. It should just be regular acceleration (gravity included).

@bdonald25
Copy link
Contributor

When would acceleration including gravity be more useful than acceleration without gravity? I found it hard to interpret the data from Canobie that included gravity because the phones were constantly changing orientation.

If a user is accelerating in a horizontal line, at 10m/s, it makes sense for the magnitude to show 10 m/s. If gravity is included the value, it is now 19.8 m/s. If the user was accelerating up at 10 m/s the magnitude would show 0.2 m/s. (10 up and 9.8 down would cancel out).

When you would want the magnitude to be 0.2 in that situation instead of 10 m/s? 10 is the users total acceleration not 0.2.

@Rajia
Copy link
Contributor

Rajia commented Jun 29, 2014

Having gone on the canobie field trip with Bobby I completely agree. The data is a lot easier for the students to comprehend without taking into account gravity.

Rajia

On Jun 29, 2014, at 12:54 PM, "bdonald25" <[email protected]mailto:[email protected]> wrote:

When would acceleration including gravity be more useful than acceleration without gravity? I found it hard to interpret the data from Canobie that included gravity because the phones were constantly changing orientation.

If a user is accelerating in a horizontal line, at 10m/s, it makes sense for the magnitude to show 10 m/s. If gravity is included the value, it is now 19.8 m/s. If the user was accelerating up at 10 m/s the magnitude would show 0.2 m/s. (10 up and 9.8 down would cancel out).

When you would want the magnitude to be 0.2 in that situation instead of 10 m/s? 10 is the users total acceleration not 0.2.

Reply to this email directly or view it on GitHubhttps://github.com//issues/1106#issuecomment-47460160.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants