🚀 Feature Request
Combining #97 and #109, it is possible to facilitate the resolution of mlm:accelerator (and other similar properties) with corresponding torch.device when exporting programs/archive representing the model.
Utility methods to perform this mapping should be provided and employed wherever applicable.
🔉 Motivation
Reduce the number of inputs that have to be explicitly provided by users, and automate their resolution to avoid MLM metadata inconsistencies. However, parameters must remain available to provide "overrides" in case a given device is explicitly desired for one situation or another.
📡 Alternatives
Leave it up to users to map and provide devices explicitly in each place.
📎 Additional context
🚀 Feature Request
Combining #97 and #109, it is possible to facilitate the resolution of
mlm:accelerator(and other similar properties) with correspondingtorch.devicewhen exporting programs/archive representing the model.Utility methods to perform this mapping should be provided and employed wherever applicable.
🔉 Motivation
Reduce the number of inputs that have to be explicitly provided by users, and automate their resolution to avoid MLM metadata inconsistencies. However, parameters must remain available to provide "overrides" in case a given device is explicitly desired for one situation or another.
📡 Alternatives
Leave it up to users to map and provide devices explicitly in each place.
📎 Additional context