You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi everyone, I'm trying tofind the optimal lambda parameter of the PowerTransform bijector with maximum lilkelihood estimation.
In order to do so I had to modify the constructor of the bijector in order to allow power to be a trainable tf.Variable.
Then code is the following:
The estimation with the MLE from the scipy library gives lambda = 0.25 but mine gives lambda = 0.64. If I use the bijector with a static value of 0.25 I can recover a distribution that is closer to the original exponential so I believe that there might be a problem with the training procedure or with the computation of the forward Jacobian in the PowerTransform bijector but I can't find it.
Anyone can help with this?
The text was updated successfully, but these errors were encountered:
indeed, the Exp bijector is just implemented as power transform with power=0. we could decouple these, exp would be very simple on its own. or we could keep the static path for efficiency but also allow a tensor input. i started removing the static path but then realized exp was using it...will take another look later.
Hi everyone, I'm trying tofind the optimal lambda parameter of the
PowerTransform
bijector with maximum lilkelihood estimation.In order to do so I had to modify the constructor of the bijector in order to allow
power
to be a trainabletf.Variable
.Then code is the following:
The estimation with the MLE from the scipy library gives
lambda = 0.25
but mine giveslambda = 0.64
. If I use the bijector with a static value of 0.25 I can recover a distribution that is closer to the original exponential so I believe that there might be a problem with the training procedure or with the computation of the forward Jacobian in thePowerTransform
bijector but I can't find it.Anyone can help with this?
The text was updated successfully, but these errors were encountered: