The `torch.compile` API itself will not be available from C++. That means that you won't get the pytorch 2.0 performance gains if you use it via C++ API.
There's no plan to deprecate the existing C++ API, it should keep working as it is. However, a common theme of all the changes is implementing more of pytorch in python (explicitly the goal of primtorch), so if this plan works it could happen in the long run.
Do you actually think it would be a good thing if an IRB was required for this type of thing? Sure, it's "human experimentation" but the likelihood for any serious harm is basically zero.
It goes with the zeitgeist to argue for what makes the life of big tech companies hard, but they are big enough that they can afford things like that. It's smaller companies and academics that would end up not being able to innovate as much
Go down that road and you end up with an IRB evaluation requires for an A/B test that changes the color of a button
That it is a little different. There you are estimating a continuous parameter (which happens to be interpretable as a probability) and it makes sense to have a probability distribution over that.
But if you are talking about whether a single discrete events will happen or not, a single number (the probability) already fully captures the uncertainty about it.
They are giving probabilities for discrete events, which already captures their level of uncertainty. Probabilities of probabilities (i.e., a probability distribution of a probability) are not very useful concepts.
Yes, 100% agree with last paragraph. And the waiting for me to type Hello back pattern is so annoying.
This really should be basic work etiquette. Type your whole question in one go. If you want to you can include pleasantries at the beginning but never if there is going to be a more than 2 second interval between them and your actual question.
Should probably be part of first day orientation for new hires.
There's no plan to deprecate the existing C++ API, it should keep working as it is. However, a common theme of all the changes is implementing more of pytorch in python (explicitly the goal of primtorch), so if this plan works it could happen in the long run.