4 ms·

The problem for me is that, as a computer scientist, I'm focused on the numerical representation of things. Geometric algebra is presented by omitting that unti

by Asooka 5y ago

The problem for me is that, as a computer scientist, I'm focused on the numerical representation of things. Geometric algebra is presented by omitting that until the last second and instead focusing on abstract concepts and how they fit together. For example, they say "A vector is an oriented scalar value" and that already confuses me. Obviously I know what a scalar is, a scalar is one number, but what is "oriented"? Is it N numbers for the e0,...,en-1 axes? Is it N^2 numbers forming a rotation matrix? Is it just N numbers for the vector and we only call it "oriented"? I would like to see geometric algebra explained from the bottom-up - starting from the numerical representation of the objects they talk about and explaining how it gives rise to the properties they're looking for.

chriswarbo 5y ago
> Obviously I know what a scalar is, a scalar is one number Hang on, is that a Natural number, or a signed Integer? Is it place-value, and if so what's the base? Big- or little-endian? Is it fractional, and if so is it a rational (numerator and denominator), or fixed-point (what precision?), or float (how big's the mantissa?); maybe it's a unum? How about a sequence of continued fractions? This is tongue-in-cheek; but from a software perspective, all those representations have the same "API" (arithmetic). Likewise, geometric algebra is an "API"; that's essentially what an algebra is.
- melissalobos 5y ago
  I think the GP is trying to make the point that, a scalar in most numerical physics contexts is either a real or complex double precision floating point number(like a double), but they don't see how someone would represent a vector in this geometric algebra(a matrix in Eigen? or a vector in Eigen? myself I would just use a vector, but the GP was interested in the oriented part and seeemed confused). I believe they were looking for an example of someone using this in practice to solve a real problem and have some explanation of the choices made.
- faller 5y ago
  > Hang on, is that a Natural number, or a signed Integer? Is it place-value, and if so what's the base? Big- or little-endian? I fail to see how that makes any sense. OP clearly referred to the unidimensional nature of a scalar in contrast to the n-dimensional nature of a vector, or the n*m-dimensional nature of a matrix. It makes no sense to try to go off on a tangent regarding, say, the resolution of a scalar representation. Perhaps the concept of a ray gets halfway there. Perhaps the concept of a line at infinity. The concept of a scalar is familiar, as is the concept of a vector. Using the terms "scalar with a direction" to describe a vector makes no sense if you come from that starting point. Perhaps magnitude+direction vector rings a bell, because that's also a basic description of a vector. Perhaps the author made a mistake, or does not have a good math background, or is filing in his knowledge gaps by coming up with definitions . Or perhaps he's actually referring to different concepts that the readership is not familiar. Who knows? > This is tongue-in-cheek; but from a software perspective, all those representations have the same "API" (arithmetic). This assertion is quite wrong. Both scalar and vector, in this context, are data types. Describing a data types as a data type of a data type is meaningless and does not compute.
  - chriswarbo 5y ago
    > The concept of a scalar is familiar, as is the concept of a vector. > Using the terms "scalar with a direction" to describe a vector makes no sense if you come from that starting point. Now I'm confused: what is a vector, if not a "scalar with a direction" (or indeed "an oriented scalar value", as the parent quoted)? > Both scalar and vector, in this context, are data types. Describing a data types as a data type of a data type is meaningless and does not compute. I disagree; "scalar value" is an interface, supporting addition, multiplication, negation, etc. (e.g. https://hackage.haskell.org/package/base-4.16.1.0/docs/Prelude.html#t:Num https://hackage.haskell.org/package/base-4.16.1.0/docs/Prelu... https://smlfamily.github.io/Basis/real.html https://smlfamily.github.io/Basis/real.html ). Many data structures can implement this interface (Float, Double, Rational, Fixed, Nat, Int, etc.). Likewise, "vector" is an interface, supporting vector addition, scalar multiplication, and (crucially in this context) inner, wedge and geometric products. Many data structures can implement this interface (e.g. a tuple of scalars, as coefficient of a fixed orthonormal basis; a scalar length paired with angular spreads projected in fixed perpendicular planes; etc.)
orlp 5y ago
So to make this familiar, you're probably used to traditional coordinate vectors in geometry. For example a 3D vector [x, y, z]. This seems sane enough, but is actually somewhat ambiguous. Which cardinal direction map to x, y, z respectively (e.g. is z for up/down or forwards/backwards)? What direction do the axes point, e.g. is +z away or towards us? To make it unambiguous, we can define three oriented basis vectors. That is, each basis vector defines what the unit is in that direction, and which way is "positive". So I could write [3, 2, 9] as 3*xunit + 2*yunit + 9*zunit. Now in geometric algebra we also have oriented basis vectors. So they determine the unit, and the direction of the embedding space (note that this not necessarily map directly to points in your world space, which becomes especially clear when you start doing projective geometry, e.g. in 3D PGA you represent lines in your world as planes in the embedding space). Rather than xunit, yunit, etc, they are simply called e1, e2, ..., en. The key difference is that geometric algebra has the exterior product, notated ^. For example, e1 ^ e2 is the exterior product of two oriented basis vectors. You can interpret this as being an oriented basis for the space spanned by e1, e2. And similarly for e1 ^ e2 ^ e3 being an oriented basis of the volume spanned by e1, e2, e3, etc. These are called basis blades. The most general closed numerical representation of an object in geometric algebra is the multivector. Just like a traditional vector is just a bag of K coefficients for K basis vectors, a multivector is a bag of 2^K coefficients for the 2^K basis blades, one for each possible combination of the exterior product of the K basis vectors.
- faller 5y ago
  > So to make this familiar, you're probably used to traditional coordinate vectors in geometry. For example a 3D vector [x, y, z]. This seems sane enough, but is actually somewhat ambiguous. The concept of a coordinate system is not ambiguous. You have dimensions, and each can be represented as a vector that complies with specific properties, such as linear independence. > Which cardinal direction map to x, y, z respectively (e.g. is z for up/down or forwards/backwards)? That's a function of whatever coordinate transformation you wish to apply. Nevertheless, I vaguely recall from school the concept of an oriented vector space and direct coordinate system, whose definition was something like the cross product of consecutive director vectors resulted in a positive vector (right-hand rule) i.e., the direction of z is determined unambiguously by the direction of x and y. > Now in geometric algebra we also have oriented basis vectors. If I'm not mistaken, oriented referential systems are covered in intro to euclidean geometry classes. > The key difference is that geometric algebra has the exterior product, notated ^. For example, e1 ^ e2 is the exterior product of two oriented basis vectors. You can interpret this as being an oriented basis for the space spanned by e1, e2. And similarly for e1 ^ e2 ^ e3 being an oriented basis of the volume spanned by e1, e2, e3, etc. These are called basis blades. Sounds like a convoluted way to refer to basic concepts like direction vectors of a direct coordinate system. Quite bluntly, this all sounds like an attempt to reinvent euclidean geometry following a convoluted way. I mean, what does all this buy you that applying a subset of affine transformations (scaling, translation, rotation) to an orthogonal coordinate system doesn't give you already?
HelloNurse 5y ago
The traditional approach to explaining geometric algebra is "bottom up": first the types of things that the theory is about (building on vector spaces), then details of operations that make sense, then how to perform useful computations in the light of useful things that have been proven, then actual code (with a detailed knowledge of its specifications).
6gvONxR4sf7o 5y ago
People are nitpicking you, but you’re right that the presentations do tend to omit or underemphasize concrete computation. Part of this is lineage, in that it’s related to differential geometry where much of the point is that you are abstracting away computational aspects like coordinates. But to do much of the fun stuff, you need coordinates, which the community would do well to connect better with the abstractions.

by Asooka 5y ago

chriswarbo 5y ago

> Obviously I know what a scalar is, a scalar is one number Hang on, is that a Natural number, or a signed Integer? Is it place-value, and if so what's the base? Big- or little-endian? Is it fractional, and if so is it a rational (numerator and denominator), or fixed-point (what precision?), or float (how big's the mantissa?); maybe it's a unum? How about a sequence of continued fractions? This is tongue-in-cheek; but from a software perspective, all those representations have the same "API" (arithmetic). Likewise, geometric algebra is an "API"; that's essentially what an algebra is.

melissalobos 5y ago
I think the GP is trying to make the point that, a scalar in most numerical physics contexts is either a real or complex double precision floating point number(like a double), but they don't see how someone would represent a vector in this geometric algebra(a matrix in Eigen? or a vector in Eigen? myself I would just use a vector, but the GP was interested in the oriented part and seeemed confused). I believe they were looking for an example of someone using this in practice to solve a real problem and have some explanation of the choices made.
faller 5y ago
> Hang on, is that a Natural number, or a signed Integer? Is it place-value, and if so what's the base? Big- or little-endian? I fail to see how that makes any sense. OP clearly referred to the unidimensional nature of a scalar in contrast to the n-dimensional nature of a vector, or the n*m-dimensional nature of a matrix. It makes no sense to try to go off on a tangent regarding, say, the resolution of a scalar representation. Perhaps the concept of a ray gets halfway there. Perhaps the concept of a line at infinity. The concept of a scalar is familiar, as is the concept of a vector. Using the terms "scalar with a direction" to describe a vector makes no sense if you come from that starting point. Perhaps magnitude+direction vector rings a bell, because that's also a basic description of a vector. Perhaps the author made a mistake, or does not have a good math background, or is filing in his knowledge gaps by coming up with definitions . Or perhaps he's actually referring to different concepts that the readership is not familiar. Who knows? > This is tongue-in-cheek; but from a software perspective, all those representations have the same "API" (arithmetic). This assertion is quite wrong. Both scalar and vector, in this context, are data types. Describing a data types as a data type of a data type is meaningless and does not compute.
- chriswarbo 5y ago
  > The concept of a scalar is familiar, as is the concept of a vector. > Using the terms "scalar with a direction" to describe a vector makes no sense if you come from that starting point. Now I'm confused: what is a vector, if not a "scalar with a direction" (or indeed "an oriented scalar value", as the parent quoted)? > Both scalar and vector, in this context, are data types. Describing a data types as a data type of a data type is meaningless and does not compute. I disagree; "scalar value" is an interface, supporting addition, multiplication, negation, etc. (e.g. https://hackage.haskell.org/package/base-4.16.1.0/docs/Prelude.html#t:Num https://hackage.haskell.org/package/base-4.16.1.0/docs/Prelu... https://smlfamily.github.io/Basis/real.html https://smlfamily.github.io/Basis/real.html ). Many data structures can implement this interface (Float, Double, Rational, Fixed, Nat, Int, etc.). Likewise, "vector" is an interface, supporting vector addition, scalar multiplication, and (crucially in this context) inner, wedge and geometric products. Many data structures can implement this interface (e.g. a tuple of scalars, as coefficient of a fixed orthonormal basis; a scalar length paired with angular spreads projected in fixed perpendicular planes; etc.)

orlp 5y ago

So to make this familiar, you're probably used to traditional coordinate vectors in geometry. For example a 3D vector [x, y, z]. This seems sane enough, but is actually somewhat ambiguous. Which cardinal direction map to x, y, z respectively (e.g. is z for up/down or forwards/backwards)? What direction do the axes point, e.g. is +z away or towards us? To make it unambiguous, we can define three oriented basis vectors. That is, each basis vector defines what the unit is in that direction, and which way is "positive". So I could write [3, 2, 9] as 3*xunit + 2*yunit + 9*zunit. Now in geometric algebra we also have oriented basis vectors. So they determine the unit, and the direction of the embedding space (note that this not necessarily map directly to points in your world space, which becomes especially clear when you start doing projective geometry, e.g. in 3D PGA you represent lines in your world as planes in the embedding space). Rather than xunit, yunit, etc, they are simply called e1, e2, ..., en. The key difference is that geometric algebra has the exterior product, notated ^. For example, e1 ^ e2 is the exterior product of two oriented basis vectors. You can interpret this as being an oriented basis for the space spanned by e1, e2. And similarly for e1 ^ e2 ^ e3 being an oriented basis of the volume spanned by e1, e2, e3, etc. These are called basis blades. The most general closed numerical representation of an object in geometric algebra is the multivector. Just like a traditional vector is just a bag of K coefficients for K basis vectors, a multivector is a bag of 2^K coefficients for the 2^K basis blades, one for each possible combination of the exterior product of the K basis vectors.

faller 5y ago
> So to make this familiar, you're probably used to traditional coordinate vectors in geometry. For example a 3D vector [x, y, z]. This seems sane enough, but is actually somewhat ambiguous. The concept of a coordinate system is not ambiguous. You have dimensions, and each can be represented as a vector that complies with specific properties, such as linear independence. > Which cardinal direction map to x, y, z respectively (e.g. is z for up/down or forwards/backwards)? That's a function of whatever coordinate transformation you wish to apply. Nevertheless, I vaguely recall from school the concept of an oriented vector space and direct coordinate system, whose definition was something like the cross product of consecutive director vectors resulted in a positive vector (right-hand rule) i.e., the direction of z is determined unambiguously by the direction of x and y. > Now in geometric algebra we also have oriented basis vectors. If I'm not mistaken, oriented referential systems are covered in intro to euclidean geometry classes. > The key difference is that geometric algebra has the exterior product, notated ^. For example, e1 ^ e2 is the exterior product of two oriented basis vectors. You can interpret this as being an oriented basis for the space spanned by e1, e2. And similarly for e1 ^ e2 ^ e3 being an oriented basis of the volume spanned by e1, e2, e3, etc. These are called basis blades. Sounds like a convoluted way to refer to basic concepts like direction vectors of a direct coordinate system. Quite bluntly, this all sounds like an attempt to reinvent euclidean geometry following a convoluted way. I mean, what does all this buy you that applying a subset of affine transformations (scaling, translation, rotation) to an orthogonal coordinate system doesn't give you already?

HelloNurse 5y ago

The traditional approach to explaining geometric algebra is "bottom up": first the types of things that the theory is about (building on vector spaces), then details of operations that make sense, then how to perform useful computations in the light of useful things that have been proven, then actual code (with a detailed knowledge of its specifications).

6gvONxR4sf7o 5y ago

People are nitpicking you, but you’re right that the presentations do tend to omit or underemphasize concrete computation. Part of this is lineage, in that it’s related to differential geometry where much of the point is that you are abstracting away computational aspects like coordinates. But to do much of the fun stuff, you need coordinates, which the community would do well to connect better with the abstractions.