2,778 karma · joined June 15, 2016
GP is correct in that the fed funds rate (the one that makes headlines and is used for policy) isn't literally _set_ by fiat: the Fed just intervenes in the interbank money market to ensure it stays in a specified range. It has near unlimited capacity to intervene so the fed funds rate only ever strays a tiny amount outside that range, and even then it's an exceptional circumstance.
On the other hand the parent is correct in that the Fed literally sets a lot of other rates that are used for financial plumbing.
Nickles I'm sure you know this already but I'm trying to clarify so that others don't get confused by an already confusing topic.
While the size of the pie is important, so is the means of distributing the pie and the assurance that pie will be served tomorrow.
So a hash function is allowed to destroy information, whereas it's pretty important that an encryption algorithm doesn't!
But almost all of the images in that set look like grey fuzz. On average there's nothing interesting there.
I know VS Code has been making progress recently but a good jupyter competitor with some halfway decent software development features would be a game changer.
The latter looks really impressive when it’s done well, but it’d be silly to expect someone with deep security knowledge to sit down and build a spreadsheet manager from scratch. The two skill sets are just different. There is no “best”.
Capital requirements are what constrain lending in the west (I think the Chinese government does try to control lending in part via a reserve requirement). For example, the "Core Tier 1 Capital Ratio" [0] is extremely important in this regard.
https://www.investopedia.com/terms/t/tier-1-capital-ratio.as...
So we're talking about the case when tensors don’t need to be multilinear functions on a product of vector spaces.
Each element of V* is (trivially) a tensor and a linear function on V. Each element of V is (trivially) a tensor and a linear function on V*. However, not all linear functions on V* are in V. So V** is bigger than V. No problem so far.
But all elements of V** are functions on (trivial) products of vector spaces, and by definition all functions in V** are linear. So how have we misunderstood each other here?
Ok, so this feels like the crux of the matter. So how does the fact that V** is not isomorphic to V make the tensor product construction a more general concept than the linear function construction?
I think I'm missing part of the argument. So we have a polynomial p in F[x,y]. The claim in my previous post basically says that there's always a way to associate p with a linear map that takes two elements of the dual space of F[x] and produces a real number. I don't see why that's impossible here.
I'm not familiar with the infinite-dimensional case. Do you have an example of a tensor that isn't a multilinear function on a product of vector spaces? I'd be interested to refine my understanding here.
To move from the mathematician's definition to the ML definition, pick a basis for your row and colum vectors. Now if you want the (i, j, ...) element of the multidimensional array, gather the vectors with one in the i-th position and zero elsewhere, the j-th position and zero elsewhere, etc. Then feed them to the tensor in that order.
It's easiest to see how it works with row vectors (rank (0,1)), column vectors (rank (1, 0)) and matrices (rank (1, 1)) and work from there.
For machine-learning types, a tensor is a multidimensaional array of numbers that admits certain operations (addition, subtraction, hadamard product, etc) [0]
For mathematicians, a tensor is a function F. We pass the function an ordered tuple of N vectors and M covectors (or, to keep things simple, N column vectors and M row vectors), and the function returns a scalar. The function F needs to be linear in each of the N vectors and M covectors. In this view, a matrix is a tensor with N=1, M=1. The operations used by machine learning types arise naturally once you crank the mathematical handle a little bit.
For physicists, a tensor is what mathematicians would refer to as a tensor field. So they take a space X (think R^N), and for each point in the space they associate a mathematician's tensor F as defined above. The properties of the function F are permitted to change from point to point. The Riemannian metric tensor is a classic example of 'tensor' according to this usage.
[0] https://machinelearningmastery.com/introduction-to-tensors-f...
And in a sense, vision is the easy part. There are whole areas like prediction and motion planning where the current state of the art isn't really up to scratch.
Edit: ah, we're probably talking about the same thing. Strassen was 1970.
[0] https://en.wikipedia.org/wiki/Matrix_multiplication_algorith...
(Not that I think it's a particularly good argument. And no, I'm not in the pocket of Big Curtain)
The issue with Kelly betting is the same as with Markowitz: knowing the parameters of the problem. If you overstate your probability of win by mis-estimating, you'll get ruined. For what it's worth, the version of Kelly betting I'm familiar with is for Bernoulli trials. I think the Gaussian version of the Kelly criterion essentially reduces to Markowitz.
Side note: kelly betting isn't new! Daniel Bernoulli knew about it back in the 1700s. Kelly just connected the formula to ideas in information theory.