Saturday, January 23, 2016

If, When, or But code Confounds F-35

In computer science 101 class you learn about firmware, software and the likes. Firmware drives the device and software drives the program. The F-35 is driven by pilots, "sort of". However, the US Air Force and Lockheed have entered into the age of Block III F-35, subtitled, "software glitches". The pilot gives a command or input, the software gives a command and the device firmware gives a command as the F-35 responds accordingly in a milliseconds. Read your Computer Science 101 text book it's all in there on page 225 chapter 8.

Image result for f-35

The pilot is interviewed after the ejection seat (a device) is loaded on a truck from deep in the desert test range. Other devices are unrecognizable in the desert rubble, the mystery solving phase is conducted back in the shop in some subcontractor's ivory tower. Having no device when the Pilot isn't talking code, and because analysis is in the software data stored in the computer lab, it becomes the story for the F-35, I'm sticking with it! 

The command language logic code isn't logical in some instances. During Computer Science Class 315, (101,201 is a prerequisite) and as a junior student who is tasked with deciphering software code as a homework assignment, we all say good luck over coffee at the campus study spots. In the Lockheed Conundrum Halls of Technology, they have real PhD’s computer types thinking about what went wrong with its software computer code. The difference between freshman year and the PhD level work is comparing one line of code as a freshman exercise compared with millions of lines of code at the PhD level. This is where the "if", "when", or "but" code commands come into play for the F-35. The code may be read in machine language from the command language as, "If" condition A exists go to line 1325, otherwise go to line 75. "But" or "when" condition B is valid, adjust flap control to 45 degrees." The pilot is looking at the horizon intently when in a millisecond, the software gets its "if" "and" or its "buts" in a knot leaving the "when" floating free from the program dichotomy.

At this time, the pilot has lights, buzzers and horns going off in is helmet. "But" He looks at the ejection sequence stickered to the cockpit hull and ejects. "When" the ejection seat is loaded onto a truck from the desert basin, the F-35 block III will be ready. "If" and "When" the Software Glitching Team of PhD’s, finds the miscoded lines before block IV starts, some say the F-35 Advanced Strike Fighter will be ready, "When" pigs fly.

Related Article: