Alexander Viand

Actually, looking at this a bit closer, the code you added above fails to parse because of the `, strided>` at the end of the type for `%3` and `%4`...

In addition to the plaintext/ciphertext moduli, there's a bunch of other parameters that are less user-visible but still necessary for bgv->poly. Here's a (likely still incomplete) list of parameters and...

Linking this to #543, which is similar, but about NTT twiddle factors and is leaning towards generating them externally and hardcoding them into the HEIR source code, rather than adding...

Re-opening this until the final PRs are merged and we have HEIR-HECO feature parity. (Or is this redundant with #571?)

That makes sense, as the current batching pass simply uses the original vector sizes (e.g., `64`) and the secret-to-bgv lowering expects tensors of secrets to be of ring size. I...

I like the idea of using `DenseArrayAttr`, though I think we should probably go for a custom textual representation that omits `dense`, as I don't think we're currently thinking about...

I'm resurrecting this issue as a parent issue/tracking issue for ongoing improvements to `--secret-to-bgv`

The major challenge with different flavors of BGV will probably be the noise management, which is quite different between different implementations. HElib has some kind of "dynamic noise estimate" going...

I wonder to what extent CSE/canonicalization can give us (some of these) for "free"...

> Here are some notes on the different packing abstractions from Fhelipe and Viaduct. At a high level, both abstractions are interchangeable and can support all three use-cases listed (packing...