Little search shows that that it's a probe sent to an asteroid to collect samples and bring them back to Earth. It was sent in 2014, arrived this year, and will fly back in 2019 and arrive in 2020.
EDIT: Looks like it just landed on the asteroid, hence this being posted 
Otherwise super cool!
Anyone know how long the signal delay is?
Why? You're assuming you have a similar amount of training/experience as the controller?
If possible, I'd like to request the assumption of good faith. Hey, at the end of the day, maybe they do know what they're talking about, no? :) Could be an ex Japanese astronaut!
There are various, competing technical definitions of “deep space” — the ITU defines it as more than 2 million kilometers from earth — but the Deep Space Network, and similar networks operated by other countries, are typically used to communicate with interplanetary spacecraft, and are effective basically anywhere higher than geosynchronous orbit (26,000 miles/42,000 km).
Cool looking web site
I'd love to use a modern GUI that adopted this aesthetic. Even though the content of documents would be in color, having the UI itself restrained to a simple monochrome palette would be very enjoyable to use.
Another great part of this particular interface is also minimal cruft. All you have is data text, descriptive text, and a bunch of small graphics, all but one meaningful (the sine wave representing communication seems to be just a gimmick, though it still carries a few bits of relevant information). No useless animations, no useless framing, no "material design", no nonsense.
I fondly love all the work you can find in the portfolio.
( edit: oh, with dark and light themes! )
Fuck it. Slater is magic software...
and it's interface is like a tiling 'window manager' for any number of screens (anything with a browser), for threads of interaction, that are modeled as a story, like a conversation... but composes natural language with rich controls, forms, and stateful widgets. and super monochrome... but also controls your browser and TV and stuff...
I'm really inspired by the design work on the LightPhone 2, btw.
Super lame, early video: https://youtu.be/_m1zEbQieYQ
I'll probably throw away the waveform. I'm just looking for ways to use the audio to pace the text output, and also to tie the speech and text together as much as possible, so there's never a gap between them for your focus to jump between.
How are you synchronizing to each word?
I wonder if Google would consider expanding their TTS a bit to provide syllable data and other rich breakdown information.
I like the waveform, btw.
I'm using Polly for the moment, and it provides word and viseme boundaries. Enough to animate face poses. I'm not taking full advantage of the visemes here: it's only affecting the saturation of the waveform color. Too subtle to notice, with the way things kind of flicker with this one.
I have other ideas I want to play with, but don't really have time, and I may just have to drop that line of thinking, because I plan to move to one of the wavenet implementations, which don't provide speech marks data.
This sort of design fits nicely into css and html without much hackery but that doesn’t mean it’s easy to design.
I suppose you could view source or inspect element.
Graphic design principles are what make the difference...
The old mIRC was mostly like this, a core/backend functionality with a very skin-able frontend.
Almost all the value is in the UI. For the user, it's the place where they interact with the system, and in software tools, UI design can make orders of magnitude of difference in value delivered to the user. For the vendor, the UI is where they shove ads at people, track them, and lock them into the product.
The problem is that Internet companies today no longer operate under "earn money by delivering value" model. They operate under "extract as much value as possible from the customer", which means any value delivered is incidental. Examples of those two models in action:
- "earn money by delivering value" - customizable interface with power-user features, and/or good API allowing users to interact with the product from third-party UIs and scripts; users pay for the product/service
- "extract value from user" - dumbed down, shiny interface, no power-user featuers; locked down SaaS little to no API access; sometimes paid, but more likely free in order to maximize user growth, which leads directly to the company being acquihired, product being shut down, and users being left in the cold
(Yes, I'm pretty bitter about the state of things, and I generally refuse to use most SaaS products because of the dominant approach of such companies.)
 - as a real-world example, consider software for managing products in ecommerce. Take away batch-processing capabilities, and your user's productivity will drop hundredfold. Which directly translates to a) frustration, and b) the need to hire more people for the same task.
It bothers me that people are drawn to it like flies and you see this type of thing everywhere in "Futuristic" projections of our life.
They're objectively worse, yet they look cool and the general public values "Coolness" over GUI's ability to meet its core purpose - that is to leverage human vision's bandwidth to convey information rapidly, concisely and without ambiguity. That is the whole point of a GUI.
I.e. not that bad, if precaution is taken against information overload in some kind if crisis.
(Ignoring things which are unknown to us - for instance would the operator benefit from trends in data? This does not seem to be present in the UX.)
Your critique would be true when leveled at the font choice, though.
Sad to think my hacker news machine (PC) is using more power than an an intergalactic satellite.
Radiation testing, maybe?
In addition the manufacture, storage, and movement of each chip is very carefully managed and documented, which adds a surprising amount to the cost. This allows you to determine root causes in case of a failure, which then lets you understand whether other spacecraft using similar parts are in danger.
Radiation tolerance is an important part of this, both in terms of lifetime exposure tolerance and in terms of single event upset susceptibility.
Suddenly I understand the fuss about the early processors (eg, the Forth ones) that went into spacecraft in the 70s and 80s. It wasn't just the architecture that was good, it was the electrical/physical design that was noteworthy (which, to excuse the terrible pun, the CPUs are still writing home about :D).
Heh, I wonder how much the ground development boards cost? Probably way too much to find one affordably on eBay, say...
Also - how do you figure out if a processor is going to last for ages? How do you test it?!
Hmm, I get the impression some spacecraft probably have full failover capability as well.
And now I wonder what systems use CPUs in lockstep _and_ have full independent failover...
“Also - how do you figure out if a processor is going to last for ages?”
Really big semiconductor junctions help. Low heat production also helps. And then there's this thing called “heritage”. If it worked on the last fifteen missions, odds are decent it'll work on the sixteenth.
Many spacecraft have fully redundant processors boards. Whether that helps you depends on whether you think chip failures are statistically uncorrelated. Which they are, sometimes. But not if there is a design flaw or manufacturing defect.
Most computers offer idle power savings. My quad core i5 uses like 15 watts while casually browsing the internet.
You can escape the galaxy if you apply a very small force over a very long time, or a larger force over a shorter time.
You might mean interplanetary.
And that's pretty normal for command receivers.