sunray2
Joined 1 year ago
Joined 1 year ago
You can see that, to some extent, in how the article’s points apply to language and communication in general, not just between Japanese and English. While turns of phrase give your repartee a flavour that sells your point—like what you’re reading now—it’s also a product of your thinking process, and as the article says, could cloud the point you’re trying to make. If you can speak or write clearer, then your points will also become clearer to yourself. That’s follows my experience, since I speak a lot of German for work. In German, I must think carefully about each point I make, otherwise I’ll run into a sentence for which I don’t know the words. I endeavour to respect the language and culture, and in doing so put effort into making my points simple enough for me to reach for the right words and phrases to show this respect (at least, I try!)
For a good example: David Sylvian collaborating with the late Ryuichi Sakamoto. You can see them writing ‘Blue of Noon’ in the Brilliant Trees sessions on Vimeo/Youtube. David talks about his use of really minimal language to get musical structure and points across, since Ryuichi’s English wasn’t yet as perfect in the 80s as it was later on. You see this directly in the session videos. What’s truly the best about it, is the respect they show for each other.
Bad example (potentially): Aston Martin F1 collaborating with Honda on the new F1 engine :-) . After several years of extensive development and billion-dollar investment, today they’re at the back end of the grid, more than 3 seconds off the pace. According to recent rumours, as recently as November, the Aston Martin F1 bosses visited Tokyo to discuss progress of the engine that had been in development for a few years, apparently having hardly visited before, and were shocked to learn that only about 30% of the original workforce from Honda's previous venture in F1 remained. It seems they didn't even know how far behind schedule Honda was! For projects as large as F1 car development, it’s unfathomable that this mutual curiosity, which in effect is a form of respect, apparently wasn’t there.
- the necessary basic electronics;
- PCB design;
- 3D CAD;
- your particular iterative process,
among other things? I get the impression you built things incrementally, observed what happens and learnt via that feedback loop? Maybe others could share their own feedback loops, too.
As for fully integrated optics, it's where quantum computers eventually want to be, and there's no physical limitations currently. But perhaps it's too early to say whether we would absolutely require free space optics because it's impossible to do some optics thing another way.
With quantum computing, one is forced to use lasers. Basically, we can't transmit quantum information with the classical light from LEDs (handwaving-ly: LEDs emit a distribution of possible photon numbers, not single photons, so you lose control at the quantum level). Moreover, we often also need the narrow linewidth of lasers, so that we can interact with atoms in the way we want them to. That is, not to excite unwanted atomic energy levels. So you see in trapped ion quantum computing people tripping over themselves to realise integration of laser optics, through fancy engineering that i don't fully understand like diffraction gratings within the chip that diffract light onto the ions. It's an absolutely crucial challenge to overcome if you want to make trapped ion quantum computers with more than several tens of ions.
Networking multiple computers via said optical interconnects is an alternative, and also similarly difficult.
What insight do i gleam from this IEEE article, then? I believe if this approach with the LEDs works out for this use case, then I'd see it as a partial admission of failure for laser-integrated optics at scale. It is, after all, the claim in the article that integrating lasers is too difficult. And then I'd expect to see quantum computing struggle severely to overcome this problem. It's still research at this stage, so let's see if Nature's cards fall fortuitously.
I think that's the real key to this stuff: what makes these things actually sound good?
I was using the demo just now: the sounds you get out of this are actually better than I expected! And I see what you meant in the videos about intuitive editing, rather than abstract.
Although, I was often hitting 100% CPU with some presets, with the sound glitching accordingly. So I could experiment only in part. I'm on an M1 Pro; initially I set 128 buffer sample size in Ableton but most presets were glitching, I then set to 2048 just to check for improvement, which it did, nevertheless it does seem a bit high. Maybe my audio settings are incorrect? I can give more info later if it helps you.
Remind me of Korg's Berlin branch with their Phase8 instrument: https://korg.berlin/ . Life imitates art imitates life :)
I highly support and encourage this. Is there a way I could contribute to Anukari at all (I'm a physicist by day)? These kinds of advancements are the stuff I would live for! However I should stay rooted in what's possible or helpful: I'm not sure if this is open-source for example. As long as I could help, I'm game.
I looked up any connection to ARTIQ they may have: it seems they do full stack QC, as they have their own quantum compiler [1]. But I'm not really sure what they're doing currently.
What's the fundamental physical limits here? Namely, timing precision, latency and jitter? How fast could PyXL bytecode react to an input?
For info, there is ARTIQ: vaguely similar thing that effectively executes Python code with 'embedded level' performance:
https://m-labs.hk/experiment-control/artiq/
ARTIQ is quite common in quantum physics labs. For that you need very precise and determining timing. Imagine you're interfering two photons as they reach a piece of glass, so that they can interact. It doesn't get faster than photons! That typically means nanosecond timing, sub-microsecond latency.
How ARTIQ does it is also interesting. The Python code is separate from the FPGA which actually executes the logic you want to do. In a hand-wavy way, you're then 'as fast' as the FPGA. How, though? The catch is, you have to get the Python code and FPGA gateware talking to each other, and that's technically difficult and has many gotchas. In comparison, although PyXL isn't as performant, if it makes it simpler for the user, that's a huge win for everyone.
Congrats once again!
It loads quick, and works with large data. Crucially, you can view and edit visually, not only programmatically.
Assuming those already working with such data have Excel and Python tools etc., the pitch here is that the $39 license fee saves time or effort. So, is it that the user can spot and correct errors that you couldn't otherwise do with either Excel or with other big data tools? And/or otherwise do the necessary data manipulations?
I came across the phrase 'eyes like a shithouse rat' recently, to describe the people doing final checks at a printing press. I think there's probably plenty of people out there who would pay $39 for eyes like a shithouse rat.
Also the website makes me nostalgic :)
He gave this pithy summary of his answer to a memorable discussion in a Nobel Laureate panel about what it actually means to explore Hilbert space, from a more practical perspective. Their discussion may be a good complement to the title article of this thread.
Others in this thread already correctly noted that just because something --- 'thing' more precisely defined as some action that results in an observable outcome --- exists in Hilbert space doesn't mean it's possible. But what Ketterle and others were getting at is that, as we make new theories and experiments, we can explore more of Nature and what's possible within, guided by the structure that Hilbert space could give to our questions' outcomes.
That being said, Ketterle explains it much better than I do.
Ketterle's answer in context: https://youtu.be/DNhmYkTW_jI?t=4220