5 ms·
Suddenly extremely worried about this: "James Webb Telescope will run a proprietary JS interpreter by a bankrupt company " https://news.ycombinator.com/item?
by belter 5y ago
Suddenly extremely worried about this:
"James Webb Telescope will run a proprietary JS interpreter by a bankrupt company
"
https://news.ycombinator.com/item?id=19737663 https://news.ycombinator.com/item?id=19737663
https://www.researchgate.net/publication/252882358_Event-driven_James_Webb_Space_Telescope_operations_using_on-board_JavaScripts_-_art_no_62740A https://www.researchgate.net/publication/252882358_Event-dri...
"The James Webb Space Telescope (JWST) will use an event-driven system architecture to provide efficient and flexible operations as initiated by a simplified, high-level ground command interface. Event-driven operations is provided through the use of an on-board COTS JavaScript engine hosted within the payload flight software..."
Edit: Found something ....Is it too late to postpone the launch?
https://www.stsci.edu/~idash/pub/dashevsky0607rcsgso.pdf https://www.stsci.edu/~idash/pub/dashevsky0607rcsgso.pdf
"...The JWST science operations will be driven by ASCII
(instead of binary command blocks) on-board scripts,
written in a customized version of JavaScript. The script
interpreter is run by the flight software, which is written
in C++. The flight software operates the spacecraft and
the science instruments.
The on-board scripts will autonomously construct
and issue commands, as well as telemetry requests, in
real-time to the flight software, to direct the
Observatory Subsystems (e.g., Science Instruments,
Attitude Control, etc.)...
The flight software will execute
the command sent by the calling on-board script and
return telemetry, which will be evaluated in real-time by
that on-board script. The calling script will then send
status information to a higher-level on-board script,
which contains the logic to skip forward in the
observing plan in response to certain events (see Section
4.1)... "
Found it...
"JWST uses an extended version of JavaScript, which
was developed as a COTS product called Nombas
ScriptEase 5.00e. ScriptEase provides functionality
common to many modern software languages and
follows the ECMAScript standard."
http://brent-noorda.com/nombas/us/toolkit/index.htm http://brent-noorda.com/nombas/us/toolkit/index.htm
http://brent-noorda.com/nombas/us/toolkit/isdkdownload.htm http://brent-noorda.com/nombas/us/toolkit/isdkdownload.htm
Latest errata from 2004, moving from worried to full panic mode...
http://brent-noorda.com/nombas/us/devspace/errata/isdk/index501.htm http://brent-noorda.com/nombas/us/devspace/errata/isdk/index...
- jazzyjackson 5y agoit’s not running Node 0.10.0 for gods sake, it’s an interpreter to write jobs that scientists can use for their studies - the flight critical stuff is a different stack
- belter 5y agoYou sure about that? From the linked paper ( unfortunately behind all kinds of paywalls...) "The major characteristics of our process are - 1) coordinated development of the operational scripts and the flight software, - 2) an incremental buildup of the operational requirements, - 3) recurring integrated testing. Our iterative script implementation process addresses how to gather requirements from a geographically dispersed team, and then how to design, build, and test the script software to accommodate the changes that are inevitable as flight hardware is built and tested. The concurrent development of the operational scripts and the flight software enables early and frequent "test-as-you-will-fly" verification, thus reducing the risk of on-orbit software problems...."
- jazzyjackson 5y ago“ 3.1. Event-driven Operations The JWST science operations will be driven by ASCII (instead of binary command blocks) on-board scripts, written in a customized version of JavaScript. The script interpreter is run by the flight software, which is written in C++. The flight software operates the spacecraft and the science instruments.” and in section 3.5, sounds like javascript just has an API to lower level system functions: “ ScriptEase JavaScript allows for a modular design flow, where on-board scripts call lower-level scripts that are defined as functions.” [0] https://www.stsci.edu/~idash/pub/dashevsky0607rcsgso.pdf https://www.stsci.edu/~idash/pub/dashevsky0607rcsgso.pdf
- nerdponx 5y agoI am mostly curious as to how they came to JS as the embedded scripting language of choice, as opposed to Lua or Scheme or anything else.
- grumpyprole 5y agoI'd like to understand how such a pinnacle of human design and engineering came to depend on a technology that is, putting it politely, certainly not.
- beebmam 5y agoThe fact that a project as profoundly important as the James Webb telescope only has a $11 Billion budget is staggering to me.
- nickff 5y agoWell, it started off with a $0.5 BB budget, and was supposed to be launched about 14 years ago...
- BatFastard 5y agoIt had a 1.5 billion budget, 9.5 billion in overruns.
- bumby 5y agoSoftware assurance within NASA is often a low-priority if not just an afterthought. Many project/program managers are from the hardware side (e.g., mechanical, electrical, or industrial engineers) and don't always give the appropriate gravitas to software in terms of its ability to contribute to failures.
- wolverine876 5y agoWhat is that based on? And has NASA had many software failures? Their missions seem incredibly reliable, especially considering how far beyond the bleeding edge they operate.
- bumby 5y ago>What is that based on? Personal experience as a civil servant with NASA. Often, quality aspects take a back seat when schedule pressure is high. It’s the whole reason their current safety and mission assurance org became a separate entity after Columbia >And has NASA had many software failures? There's been quite a few high profile ones like Mars Climate Orbiter and more recently with CST-100. In the case of the latter, there were clear process gaps that should have caught the issues if the software assurance procedures were actually followed. Note that last one is for a non-crewed test of a vehicle meant to take people into orbit; presumably this is the highest threshold for quality procedures. There are many, many more lower profile ones that don't get talked about, even within the agency, dating back to Gemini. >especially considering how far beyond the bleeding edge they operate. I know that's the public perception. Much of the missions are bleeding edge (because there's very little incentive for anyone except the government to do them), but you might be surprised about how they don't always use state-of-the-art tech. Now some of that is by prudent choice because you'll often prefer tried-and-true of bleeding-edge, but some of it is just because of complacency.
- belter 5y agoSounds like somebody at NASA should contact Brent Noorda. "Nombas,Un-Incorporated" http://brent-noorda.com/nombas/us/index.htm http://brent-noorda.com/nombas/us/index.htm He is in the critical path...
- xenadu02 5y agoIt is common in such commercial agreements to provide source code or to escrow source code with a third party service with conditions that trigger release of the sources (eg bankruptcy or sale to another company that discontinues the product). So it is possible they have the full source. It is also worth considering that the JS engine likely hasn't changed much (if at all) in the past 15 years. Its bugs and limits are well-known at this point. It is also an interpreter which makes it slower* but less subject to vulnerabilities that impact the host. Honestly that's probably the correct choice for a spacecraft where reliability and safety is more important than performance. Don't get me wrong: JavaScript is a big ball of WAT and nonsense we've spent way too much effort improving but I don't blame them for making the choice so long ago and sticking with a known quantity rather than risk introducing new problems by changing things. * I once worked on a project that used IronJS to run JS in the .Net runtime. It took advantage of the runtime's JIT but was a lot of not terribly optimized F# code. I built a V8 bridge and was very excited for the increase in perf... but it got slower. It turned out most customer-written JS code spent most of its time using the API which was backed by C# code and that meant lots of bridging. At the time I left they were still using IronJS because it was faster for their workloads. It taught me the importance of testing your actual workload and taking a whole-system approach to perf.
- johnisgood 5y agoThey really ought to look into Ada.