New Gear ratio Calculator

[MY1]

I have noticed that while @Sariel has already created a web-based gear ratio calculator I myself have found some things that I dislike about it. First Sariel's gear ratio calculator calculates everything as being something:1 or 1:something, this makes it so that there are no decimals, while I'm sure he has intentionally done this, many gear ratios in real life are calculated as being something:1 My gear ratio calculator calculates everything as being something:1. 2nd, this isn't a big deal but sometimes people like to 3d print their own gears which are compatible with lego. Sariel's calculator is limited to only gears made by lego. whereas mine the user must enter in how many teeth are on the driver and follower gears. like I said this isn't really a problem but it leads me to my third and final point. 3rd Sariel's gear calculator does not yet have the new red differential gear piece 65413 as an option. but mine I have a little note at the top saying that the gear has 28 teeth. with that information, you can then enter in that gear. here is a link to my gear ratio calculator https://py3.codeskulptor.org/#user305_U6IzdyXIAHcj1Si.py. my original plan was to create a program in my ti 84 calculator that could do this, because a calculator is much easier to access then logging into my computer and opening up Sariels gear ratio calculator but as I realized that calculators use a very different language then what im used to so I decided to put first write the program in python then translate it. so while it doesn't look anywhere as neat as Sariel's it gets the job done. to run the program simply hit the green run button in the upper left and it will start. Please tell me what you think I could improve or changehttps://py3.codeskulptor.org/#user305_U6IzdyXIAHcj1Si.py

Edited December 10, 2020 by MY1

[Void_S]

Personally, I didn't observe any difference in the output result between your and Sariel's programs...

Could you explain in detail the "something:1 or 1:something" problem you're talking about?

[MY1]

Just now, Void_S said:

Personally, I didn't observe any difference in the output result between your and Sariel's programs...

Could you explain in detail the "something:1 or 1:something" problem you're talking about?

so if you have a 24t driver gear with a 8t follower gear on Sariels the gear ratio would be 1:3 whereas on mine it would be .333333333:1 both of these gear ratios are the same however i have found that more often people tend to use decimals

[TeamThrifty]

I think you may have solved a problem that doesn't exist?

Select 24 and 8 on @Sariel 's app and it returns 1:3 which makes perfect sense, 0.33333:1 as your suggested alternative doesn't.... its technically the same, but is not intuitive. i see no benefit from your suggestion? 

 

[howitzer]

Sariel has also made an app for Android phones for gear ratio calculations, which can be found in the Play store. I haven't tested it because I try to avoid installing apps that are not absolutely necessary but unless you're an Iphone-user, you might find it interesting.

I took a look at your Python and well, it does the job but there's so much more to be done to make it actually usable, like a proper interface. It should allow input of multiple consecutive gears, and preferably have pictures of officially released gears for user to easily make sure they have entered the correct gears in correct order, and it should allow editing the gear lineup etc. and all this should be happening with mouse. Custom gear teeth number might be a nice additional feature too, but I suspect vast majority of potential users will stick to just Lego gears.

[nerdsforprez]

40 minutes ago, TeamThrifty said:

and it returns 1:3 which makes perfect sense, 0.33333:1 as your suggested alternative doesn't.... its technically the same, but is not intuitive.

 

Perhaps this is a language/metric used thing.  For the record, I love Sariel's calculator.  Great tool.  But, in terms of this language, I have always hated the notation (ex: 24t driver gear with a 8t follower gear = 1:3 ratio).  Stating it .33333:1 makes MUCH more sense to me.  So, this whole idea of what is intuitive versus not-intuitive may be location/language specific.  Not sure there is any set standard here.  For the record, I live in the US.  

But agree not sure if this is a meaningful change.  Even if the metric used in Sariel's calculator is not intuitive to me it is good for me to mentally work out the solution both ways.  Helps with overall understanding IMO.  

 

 

[doug72]

I use the old fashion way using  pen & paper with a calculator for all my GBC gear ratios.

[TeamThrifty]

23 minutes ago, nerdsforprez said:

his whole idea of what is intuitive versus not-intuitive may be location/language specific

Good point

[MY1]

1 hour ago, howitzer said:

I took a look at your Python and well, it does the job but there's so much more to be done to make it actually usable, like a proper interface. It should allow input of multiple consecutive gears, and preferably have pictures of officially released gears for user to easily make sure they have entered the correct gears in correct order, and it should allow editing the gear lineup etc. and all this should be happening with mouse. Custom gear teeth number might be a nice additional feature too, but I suspect vast majority of potential users will stick to just Lego gears.

ya I agree this setup isn't ideal, Sariels is probably more user friendly, to have pictures and stuff I would have to make a website and incorporate the program into the website. code sculptor is simply a tool that is used for running some code, its not really made for people to go to it as i have attempted. but as I said I had originally meant for this to be a calculator program which I could run on my TI-84 plus ce. 

 

1 hour ago, nerdsforprez said:

Perhaps this is a language/metric used thing.  For the record, I love Sariel's calculator.  Great tool.  But, in terms of this language, I have always hated the notation (ex: 24t driver gear with a 8t follower gear = 1:3 ratio).  Stating it .33333:1 makes MUCH more sense to me.  So, this whole idea of what is intuitive versus not-intuitive may be location/language specific.  Not sure there is any set standard here.  For the record, I live in the US. 

I had never actually thought of it as being a language thing/ metric thing. for me if i search for the gear ratios of a Ford Mustang or about any other car the result is something like .3333:1. I too live in the US so for me i have just never seen gear ratio as being 1:3 in real documentation