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
Expose module property from ShardedDDP again which points to underlying wrapped model.
Motivation
Recent PR #611 made a lot of class members in ShardedDDP private. Unfortunately, this behavior is now different from DDP which exposes module property to expose the underlying model directly. In MMF's checkpointing system, we use this property to extract out the underlying model to allow checkpoints to work agnostic of distributed system or not.
Pitch
I can open up a PR to expose it as a property if possible.
Alternatives
I can hack around in our code to check _module but the change in itself is backwards incompatible from at least 3.3 to 3.6 version of fairscale.
The text was updated successfully, but these errors were encountered:
apsdehal
changed the title
[ShardedDDP] Expose 'module
[ShardedDDP] Expose 'module' property from ShardedDDP
May 3, 2021
🚀 Feature
Expose
module
property from ShardedDDP again which points to underlying wrapped model.Motivation
Recent PR #611 made a lot of class members in ShardedDDP private. Unfortunately, this behavior is now different from DDP which exposes module property to expose the underlying model directly. In MMF's checkpointing system, we use this property to extract out the underlying model to allow checkpoints to work agnostic of distributed system or not.
Pitch
I can open up a PR to expose it as a property if possible.
Alternatives
I can hack around in our code to check
_module
but the change in itself is backwards incompatible from at least 3.3 to 3.6 version of fairscale.The text was updated successfully, but these errors were encountered: