The paper describes a split Alvarez (Lohmann) lens [1,2] with a phase modulator between them. I didn't do the math, but it looks like the phase modulator is optically equivalent to a mechanical shift of the Alvarez lenses over regions of the field of view. Alvarez lenses have higher aberrations, and are relatively bulky, compared to normal lenses. AR was referenced in the paper, but this lens will be hard to make compact, and have great image quality, over large fields of view.
Each pixel of such a scanner would need to somehow scan the spectral content. For example, imagine an array of fibers each transporting light from image plane pixel coupled to a spectrometer (bulky, expensive). Slit (a.k.a. push broom) scanners take each pixel of its slit and disperses the light perpendicular to the slit onto a 2D sensor array (more compact, 1D mechanical scan required). I recall seeing spectral (color) filters made from dispersive materials sandwiched between rotating polarizers to filter (scan) the light entering camera (expensive, compact).
Sounds great, but I often find myself wondering "where's the catch?". There's not enough info in the abstract judge for myself whether the idea has legs. I'm sure it'll get more press if there's something to it.
As I read the article. The tsunami wave (water) displaces air at the surface and creates a sound wave, and gravity waves, that travels to the upper atmosphere. These waves then interact with electrons in the upper atmosphere.
Thanks. I wasn't thinking of enums. To the extent one designs a trait to use an enum type (or the enum to satisfy the trait), one wins. But it seems impossible to avoid code to handle all future {type, op} combinations. The nice thing I've seen with Rust is the ability to add to what's been done before without breaking what already works. I'm thinking of "orphan rules" here.
The article's `expression problem matrix` section states that the goal is make it `easy to add ops` and `easy to add types`. My learning of Rust so far indicates Rust satisfies both: traits satisfies the `ops` problem for all traits you want to support the op, and Rust's implementations (impl) solves the problem of adding types. Of course, for each new {op,type} combination, one must write the code, but Rust allows you to do that with its trait and generic systems. Am I missing something important?
1. https://www.laserfocusworld.com/optics/article/16555776/alva... 2. https://pdfs.semanticscholar.org/55af/9b325ba16fa471e55b2e49...