Hello,

while working with tdu.Matrix I have noticed couple of areas that I thought could be improved to make the experience better. Here are my ideas

`fromTable(DAT)`

- constructs tdu.Matrix from DAT. Since`fillTable(tableDAT)`

is already present, this seems like a logical addition.`fromChop(CHOP)`

- constructs tdu.Matrix from CHOP. This could be quite useful when trying to move from CHOPs to Python with some transformation.`fillConstantChop(ConstantCHOP)`

- fills matrix into Constant CHOP. Not sure if anyone else is doing this, but I find myself in such scenario sometimes and I thought it might make sense to have this as an alternative to tableDAT version.- Support tdu.Matrix in Transform CHOP and Transform SOP. I feel like the same way Geometry COMP has
`Xform Matrix/CHOP/DAT`

parameter (which accepts tdu.Matrix), Transform CHOP (and also SOP) would greatly benefit of having such option. When I get to situation where I need to use tdu.Matrix in Transform CHOP, I need to do 9 expressions where I decompose() the matrix and select correct indexes. Not only it is error prone, it also adds quite some overhead due to doing decompose() for each parameter.

What do you think? Thanks