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
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The reason will be displayed to describe this comment to others. Learn more.
@Jack-Khuu Not sure why args.device == "fast" should be treated as a functional nop relative to executor spec? Did I miss something with the original PR?
My thinking was that if the user says "fast" device, they should get the fastest device on this node with them same outcome as always.(To enable this, "fast" is no longer the arg parser default, so we should not get args.device=="fast" unless user specifically said so. )
4697764
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Jack-Khuu Not sure why
args.device == "fast"
should be treated as a functional nop relative to executor spec? Did I miss something with the original PR?My thinking was that if the user says "fast" device, they should get the fastest device on this node with them same outcome as always.(To enable this, "fast" is no longer the arg parser default, so we should not get
args.device=="fast"
unless user specifically said so. )4697764
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Prior to adding this condition, providing fast as an arg crashed the entire command since it was never resolved to an actual device.
#1373
Edit: Ah but, this fix PR is also wrong since fast can no longer override the quantize config, I'll spin something up