The thumbnail image for this video has been updated - thumbnail added by eric3579.

I think that at best this would be applicable only to the very lightest of electric vehicles (something in the "motorcycle" weight class, even half a ton is probably too heavy), and I have my doubts about even those, even when completely disregarding the sideways forces.

With a system like this you do not want more than a few cm (about an inch, at a guess) of suspension travel from when the car is lifted in air to the car at rest (= 1G vertical load), just from the weight of the car compressing the springs. If you have more the springs (which the loops naturally are) have to compress a lot with each revolution, which strains them, heats them, isn't good for rolling resistance, etc.

If we assume a 1000 kg car with a 50/50 weight distribution, to get about 2 cm of suspension travel the spring stiffness would be about comparable to a high level GT racing car. Comparing to high level sports cars, the street going Porsche 911 GT3 RS car, which is regarded as a pretty stiff, racy and track oriented vehicle has something in the region of three times that much travel, a normal commuter car can have way over 10 cm due to soft, comfort oriented springs.

So you can't spring a proper car with just these because it'd require it to be too stiff (also I can foresee shock absorption issues). Another problem is the 360 degree springy nature of it. You really don't want car tyres to move much aside from up and down. These have the problem that when you brake, the forces will try to push the axle forwards in relation to the wheel (i.e. the wheel moves backwards while braking), and the reverse when accelerating. You'd be (possibly) drastically changing the wheelbase of the car during acceleration and braking, which could have catastrophic results for handling in extreme situations. Many if not most cars these days are capable of braking at over 1 G, as long as they have decent tyres, so the front-back movement could be bigger than the up-down movement.

So yeah, doesn't really sound like a workable solution as the ONLY spring system on a car. Having some springiness in the tyres (either in the wheel itself of just having larger profile tyres, like we used to back in the day) can be helpful for comfort and even handling in some cases, but springing the car only via the wheels isn't a good idea, you really want to be able to control the wheels better than that.

The thumbnail image for this video has been updated - thumbnail added by blackfox42.

He said an average of 150 times larger. That seems ... unlikely. 150 percent, maybe -- and still a statistically significant increase.

A quick google search suggests yellowfin tuna commonly range from 40-150cm long, and up to 70kg in weight/mass. If they are close to the "average" of 150 (times? or percent?) larger, the species would have started out at about a half kilogram MAX (more like a small trout) if "size" is determined by mass. Or about 1/4 to 1 cm long (like half a guppy) if determined by length.

Both of those make more sense if it was 150% -- that would be early tuna in the range of 50kg (by mass) or 26-100cm (by length).


And then there was the "maximum size increased by 100,000 times" line. By mass, that is like the trout evolving into a blue whale. Yeah, I am guessing that is a percent again. Still means 1000 times bigger, which is massive.


I tried searching YouTube comments to see if anyone else brought this up, but they are YouTube comments. Hah! Silly me, thinking that YouTube comments on something like SciSchow might be at least partially exempt from the "sanity free zone" that pervades YT.

https://openpaymentsdata.cms.gov

it really is quite interesting!
4th column over is Amount. order by clicking the arrow next to it.

we could make a game of this, and find the doctor with the highest payoff!
so far, this one is my highest.

The thumbnail image for this video has been updated - thumbnail added by oritteropo.

This video lacks a lot of salient details.

Yes, the F35 is aiming at the A10 because contractors want jobs (something to do).

However, the strength of the A10 is also its weakness. Low and slow also means that it takes you a long time to get to your troops. Fast jets arrive much sooner (significantly so). A combination of both would be ideal. F35 to get there ASAP, and A10 arriving later to take over.

It's not really worth debating the merit of new fighters. You don't wait for a war to start developing weapons.

Yes, our recent enemies are durkas with small arms, and you don't need an F35 to fight them - but you also don't even need to fight them to begin with - they aren't an existential threat. Terrorist attacks are emotionally charged (well, until they happen so often that you get used to hearing about them, and they stop affecting people), but they are nothing compared to say, a carpet bombing campaign.

The relevance of things like the F35 is to have weapons ready and able to face a large national power, should a nation v nation conflict arise with a significant other nation. In the event that such a conflict ever does, you don't want to be caught with your pants down.

Defense spending costs scale with oversight requirements.

Keep in mind that money pays people. Even materials are simply salaries of the material suppliers. The more people you put on a program, the more that program will cost.

Yes, big contractors make big profits - but the major chunk of their charges is still salaries.

Let me explain what is going on.

Remember the $100 hammers?
In fact, the hammer still cost a few bucks. What cost 100+ bucks was the total charges associated with acquiring a hammer.
Everything someone does in association with acquiring the hammer, gets charged to a charge code that's specific for that task.

Someone has to create a material request - $time.
Someone has to check contracts for whether or not it will be covered - $time.
Someone has to place the order - $time.
Someone has to receiver the package, inspect it, and put it into a received bin - $time.
Someone has to go through the received items and assign them property tags - $time.
Someone has to take the item to the department that needed it, and get someone to sign for it - $time.
Someone has to update the monthly contract report - $time.
Someone has to generate an entry in the process artifacts report, detailing the actions taken in order to acquire the hammer - $time.
Someone on the government side has to review the process artifacts report, and validate that proper process was followed (and if not, punish the company for skipping steps) - $time.

Add up all the minutes here and there that each person charged in association with getting a hammer, and it's $95 on top of a $5 hammer. Which is why little things cost so much.

You could say "Hey, why do all that? Just buy the hammer".
Well, if a company did that, it would be in trouble with govt. oversight folks because they violated the process.
If an employee bought a hammer of his own volition, he would be in trouble with his company for violating the process.
The steps are required, and if you don't follow them, and there is ever any problem/issue, your lack of process will be discovered on investigation, and you could face massive liability - even if it's not even relevant - because it points to careless company culture.

Complex systems like jet fighters necessarily have bugs to work out. When you start using the system, that's when you discover all the bits and pieces that nobody anticipated - and you fix them. That's fine. That's always been the case.



As an airplane example, imagine if there's an issue with a regulator that ultimately causes a system failure - but that issue is just some constant value in a piece of software that determines a duty cycle.

Say for example, that all it takes is changing 1 digit, and recompiling. Ez, right? NOPE!

An engineer can't simply provide a fix.

If something went wrong, even unrelated, but simply in the same general system, he could be personally liable for anything that happens.

On top of that, if there is no contract for work on that system, then an engineer providing a free fix is robbing the company of work, and he could get fired.

A company can't instruct an engineer to provide a fix for the same reasons that the engineer himself can't just do it.

So, the process kicks in.

Someone has to generate a trouble report - $time.
Someone has to identify a possible solution - $time.
Someone has to check contracts to see if work on that fix would be covered under current tasking - $time.
Say it's not covered (it's a previously closed [i.e. delivered] item), so you need a new charge code.
Someone has to write a proposal to fix the defect - $time.
Someone has to go deal with the government to get them to accept the proposal - $time.
(say it's accepted)
Someone has to write new contracts with the government for the new work - $time.
To know what to put into the contract, "requrements engineers" have to talk with the "software engineers" to get a list of action items, and incorporate them into the contract - $time.
(say the contract is accepted)
Finance in conjuration with Requirements engineers has to generate a list of charge codes for each action item - $time.
CM engineers have to update the CM system - $time.
Some manager has to coordinate this mess, and let folks know when to do what - $time.
Software engineer goes to work, changes 1 number, recompiles - $time.
Software engineer checks in new load into CM - $time.
CM engineer updates CM history report - $time.
Software engineer delivers new load to testing manger - $time.
Test manager gets crew of 30 test engineers to run the new load through testing in a SIL (systems integration lab) - $time.
Test engineers write report on results - $time.
If results are fine, Test manager has 30 test engineers run a test on real hardware - $time.
Test engineers write new report - $time.
(assuming all went well)
CM engineer gets resting results and pushes the task to deliverable - $time.
Management has a report written up to hand to the governemnt, covering all work done, and each action taken - documenting that proper process was followed - $time.
Folks writing document know nothing technical, so they get engineers to write sections covering actual work done, and mostly collate what other people send to them - $time.
Engineers write most the report - $time.
Company has new load delivered to government (sending a disk), along with the report/papers/documentation - $time.
Government reviews the report, but because the govt. employees are not technical and don't understand any of the technical data, they simply take the company's word for the results, and simply grade the company on how closely they followed process (the only thing they do understand) - $time.
Company sends engineer to government location to load the new software and help government side testing - $time.
Government runs independent acceptance tests on delivered load - $time.
(Say all goes well)
Government talks with company contracts people, and contract is brought to a close - $time.
CM / Requirements engineers close out the action item - $time.

And this is how a 1 line code change takes 6 months and 5 million dollars.

And this gets repeated for _everything_.

Then imagine if it is a hardware issue, and the only real fix is a change of hardware. For an airplane, just getting permission to plug anything that needs electricity into the airplanes power supply takes months of paper work and lab testing artifacts for approval. Try getting your testing done in that kind of environment.



Basically, the F35 could actually be fixed quickly and cheaply - but the system that is in place right now does not allow for it. And if you tried to circumvent that system, you would be in trouble. The system is required. It's how oversight works - to make sure everything is by the book, documented, reviewed, and approved - so no money gets wasted on any funny business.

Best part, if the government thinks that the program is costing too much, they put more oversight on it to watch for more waste.
Because apparently, when you pay more people to stare at something, the waste just runs away in fear.
Someone at the contractors has to write the reports that these oversight people are supposed to be reviewing - so when you go to a contractor and see a cube farm with 90 paper pushers and 10 'actual' engineers (not a joke), you start to wonder how anything gets done.

Once upon a time, during the cold war, we had an existential threat.
People took things seriously. There was no F'ing around with paperwork - people had to deliver hardware. The typical time elapsed from "idea" to "aircraft first flight" used to be 2 years. USSR went away, cold war ended, new hardware deliveries fell to a trickle - but the spending remained, and the money billed to an inflated process.

-scheherazade

Proof seems to be lacking in your empty non-argument.
Read something not printed by Murdoch.

Wealthiest Pay Higher Taxes With Scant U.S. Economic Harm
http://www.bloomberg.com/news/2014-04-11/wealthiest-pay-higher-taxes-with-scant-u-s-economic-harm.html

"tax increases harm growth is simply false."
http://www.cbpp.org/cms/?fa=view&id=4094

Oh...so it's OK with you to simplify and 'falsify details' significantly by modeling the earth as a perfect sphere, but not ignore the mathematically insignificant and immeasurably small possible movement of the earth in some direction or another due to multiple immeasurably small gravities?! WHAT?!? ;-)

....Um...1 degree on earth is 111.2 KM, there's such a tiny difference (1 cm+-) they are in the same place for all possible measureable purposes, nothing like 1 deg apart. My scientific calculator won't give an answer, 1 deg * (1cm/111.2km) =0.00deg on it. (OK, it's not hard math...1/11120000 deg.) Because of this, yes, they WOULD cross the imaginary line, AND hit the earth at the same time by any possible measurement. If the smallest distance measureable is FAR larger than the distance they differ by, and the smallest time measureable is MUCH longer than the difference in time they hit, normal (and most abnormal) people say it's exactly the same.

And again...the experiment properly ignores any infinitely tiny immeasurable movement of the earth in ANY random direction for the obvious reasons already stated. There's far more difference based on the precise position of mercury than the position of the bowling ball and feather, especially when they are nearly touching...You know and understand this.

The thumbnail image for this video has been updated - thumbnail added by oritteropo.

The thumbnail image for this video has been updated - thumbnail added by ChaosEngine.

The thumbnail image for this video has been updated - thumbnail added by eric3579.

And She gets the cover of Sports Illustrated
http://cdn.abclocal.go.com/content/creativeContent/images/cms/Cover.jpg

The thumbnail image for this video has been updated - thumbnail added by eric3579.

For guys, ho many times have you looked behind your balls? It's somewhat comparable acrobatic action needed... It does still strike me odd that someone hasn't studied every cm of their body at least once.