And even with the non-deep networks from back in the day, people felt compelled to include prior knowledge and even used Bayesian priors to deal with a lack of data.
[1] http://papers.neurips.cc/paper/447-neural-control-for-rollin...
1,706 karma · joined March 5, 2014
And even with the non-deep networks from back in the day, people felt compelled to include prior knowledge and even used Bayesian priors to deal with a lack of data.
[1] http://papers.neurips.cc/paper/447-neural-control-for-rollin...
Deep RL is one of the most data hungry methods. And in physical systems you don’t get enough samples.
There are loads of data. But no manager of a shopfloor lets you produce scrap just to potentially learn.
There is an opportunity to combine ML with classical engineering models for manufacturing. Think differential equations for chemical processes. Then you end up with something like ML augmented control theory. That does work.
https://news.ycombinator.com/item?id=25542963
Many of the early critiques of RISC-V have not considered that. And many points become entirely moot in light of these techniques.
The crazy thing is ... he is not entirely wrong. Only mostly.
Wiener's wife told him a lie about Pitts. She invented an indecency involving Wiender's daugher. Both Wiener and Pitts never found out the truth about who ended their relationship.
That however means that some packages get a preferred status in the Julia ecosystem.
For any systems language, interop with C is the litmus test.
With that in mind, this new language should not require 15,000 lines of standard library. A type-safe wrapper for libc should be enough...
I got used to switching between 0/1-indexing. The only place it actually hurts is when using modulo to remain within some range. And this is needed much much less in Julia than in C and C-like.
It works in principle but is slow due to some impedance mismatches that have to be bridged. Especially, Emacs has a special string format internally that is not native utf-8.
Andy Wingo is making a great job with JIT-support for Guile. We have to see whether emacs-guile can become fast enough to replace native-elisp. At this time it doesn't look like it...
http://www.opencypher.org/articles/2019/09/12/SQL-and-now-GQ...
For the tech-savvy readers there's a lot of stuff pg did that is not directly related to his material success, but oh so cool.
For example his book on Lisp: http://www.paulgraham.com/onlisp.html
You don't write a book on Lisp because you want to get rich. You write it because you just do it for its own sake. And then he got rich immediately after publishing it.
What a cool move. For the nerds who can read the signals.
We don‘t know which works are going to be important for future generations. And just putting out a „PDF on the net“ will be gone in 20 years if there is no publishing house maintaining the original copy.
Arxiv could also take on that role. But not for the last 300 years of existing research in the publishers archives.
A blockchain / distributed ledger can be easily flooded with spam. The only way around that is to make access expensive. That works for the "actual" blockchain because the effort to put something in the chain is the money.
In applications where you don't have want expensive writes, a central gatekeeper (or at least a cabal of power-nodes) is needed to restrict access to prevent spamming.
The ngn/k implementation of the k language [1] is even more terse.
I'm under the impression his work is closer to the "radio protocol" than the infrastructure management behind. Not sure if they are related to Open-RAN though...
First, it removes the typical numpy syntax boilerplate. Due to its conciseness, Julia has mostly replaced showing pseudo-code on my slides. It can be just as concise / readable; and on top the students immeditaly get the "real thing" they can plug into Jupyter notebooks for the exercises.
Second, you get C-like speed. And that counts for numerical algorithms.
Third, the type system and method dispatch of Julia is very powerful for scientific programming. It allows for composition of ideas in ways I couldn't imagine before seeing it in action. For example, in the optimization course, we develop a mimimalistic implementation of Automatic Differentiation on a single slide. And that can be applied to virtually all Julia functions and combined with code from preexisting Julia libraries.
[1] https://www.youtube.com/playlist?list=PLdkTDauaUnQpzuOCZyUUZ...
[2] https://drive.google.com/drive/folders/1WWVWV4vDBIOkjZc6uFY3...
But IMHO Lex tries too hard getting deep/philosophical answers from his guests. And some guests clearly are not into “can we ever understand the brain and what would that even mean?”-type discussions.
If you want to see a real AI bullshit artist in action, look up recent appearances of Ben Goertzel.
He speaks French after all...
You introduce bias by your selection of measurements. Plus a large portion of the earth is scantly inhabited with no weather stations in place. Like the poles or international waters.
Instead you should look at satellite measurements of the temperature across the entire planet. These are widely available. The scientific discourse and the available evidence is much more advanced than "hey it became colder in those 20 places".
https://en.wikipedia.org/wiki/Satellite_temperature_measurem...
I don't have my "media libraries" from 20 years ago.
As soon as a tool tries to move my files into an internal representatation I cannot control, I delete the tool.
Too bad. I liked having a player that emphasized playing "files" instead of loading everything into some opaque "media library" first.
Let's see how long it takes before the monetization of the new "iTunes VLC" kicks in.
There is support for many different "frontend" architectures: Win32/MacOS/Gtk/<Motif and many more old X11 toolkits>
But a lot of code was just duplicated when a new frontend architecture was added. And started to grow into different directions. The code is littered with #ifdef and there is no clear API for the fronted architectures to sit on top of.
For example, font handling is different for most frontends. And this difference leaks into the core part of Emacs where line-breaks are managed, etc.
There is work towards a "pure GTK" that uses Cairo as a drawing surface.
https://github.com/masm11/emacs
Imho the Cairo "drawing surface" and font handling should be the only implementation for what it does and reused for all frontend architectures. With the exception of terminal sessions...
But, Emacs devs are very conservative when it comes to "modernize". In my experience, it is a lot easier to add stuff than to clean up. That also explains the forest of #ifdef and accumulation of cruft.
https://lists.gnu.org/archive/html/emacs-devel/2018-03/msg00...
https://lists.gnu.org/archive/html/emacs-devel/2020-04/msg01...
And not everybody is happy about it. [Careful, flame ahead.]
But development seems to have completely stopped earlier this year. Anybody knows what's going on there?
GAIA-X self-descriptions give visibility on whether your data is (would be) in a data center that also has GPU-capacities. And if not, what you would have to pay for interconnection.
See this demo for the basic idea of the self-description graph: https://www.youtube.com/watch?v=f17c3Vpi3rA
Rather, different providers can offer services and (compute) nodes with different levels of certification / geographic location.
So a government agency / hospital / critical-Infrastructure on can use cloud offerings without loosing „digital sovereignty“ by depending on single providers or outside actors.