Power and torque made simple

Power and torque, as with many topics, are simple to understand, if explained concisely.

Force is mass times acceleration. (translation)
Torque is force times arm distance. (rotation)
(note: at that arm distance Force = Torque)

Work is Force times displacement. (translation)
Work is Torque times displacement. (rotation)
(note: displacement along the circular path)

Power is Work divided by Time.

You can't always overpower something simply by ;increasing power', the force component of power has to exceed that of the load.

Microwave power density

Simply stating wattage of a microwave seems inadequate. Microwaves come in different sizes. A 1500 watt small microwave has a higher power density than does a 1500 watt large microwave. Size being the internal cooking space. They should be rated with say watts/cubic meter, to indicate how long it will take for the meal to cook.

Efficient traffic convoy system

Starting and stopping at stoplights is a waste of energy, also it takes time for long group of cars to accelerate once stopped at a stoplight.

What would be better is to bunch up vehicles into a convoy all following the nearest 'virtual pace car'. Cars just ahead of the virtual pace car would slow down to get closer to the pace car, while cars behind the virtual pace car would speed up to catch up.

Within limits of course, never go above the speed limit to catch up, rather simply slow down to the next virtual pace car behind them.

The virtual pace car would be synchronized with the stoplights; the lights turn green just as it approaches a light. The cars will be bunched together so it wouldn't have to stay green for long to get a bunch of cars through. This will let cross traffic enter more often.

The virtual pace car can simply take a form of signs that simply indicate whether you should slow down or speed up to catch up to the nearest virtual pace car. Brakes and energy will be saved, smooth driving the whole way!

https://en.wikipedia.org/wiki/Traffic_light_control_and_coordination
https://en.wikipedia.org/wiki/Green_wave Same as convoy idea
https://en.wikipedia.org/wiki/Speed_sign Same as pace car idea

Automatic loudness adjustment

Headphones should be smart. They should automatically sense minimum and maximum loudness of sound input and scale to a set minimum and maximum decibel scale.

Seems that even modern headphones simply amplify by a certain amount, no matter how quiet or loud the result is, ears be damned!

Furthermore volume settings should state decibels, knowing exactly the decibel output of a speaker system.

Summing temperature durations

Highs and lows on weather forecasts only gives a vague sense of the weather. For example, deserts might reach over 100 degrees Fahrenheit, however that's often times counter balanced with very cold nights.

A better sense would be in the form temperature duration.

For example this forecast:
City A high 88, low 70
City B high 100, low 50

One might think city B has hotter weather, but say these are the durations
City A day: 10 hours in the 80s and 14 hours in the 70s
City B day: 1 hour in the 100s, 3 hours in the 90s, 4 hours in the 80s, 4 hours in the 70s, 8 hours in the 60s, 4 hours in the 50s.

Perhaps the integral under a curve could be stated for forecasts, sort of like how much area under a temperature/time curve.

Also for temps over 80degF or so humidity becomes an important factor. 100degF @ 15 humidity is more tolerable than is 80degF @ 85% humidity due to the amount of evaporation of liquid on the skin which has a strong cooling effect.

Proposed Metric Calendar

(link to part 2 http://www.polarjetstream.com/2019/08/proposed-metric-calendar-part-2.html )

See a metric calendar for any month/year using this new JavaScript program (made in 2019 Aug)
https://warpdrive.github.io/JavaScript-Metric-Calendar-2019/metric%20calendar.htm
This calendar is zero based, meaning day of year and day of month both start at zero instead of at 1. You can multiply week by 10 to get the day of year. In fact you can simply forgo months and simply identify days using weeks to the 0.1 precision.

-Always: First day of the month is the first day of the week
-Always: Last day of the month is the last day of the week
-Always: Exactly 3 weeks per month
-Always: Exactly 9 weeks per season
-Always: Day of Month always falls on the same day of week.
-Always: Day of Year simply equals week of year * 10
-Leapday at end of the year as to not disturb the consistent order of a year
-Take 3 days off from work a metric week (off 30% of the days, about the same % as now)
-Matching January 1st of the current calendar to this proposed metric calendar seems best.
-Calendar seasons begin roughly 10 days after the corresponding solstice/equinox (align with months)

January (Winter)
01 02 03 04 05 06 07 08 09 10 (week 1)
11 12 13 14 15 16 17 18 19 20 (week 2)
21 22 23 24 25 26 27 28 29 30 (week 3)

February (Winter)
01 02 03 04 05 06 07 08 09 10 (week 4)
11 12 13 14 15 16 17 18 19 20 (week 5)
21 22 23 24 25 26 27 28 29 30 (week 6)

March (Winter)
01 02 03 04 05 06 07 08 09 10 (week 7)
11 12 13 14 15 16 17 18 19 20 (week 8)
21 22 23 24 25 26 27 28 29 30 (week 9)

April (Spring)
01 02 03 04 05 06 07 08 09 10 (week 10)
11 12 13 14 15 16 17 18 19 20 (week 11)
21 22 23 24 25 26 27 28 29 30 (week 12)

May (Spring)
01 02 03 04 05 06 07 08 09 10 (week 13)
11 12 13 14 15 16 17 18 19 20 (week 14)
21 22 23 24 25 26 27 28 29 30 (week 15)

June (Spring)
01 02 03 04 05 06 07 08 09 10 (week 16)
11 12 13 14 15 16 17 18 19 20 (week 17)
21 22 23 24 25 26 27 28 29 30 (week 18)

July (Summer)
01 02 03 04 05 06 07 08 09 10 (week 19)
11 12 13 14 15 16 17 18 19 20 (week 20)
21 22 23 24 25 26 27 28 29 30 (week 21)

August (Summer)
01 02 03 04 05 06 07 08 09 10 (week 22)
11 12 13 14 15 16 17 18 19 20 (week 23)
21 22 23 24 25 26 27 28 29 30 (week 24)

September (Summer)
01 02 03 04 05 06 07 08 09 10 (week 25)
11 12 13 14 15 16 17 18 19 20 (week 26)
21 22 23 24 25 26 27 28 29 30 (week 27)

October (Fall)
01 02 03 04 05 06 07 08 09 10 (week 28)
11 12 13 14 15 16 17 18 19 20 (week 29)
21 22 23 24 25 26 27 28 29 30 (week 30)

November (Fall)
01 02 03 04 05 06 07 08 09 10 (week 31)
11 12 13 14 15 16 17 18 19 20 (week 32)
21 22 23 24 25 26 27 28 29 30 (week 33)

December (Fall)
01 02 03 04 05 06 07 08 09 10 (week 34)
11 12 13 14 15 16 17 18 19 20 (week 35)
21 22 23 24 25 26 27 28 29 30 (week 36)

Remainder days (not part of a month or week)
01 02 03 04 05 (06 if a leapyear)

Metric Week
Sun Mon Tue Wed Thu Fri Sat Off1 Off2 Off3

Same calendar, except days/weeks start with zero

January (Winter)
00 01 02 03 04 05 06 07 08 09 (week 0)
10 11 12 13 14 15 16 17 18 19 (week 1)
20 21 22 23 24 25 26 27 28 29 (week 2)

February (Winter)
00 01 02 03 04 05 06 07 08 09 (week 3)
10 11 12 13 14 15 16 17 18 19 (week 4)
20 21 22 23 24 25 26 27 28 29 (week 5)

March (Winter)
00 01 02 03 04 05 06 07 08 09 (week 6)
10 11 12 13 14 15 16 17 18 19 (week 7)
20 21 22 23 24 25 26 27 28 29 (week 8)

April (Spring)
00 01 02 03 04 05 06 07 08 09 (week 9)
10 11 12 13 14 15 16 17 18 19 (week 10)
20 21 22 23 24 25 26 27 28 29 (week 11)

May (Spring)
00 01 02 03 04 05 06 07 08 09 (week 12)
10 11 12 13 14 15 16 17 18 19 (week 13)
20 21 22 23 24 25 26 27 28 29 (week 14)

June (Spring)
00 01 02 03 04 05 06 07 08 09 (week 15)
10 11 12 13 14 15 16 17 18 19 (week 16)
20 21 22 23 24 25 26 27 28 29 (week 17)

July (Summer)
00 01 02 03 04 05 06 07 08 09 (week 18)
10 11 12 13 14 15 16 17 18 19 (week 19)
20 21 22 23 24 25 26 27 28 29 (week 20)

August (Summer)
00 01 02 03 04 05 06 07 08 09 (week 21)
10 11 12 13 14 15 16 17 18 19 (week 22)
20 21 22 23 24 25 26 27 28 29 (week 23)

September (Summer)
00 01 02 03 04 05 06 07 08 09 (week 24)
10 11 12 13 14 15 16 17 18 19 (week 25)
20 21 22 23 24 25 26 27 28 29 (week 26)

October (Fall)
00 01 02 03 04 05 06 07 08 09 (week 27)
10 11 12 13 14 15 16 17 18 19 (week 28)
20 21 22 23 24 25 26 27 28 29 (week 29)

November (Fall)
00 01 02 03 04 05 06 07 08 09 (week 30)
10 11 12 13 14 15 16 17 18 19 (week 31)
20 21 22 23 24 25 26 27 28 29 (week 32)

December (Fall)
00 01 02 03 04 05 06 07 08 09 (week 33)
10 11 12 13 14 15 16 17 18 19 (week 34)
20 21 22 23 24 25 26 27 28 29 (week 35)

Remainder days (not part of a month or week)
01 02 03 04 05 (06 if a leapyear)

Metric Week
Sun Mon Tue Wed Thu Fri Sat Off1 Off2 Off3

Time to metric-size time

Time would be so much simpler if we would just stick with Earth rotating around itself (day) and Earth rotating around the Sun (year.) Just know that there are about 365.25 days per year. That's all you have to remember, other than the standard metric prefixes.

What are we using now? Year, month, week, day, hour, minute, second... aye yay yay... what a mess!!! Not only do you have to know that there are about 365.25 days per year, but also:
-12 months per year (months vary 30 or 31 days, sometimes 28 or 29 days!!!)
-7 days per week (weeks don't even evenly divide into months!!!)
-24 hours per day
-60 minutes per hour (1440 minutes per day)
-60 seconds per minute (86400 seconds per day)

Similar to the distance mess (inch, foot (12 inches), yard (3 feet), mile E(5280 feet) )
Or the volume mess (teaspoon, tablespoon, ounce, cup, gallon)

https://en.wikipedia.org/wiki/Metric_prefix

Easiest method (forget weeks and months)
Date: (Year) and the whole part of (Day of Year)
Time:  the fractional part of Day of Year

For example: date 2017: 21.5 is 2017 January 21 at 12pm.

Multi-days
Week based on day: Instead of a 7 day week, replace it with 1 deca-day (10 days), with about 36.5 deca-days per year. Maybe have 36 deca-days with 5 days remainder at the end of the year.
Week based on year: Instead of about 52 weeks a year, replace with 20 milli-years (about 7.3 days), with exactly 50 x 20 milli-years per year.

Month based on day: 3 deca-days (30 days) with about 12 deca-days per year with 5 days remainder days at the end of the year.
Month based on year: 10 months per year which would be exactly 1 deci-year (about 36.5 days.) Maybe have 10 36-day months, then 5 day remainder at the end of the year.

Or perhaps just dump the notion of weeks and months altogether and just go by x amount of deca-days or deci-years.

Sub-days
1 day is 86400 sec (24 hrs)
0.1 day = deci-day = 8640 sec (2.4 hrs)
0.01 day = centi-day = 864 sec (14.4 min)
0.001 day = milli-day = is 86.4 sec (1.44 min)
0.0001 = 100 micro-days = 8.64 sec
0.00001 = 10 micro-days = 0.864 sec

All sub-day units are evenly divisible with each-other with simple metric.

Calendars/Clocks can easily switch between the 2 systems.

00000(sec) 0.0 (days) 0.0 (24hrs)
08640(sec) 0.1 (days) 02.4 (24hrs)
17280(sec) 0.2 (days) 04.8 (24hrs)
25920(sec) 0.3 (days) 07.2 (24hrs)
34560(dec) 0.4 (days) 09.6 (24hrs)
43200(sec) 0.5 (days) 12.0 (24hrs)
51840(sec) 0.6 (days) 14.4 (24hrs)
60480(sec) 0.7 (days) 16.8 (24hrs)
69120(sec) 0.8 (days) 19.2 (24hrs)
77760(sec) 0.9 (days) 21.6 (24hrs)
86400(sec) 1.0 (days) 24.0 (24hrs)

Time duration is easy to calculate

If range remains in a year then use day of year (using fractional days)
For example, time between 2002 Jan 01 00:00hrs and 2002 Feb 01 12:00 hrs.
In metric time that would be 32.5 - 2 = 30.5 days.

If range spans multiple years then convert to years (using fractional years)
2002 Feb 01 12:00hrs = 32.5 day of year = about 2002.0890 years (32.5/365.25)
2003 Feb 20 00:00hrs = 51 day of year = about 2003.1396 years (51/365.25)
In metric time that would be 2003.1396 - 2002.0890 = 1.0506 (383.73165 days)

(leap year days need to be added in for some cases)
(timecards do use decimal hours)

Related links
https://en.wikipedia.org/wiki/Metric_time
https://en.wikipedia.org/wiki/Decimal_time

Come on people, use all of the Metric Prefixes!

http://www.space.com/36504-huge-peanut-shaped-asteroid-2014-jo25-earth-flyby.html
1.8 million kilometers ...
Are we stuck with using kilo only? Are mega and giga bad words? It's really simple for those whom don't fear the words mega and giga.
1.8 * 1,000,000 * 1000 = 1,800,000,000 meters.

Using the proper prefix ( https://en.wikipedia.org/wiki/Metric_prefix )

1.8 giga meters.

That's easier to type and say than 1.8 million kilometers, or 1.8 mega kilo. Please, use all of the prefixes, that's what they're there for!

Each prefix increases by 1000, or 10^3
1000 meters in 1 kilo-meter
1000 kilo-meters in 1 mega-meter
1000 mega-meters in 1 giga-meter.