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
Currently, transforms in the RobertaBundle are defined as anonymous lambda functions. These are not pickleable and cannot be imported for use anywhere else.
Hey I would recommend taking a look at #1482 where we actually moved away from using classes to using scriptable sequential container to create the transform. The main benefit from this was as follows
As we added necessary primitive transforms, along with support of #1481 for text transforms, we can easily avoid overhead of maintaining a separate class for model transform. Instead in this PR, we argue that this can be accomplished in much more sustainable way by directly constructing sequential transform as part of Model Bundle object.
As such do you think we want to migrate back to using classes for our model transforms?
Currently, transforms in the RobertaBundle are defined as anonymous lambda functions. These are not pickleable and cannot be imported for use anywhere else.
Ex proposal:
-->
The text was updated successfully, but these errors were encountered: