again?

Or just an identity check using a neural-response scan while certain questions are being asked:

https://www.youtube.com/watch?...

The pilots should have reasoned: "Engines not responding to control. Since the engines are still at least giving us high power, we should climb to a height that gives us options, then try some things to fix the problem, or figure out how to cut the engines completely and glide in, having enough height to get the setup of the difficult approach just right."

Of course the maintenance program manager for the aircraft manufaturer should have reasoned: "All maintenance procedures should be performed by checking off, in an app, a detailed automated checklist of steps, such as restoring custom-data files. The maintenance software app should not permit maintenance to be signed off as complete until the automated checklist is all checkmarked. and it goes without saying that all such step-by-step procedures should be verified as complete and working before being included in allowed maintenance procedures of operational aircraft."

My printer at home does it every time it starts up.

Too bad the airplane doesn't.

I guess production delays are more expensive than debugging-by-crash. Sad.

before our robots became cheaper than their workers, and capable enough to do the job.

Don't be fooled into thinking this trend is much of a local employment boon.

(Unless you're a robot.)

And this would make the testing of my Oscillation Overthruster version 2 prototype in my basement so much easier.

Right now having to hot-wire to the medium-voltage side of the pole-top transformer is such a pain.

We will have solar panels but lots of partial-array shading so no series-strings for us thus no high DC voltage and sadly, no Tesla Powerwall.

Instead, we'll go for a large 24V LiFePO4 of LiYFePO4 battery pack, and re-use some of our existing house circuits for 24 V DC for LED lights and 24V fridge and freezer. The 24V or 48V RV/Yacht fridges/freezers available are 5 to 10 times more energy efficient than standard "Energy Star" AC fridges.

Then we'll run a cheap DC/AC inverter or two for running laptops from the DC system.

Laptops, lights, (beer) fridge. In summer, what else do you need really?

But that happens relatively rarely, and it is rarer still that the new theory completely falsifies the old theory and observations.

More often, the new theory just puts the old one in perspective, or modifies it partially.

e.g. Newton's theory of gravitation, acceleration, velocity etc. are special cases of Einstein's theory. The two theories both align very well with observation at most measurement precisions and time, distance, and mass scales that people have ever experienced.

My philosophy has always been that once having passed the bar of qualification, a scientist should be left alone, career-wise, to have peace, and time to think and experiment, and time to try and fail with impunity. And these time chunks need to be on the order of 5 years or so.

The current system is optimized to produce incremental advances by scientific worker-drones. It is not designed to produce important new insights or confidently well tested important results.

It is way more expensive to waste scientific talent on bureacracy, grant application toil and stress, and writing of interim cruft than it would be to just let the people friggin' work unmolested using their own best judgement and wisdom about what to work on and at what pace and priority.

Scientists are, or are before it is beat out of them, all highly self-motivated, DRIVEN people with unique interests and insights.

Take off the reigns.

0. MAKE A CONCEPTUAL MODEL OF THE PROBLEM-DOMAIN THAT YOUR PROGRAM WILL REPRESENT AND WORK ON.
Jot down a circles-and-arrows model (diagram) of the types of entities that exist (and are important as far as your program will be concerned) in your problem domain. The circles, with an entity-type-name written in each, represent the important different kinds of objects/entities in your domain. The arrows, which you may refer to later when defining attributes or functions that work on the entity types, summarize the important relationships you have noticed between the different kinds of entities in your problem-domain. Look around for groups of entity-types in your domain model which are really just different subtypes of a common kind of general entity type in your domain. Create a named circle for the general type of entity, drawing it above the group of more specific subtype entity-type circles, and join the general-entity-type circle, to each of the entity-subtype circles separately, with a different kind/colour of arrow than you used to represent relationships between one kind of entity and a completely different kind in your domain model diagram.

1. TURN THE CONCEPTUAL MODEL OF THE DOMAIN INTO A STRUCT-BASED DATA MODEL
      Organize data (variable) definitions in the program you are writing into "struct" definitions, where each kind of struct has a set of attributes that together represent the essential properties of some kind of entity in your problem domain.
  (And, for advanced credit, create an additional named struct-type to represent the properties of some kind of abstract record-keeping entity-type you are concocting as part of your "solution" domain. A "solution" domain model is an extension of your model of the problem domain, where you are adding abstractions (new variables) into your problem domain to create a computer model of the solution to whatever problem you've been asked to program a solution for in the problem domain. Some of those solution-domain entity types may not have occurred to you when you first looked around at the external "outside of the program" problem-domain to create your struct-definition-based data model of the problem domain entity types.)

2. NAME YOUR DATA TYPES AFTER THE PRECISE NAMES OF DOMAIN ENTITY TYPES
        Use the common (but precise) name of each kind of domain entity as the type-name of the corresponding struct definition.

3. METHODS - are functions/procedures specifically applicable to the attributes of a single struct type.
        For each type of struct you have defined, define the interface signature of, and code for the implemention of, a set of functions which access the attributes of, set the attribute values of, or compute some function of the attributes of a single type of struct.

4. INHERITANCE
        Object-oriented languages let you create a struct-type which is meant to represent a specific subtype of domain entity, whenever you have already created a struct-type (and its functions) to represent the common attributes shared by several subtypes of entity. That is, you have already created an abstract supertype struct definition to represent general properties of a general category of domain entity, now you want to add attributes (or specific values of attributes) that describe how different subtypes of the general entity differ from each other.
In an object oriented programming language, the subtype of struct can be created so that its definition references (mentions) the supertype struct type by name.
Then any in-memory instance of that subtype struct inherits all the attributes and applicable functions of the supertype struct definition. Then you add more, specific attributes, attribute value settings, and function interfaces or function implementations to the new subtype of struct you are creating.

5. PROGRAM WITH YOUR DOMAIN-ENTITY-MODELLING STRUCTS AND THEIR STRUCT-TYPE-SPECIFIC FUNCTION-SETS
To represent as program data the state of the problem-domain or the values from your programmatic manipulations of it or calculations about it, allocate in-memory instances of the appropriate struct types, and set or read their attribute values. To access or manipulate attribute values of a struct instance (also called an object), use ONLY the functions you defined to apply to that type of struct. Do not access or assign to the struct attributes without going through one of the functions you defined. This discipline has several benefits, including allowing you to safely modify some details of each struct type's representation or state-maintenance logic without having to modify external program sections that refer to or set the attributes of the struct.

Some advantages of all this are:

A. The complexity of your program, as a representation of your problem domain, will be minimized by directly modelling, one-to-one, the obvious entity types that occur in that domain, as opposed to just creating a large set of individual, ungrouped variables to represent individual attributes of things in the domain.

B. Provided you do not go crazy creating super-abstract, impenetrable-to-understand supertype struct types, the creation of supertype struct types and supertype function definitions further reduces the complexity of your program, by representing common properties of, and general manipulations of the domain (model) only once in the program. Lack of repeated similar data-representations and code sections leads to a smaller program, and assists in program incremental development or maintenance, because it prevents error-prone and program-complicating partial-modifications where some but not all of the similar data definitions and code sections are modified.

C. The set of functions grouped to be applicable to each type of domain entity form a modular, loosely coupled program structure.

D. By restricting access to the domain model and modification of it to predefined and grouped functions only, you create a program that is easier and less risky to modify, Program modifications generally have fewer cascading dependent modifications and fewer dangerously randomly located sets of co-dependent modifications.

Currently, EVs represent 0.115 % of motor vehicles on US roads and 0.06% worldwide.

That is, roughly 1 out of 1000 vehicles in the US and 1 out of every 1700 vehicles worldwide.

Remember that we are trying to keep global warming below 2 degrees Celsius and so far epic failing on that.

My proposal, consistent with climate prudence, is to keep using increased gas taxes until EVs become 50% of vehicles on the road, then and only then start transitioning to distance-travelled fees.

You are SUPPOSED to be incentivising the switch away from fossil fuel transportation now, and as you can see, there are miles and miles and miles to go on the transition plan.

Stopping the various EV incentives now is the kind of short term thinking insanity that got us into this mess in the first place.

Want to run a 24V DC "RV electrical system / yacht electrical system" from a DC sub-panel in my house running efficient DC fridge, LED lights, small inverter for laptops etc, and maybe a larger inverter for a diversion load in summer.

Also, our PV modules on our roof need to be entirely in parallel because lots of partial-array shading at various times of day.
So our input voltage range (to batteries) will be around 30V and the output should be 24V DC.

Anyone seen the spec. for input voltage range for the Tesla Powerwall?

Also, anyone know where one can get a 400V to 24V efficient and safe DC/DC converter for the output side of the Powerwall?

what could possibly go wrong?

Members of congress have a library? Don't they know libraries are full of liberals? "There's only one book worth reading!" I was pretty sure they stayed far away from libraries, and radical interwebs and such.

where they don't build grocery stores within walking distance.

That is soooo.... 1950s/60s/70s.