Correct transformation of second-order tensors in adapters

[han-ol]

Currently, only first-order tensors, a.k.a. vectors can be transformed in both forward and inverse direction through an adapter object.

Can we transform also different orders, particularly second-order?

The question arises because a PointInferenceNetwork can estimate the covariance matrix of the inference_variables.
Some adapters represent a change of basis and origin, for example, standardize is a linear coordinate transformation from "original coordinates" to "standardized coordinates".
Thus, the inference_variables live in the standardized coordinates, and the covariance matrix needs to be adapted in inverse direction to relate to unstandardized coordinates.

When a covariance matrix is estimated in the standardized coordinates, the inverse of the coordinates transformation is different from naively transforming matrix columns as if they were vectors in standardized coordinates.
Rather, a covariance matrix ${\mathrm{\Sigma }}^{-1}$ transforms as an order 2 tensor: the basis change matrix $A$ is multiplied from both sides $A^T{\mathrm{\Sigma }}^{-1}A$.
For standardize, $A=diag({\sigma }_i)$ with ${\sigma }_i$ the standard deviations for each dimension, so $A^T{\mathrm{\Sigma }}^{-1}A={\mathrm{\Sigma }}^{-1}\cdot diag({\sigma }_i^2)$.

Solutions to this issue are likely related to a separate issue on keeping track of jacobians of adapter transforms, as mentioned in #245.

[paul-buerkner]

For non-linear transformations, I see little hope that we can make it work generally for point estimates. There are some combinations of point estimates and transformations that work such as quantiles and strictly monotonic transforms. But I think that, for now, we should warn somewhere when a point estimate is passed through a non-linear transformation and recommend to just not use these transformation with pointInferenceNetworks.

Standarize is a bit of a different situation, both because it is linear and because it is so important for the networks to work in a stable manner in lots of situtations. So mean and quantiles can just be back transformed through standardize and all is well.

Now, for a covariance matrix the situation is different as you highlight above. Same actually for only the variance since we need to square the scaling.

I suggest something like the following solution to this general problem (covariance matrix is even harder than this):

Every point estimation loss implemented natively by us (e.g. squared loss) knows which point estimate it produces (e.g., mean). So we can enrich it by a structure telling us what to do with inverese transforms. This is turn could be a dict of 3 options.

• Names of transforms that are valid for this point estimate, such that the point estimate can be safely transformed by the default approach (e.g., standardize for mean)
• Names of transforms that are invalid for this point estimate and whose correct value cannot be computed in general without additional knowledge (e.g., exp/log for mean). There, we would probably perform the transformation anyway but warn that this will likely lead to biased estimates.
• A dict of transforms for which we know the correct inverse transform for a given point estimate, but that transform is different from what the adapter has implemented. If such a new transform is specified, it will replace the standard adapter (back-)transform. E.g. We want to compute the variance when passed through standardized. Then our new backtransform would ignore the mean and square the scaling.

This approach of course needs a bit of work for each point estimation loss but I believe it can be done in a structured and tidy way such that the maintainence effort of this feature would be small.

What do you think @han-ol and @stefanradev93 ?

[han-ol]

Until we resolve this issue fully in the future, changes introduced in PR #380 warn the user when adapter(data, inverse=True) is called on a covariance estimator. The covariance estimator is the only one that currently cannot be adapted safely.

As it stands, the warning is raised even if the adapter does not contain a problematic transformation.

To be more specific in raising a warning, we would need a reliable way to determine, whether (a part of) a variable that is eventually renamed to "inference_variables" is standardized at some point.
For now such improvements have low priority in my opinion, but I agree it is achievable in a tidy and maintenance friendly way (with some work). Specifically, your proposal seems a good goal.

[LarsKue]

@han-ol do you think we can close this issue as resolved for now? Both Stefan and I are fine with the warning for now as it is.