Saturday, July 13, 2013

Zimmerman case sets a grim precedent

I'm writing this just as the news of the verdict came in, and I was expecting that even the lesser charge conviction would have been justice served.  What happened, in my view, was the same sort of result that came of the trial in "To Kill A Mockingbird".  Evidence just didn't matter, especially in a state just as PWNed by the NRA as Oklahoma is.

A few days ago I posted a blog entry regarding this case during the testimony of medical examiner Shiping Bao, who, to my eye, was just as distrustful of the defense attorney on the basis of familiarity with the community's racism as any black might be, as a non-white member of that community.  



I removed that entry because I felt that I put too much personal information in there to provide a basis for my evaluation, giving full acknowledgement of my own race in the process.

In view of this verdict, I think I should at least mention again that particular part, as I think the manner in which the medical examiner went from objective witness to hostile-to-defense witness is particularly revealing in regards to the nature of the community as a whole, and it's the community as a whole that provided the jury.

Justice was not done today.




Train wrecks and smaller government: workplace safety, cost cutting issues.

Fuel train in Quebec went boom, it's employee's fault. According to any company, all safety failures are employee's fault and never faulty equipment fault or company negligence. Ever.

This situation is the case no matter where you go--when something goes wrong even in a circular coal-feed rail yard, it's the employee's fault and the violation can be found in the safety book, if you're working in a union shop.  And if you don't violate safety procedures at the direction of the company, you get a poor performance review and fail to get promoted.  This is tradition, and was even the case in non-union Motorola's factories where OSHA, not union contract, held sway. And we know how under-funded OSHA has been since our small governmental small minds have had anything to do about it.

Let's review some railroad history: in its earliest days, trains would careen down steep slopes and jump the tracks, or run clean off of a drop-off caused by a bridge getting washed out or sabotaged.  That's why the Deadman's Stick got invented.  Yeah--it's an arrangement where the brake is applied to the train as default, released only in the presence of a live man to keep it held off.  Man dies by, say, train robber or Indian, train stops dead on its tracks.  Man dies, train's dead too. Locomotive engines have been manufactured with the brakes always on ever since.

Corker question: who defeated the train's Deadman's Stick?  Negligence doesn't explain the fact that it takes an action, not an inaction, for taking the brake off.

Part of my job at the power plant included railroad controls out in the coal yard.  That train wasn't manned either, and brakes weren't an issue because it's the radio control that actively kept the brakes off when the train was in motion.  When the radio control was off,  the brake was always engaged as default position.

That wasn't the only railroad involved with the power plant, either. On another track, we had tanker car full of chlorine gas used for water treatment while turning the lake water into boiler circulation water, for steam generation.  While the coal yard train, with engine, went around in circles (delivering coal from the point where it was railed in to the point where it was fed to a crusher and then fed, on conveyor belts, to the generating plant), the rails that brought in the chlorine tanks that were left with no engines and therefore the cars had their wheels chocked.  The brakes on any train engine are always on unless they're deliberately taken off by human or by remote.

Blaming the employee for failure to engage brakes is BS.

(I used to have this tune on a rather old 78 rpm platter; don't remember the artist)


I'm adding this sidebar in order to add a link to a site where I found historic railroad jargon, so that I can find it again more easily than I could if I bookmarked it.  And in the event anyone else may be interested in such things. Catskill Archive

Friday, July 12, 2013

Proving a negative--it can be done, and people do it routinely.

The other term for proving a negative is ruling things out as possible.  That's what's going on with the Zimmerman trial as we speak: prosecution trying to prove that what Zimmerman claims happened could not possibly have happened, and citing events and conditions which prove that particular negative.  The defense's business is not only to prove what happened actually did happen the way it was described, but also how what the prosecution claims happened couldn't really have happened. It's a question I often ask when encountering people who claim certain events in history happened as they were taught, or as they read, but couldn't have, given the circumstances of those times.

If you have passed any upper level mathematics classes involving algebra, you too have proven negatives in the process of solving for an unknown variable, because you have to rule out what the variable couldn't be in order to arrive at what it actually is.  You have doubtless encountered the Venn Diagram, which graphically depicts sets (families) of data in order to determine where the sets overlap and where they don't.  If you're about the business of determining where the sets have something in common, what you've done with the non-intersecting parts is rule them out, and in this manner prove a negative in their case.

Negatives can be proven, and in court cases MUST be proven. Also true of the methodology of solving sudoku puzzles.  If you cannot rule out all the numbers from 1 to 9 except one number, then you're making a mistake of writing in your best guess.  Guess at sudoku, and you fail nearly all the time, especially on puzzles of greater difficulty than the beginner level puzzle.  You MUST prove that all other numbers except one number do NOT belong inside the cell.

So the next time you get into an argument with an evangelist who proclaims that nobody can prove or disprove the existence of God, and you're an atheist, simply point out that what you've done is rule him out.  It's doable.


Wednesday, July 10, 2013

History, computer style--only coding geeks can grok most of this.

The missing pictures were linked to Facebook album pics and that's why they're not appearing.  Looking into fixing that.





As stated in my Profile, I've been online ever since computers could talk to each other even before the PC was invented. Mainframes were talking to each other on the phone via acoustic couplers using what would eventually become an RS232 standard port for the PC after the PC was invented.  Same deal, same standards, familiar rate of 300 baud.  I was mainly on an IBM 370 VM/CMS at Academic Computing in my early college years (okay, so I occasionally played a game of Star Trek) where the first language I picked up was CMS (Conversational Monitor System).

Computer language, that is.  Forget the French I grew up with, forget the Portuguese I signed up for as a freshman (at the end of the day, it's all Latin anyway)--CMS was the language that would serve me well even today as VM (Virtual Machine) became regarded as some kind of Microsoft novelty when it really isn't.  Windows is still evolutionary bloatware that would still take antique WordStar commands in its earlier versions.  When MSDOS 2.0 finally came out with the first version of commercially sold PCs, it would still take CP/M commands.  Nothing about Microsoft is original. 



I did some moving around since the PC was finally invented by IBM (enlisting Intel for the purpose of miniaturizing the venerable IBM 370 onto a microchip that became the Intel 8080 microprocessor).  So there ya go--I was already intimately familiar with the thing by the time a whole huge room of computer became small enough to fit on a desktop. Alas, all the moving I did had the effect of my being able to preserve some documentation from this computer history, but also losing a lot.  Recently, storage damage due to moisture incursions mandated that I go through all my old packing boxes and scan stuff into today's technology storage media before I completely toss it all, and it's partly in presentation with this blog entry, beginning with record of interactions on the now-defunct CompuServe.



I have a Facebook Album which has a lot of it already scanned in, but just today I located some stuff I thought I'd lost or tossed long ago and pertains to what I put in my Profile on Google Plus: printouts from my CompuServe WITSIG days (aka NETWITS).  When I was on there, I had the first laptop ever manufactured, and that was the Tandy Model 100. I also bought a suite of attachments including a 4-color plotter (not to be confused with a printer; the Model 100 could indeed do scientific plotting as a sort of proto-CAD manner), and it was the plotter that preserved some of that irreplaceable humorous chatter that took place on WITSIG with some of my favorite people.  I've scanned it, and I will post it here.

"RR" = Ronald Reagan. <>lessa<> was the sysop of the SIG (Special Interest Group), but just as guilty as smartassery as the rest of us NETWITS renegades. Definitely one of the family among such luminaries as Otto Graph and Mahatma Coate. Partial list:

The following duplicates a couple of Users, but my name and ID is listed, and I post this as a proud badge of long standing NETWITS smartassery with seniority.

Of course I noted with much interest that Son of Sister Sam was also in via the Phoenix node of CompuServe. Yes, you would be accurate if you said that I honed smartassery down to a science--but I was not alone.  My co-conspirators are still out there somewhere in cyberspace, so keep looking over your shoulder.  Typical chatter would be just as off-colorful as it was colorful:


Yeah, that wasn't a condominium we were talking about, and the preceding discourse was omitted because I checked an agreement with Blogger not to post adult content. Among my historic artifacts in storage I also discovered everything I ever wrote as an assignment for all of my English classes, thinking that this particular story was worth writing an essay about, because this is where smartassery surfaced in the first place.



I went from doing battle with a TA who proclaimed that "English is hard" every chance he got to getting not just A+-es on my papers but smiley faces too. Stewart Vyse, you know I'm talking about you, man.


This was basically the launch of the Clara Listensprechen Report as first conceived in English class and then into print on the ASWLC. Whole 'nother tale, that. Anyway...

Ah, the wonderful world of languages. French, Portuguese, CMS, CP/M, which was the proto MSDOS command set; MSDOS proper, and BASIC. I really took to BASIC like a duck takes to water, and that proved useful when I interviewed with Motorola for its USA-1 automated factory project, so despite its acronym, it was NOT a language used by beginners.  When I first signed on, it didn't start out with a central computer control system, but they were working up to it.  Central computing involved a DEC mainframe, but the individual machine co-ordinators were (ta-da!) Tandy Model 100s.  Well hey--that was the ONLY laptop on the market with a shrunken IBM 370 smooshed inside, and I knew how to program the thing like it was my native language.

Not just in BASIC, but also machine language (assembly language).


Served to come in handy still yet again when USA-1 closed down, and two departments later, wound up in the Electronics Materials Operation of Motorola and they had an interesting automated acid dipper I got more or less assigned to: the Autotraq.  Learned a new version of BASIC: robot BASIC, which was called RBASIC.


And since my employment at Motorola, I picked up a few other machine languages as well, including one that was proprietary to Westinghouse, whose boilers I was already familiar with, heh.



So there you have it.  What was used for calculators, though? Slide rules. What's old is new again (except for the slide rule), and just because it may be new to you, doesn't mean it was invented just yesterday, although the programming language standard these days is C++. @Tipa, if you should come over from Facebook to read this, you should note that not every editor will accept ASCII coding from your keyboard just like Facebook editors can.  The following is a test of what low-end ASCII that Blogger will tolerate:

☺☻♥♦♣♠•◘○.........◙♂♀♪♫☼►◄↕‼.........¶§▬↨↑↓→←∟↔.......▲▼ !"#$%&'

Confirmed: Blogger editor will accept low-end ASCII code.  Let's see how well it does with extended ASCII.

⌂Çü......éâäàåçêëèï.....æÆôöò.....¢£¥₧ƒ.....ñѪº¿⌐...¬½¼¡«»░▒▓│.....┤╡╢╖╕╣║╗╝╜

Ya, I'd say it does well with extended ASCII too. Very good.  P.S.--I also speak hexadecimal fluently.




Computer Employment Gallery






Before that, I was a C&I tech at Illinois Power Co. and member IBEW, Instrument Man 2nd Class. Is this computer history? You bet.  The Leeds and Northrup computer which monitored all the subsystems of all three boilers was a classic analogue computer using a truckload of operational amplifiers (op amps).

Before there was such a thing as digital computers, there were analogue computers and not just using vacuum tubes either.  There were pneumatic analogue computers and relay computers as well, and the one thing they had in common was that their configuration worked as computational logic gates.

The Leeds & Northrup computer was used for on-grid operations monitoring/safety, but a separate computer was used for combustion efficiency analysis and that was a Honeywell digital mainframe that spoke octal, and generated printouts on not printers exactly--they printed out using EBCDIC on relay-equipped IBM Selectric typewriters.

A third computer made by Bailey was used for ramp ups and shutdowns.


 The notations with LN numbers = Leeds & Northrup part numbers.  A typical L&N logic diagram follows:


Next is a publication for the employees...What, this isn't the computer history part now? Actually, Illinois Power Company doesn't exist anymore either.  It's where the computers were, and it, too, is history.



The following is a sort of map of one of the three boilers I worked on. There were two of these (Westinghouse cyclone-fired once-throughs, universal pressure type) and one General Electric recirc, drum type.

Taking photos of the power plant are usually prohibited, but on my last day at work, before going to Motorola, I was permitted one shot from the ladies' room...

{okay, so I took 3 to make this composite}  As dirty and as hot as it was, it had its good moments and there are times I actually miss the ole place, especially that lake.  You should see the channel cat and drummers you could pull outta that thing. Oh yeah--I was granted permission to keep my boiler book and hardhat.

Tuesday, July 09, 2013

Ed Snowden, he take the data and run to Venezuela?

Voice of Russia posted on Facebook that Snowden had accepted a grant of asylum from Venezuela, then it posted a sort of retraction saying that this information came in via Twitter, and that the Tweet had been removed.  It's not like Twitter is any kind of authoritative source in the first place, even with verified accounts.  Accounts get hacked, as anyone who has had trouble with spammers can attest.

Nonetheless, despite the embarrassment of the Bolivian affair, all eyes are now on Venezuela as if Snowden actually can get from Point A to Point B under the circumstances. Worth watching.  So is the guy who I paraphrased to come up with the title for this blog entry.  I'm just as much a fan of his as I am of Bert Williams.



++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
LATE NEWS---CARACAS PUBLIC TRANSPORT PROTEST
 (Blogspot didn't want to embed this for some odd reason--sorry)
 33 protesters arrested so far. Other videos have been posted on YouTube about this.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

A  Spanish language update on Snowden, which suggest Russia →Cuba→Venezuela.  
http://actualidad.rt.com/actualidad/view/99769-snowden-moscu-vuelo-habana-aeroflot 
 

Monday, July 08, 2013

OF COURSE I'm going! Festival Peruano 2013 en Oklahoma City

Looks like somebody forgot to put the hours on the announcement.  I just learned that it's from 11 am to 8 pm.

Also gonna put in a shameless plug for my favorite Peruvian restaurant in OKC, the Inca Trail.  I've enjoyed it since it first opened--it's quite an adventure to Peru without actually going. :)  They have since opened a sister restaurant called Naylamp (their Facebook page). They don't have their own stand-alone website yet.

Going to be on the lookout for some of that famous chocolate, you bet! I'll be taking every camera I own. :)

If you're on Facebook, these are the people to follow for updates: Peruanos en Oklahoma

The event page on Facebook: Festival Peruano 2013 en Oklahoma City

 El Nacional de Oklahoma article (Spanish)
More event info.


JULY 20 CULTURAL NOTE UPDATE: NY Post posted this article about a Peruvian tradition regarding pall bearers and reported some remarkable statistics associated with its treatment of black Peruvians. O_O