Forwarding broadcasted scalar metadata in Scalify tracer. #97
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
scalify
interpreter/tracer is now properly tracking which tensors arejust broadcasted scalars, helping then to refine the conversion rule to
ScaledArray for these.
In practice: it means (finally!) proper full scale propagation in MNIST training,
resulting in stable training with dynamic rescale.
TODO: we still need to understand why
scaled_mul
requires ScaledArray promotion toget the MNIST training example running. This requirement has been lifted in
div/add/sub
thanks to this PR.