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
About Chapter 2.1.4 and 2.3.7, there is too much talk about the broadcast mechanism. It's like the implicit type conversion rule, which is not a good programming style.
About 2.3.7, a good programming style is to call the functions supplied by torch.nn.functional:
If there is really a need to use the broadcast mechanism, recommend first checkout the broadcast output:
np.broadcast_arrays(x, y)
torch.broadcast_tensors(x, y)
This helps to check what the internal broadcast mechanism will output. The broadcast mechanism is an internal mechanism in NumPy designed for speeding up computations. However, encouraging the use of this style of code is not a good idea.
The text was updated successfully, but these errors were encountered:
a358003542
changed the title
Please do not talk too much about the boardcast mechnism.
Please do not talk too much about the broadcast mechanism.
Mar 21, 2025
About Chapter 2.1.4 and 2.3.7, there is too much talk about the broadcast mechanism. It's like the implicit type conversion rule, which is not a good programming style.
About 2.3.7, a good programming style is to call the functions supplied by
torch.nn.functional
:If there is really a need to use the broadcast mechanism, recommend first checkout the broadcast output:
This helps to check what the internal broadcast mechanism will output. The broadcast mechanism is an internal mechanism in NumPy designed for speeding up computations. However, encouraging the use of this style of code is not a good idea.
The text was updated successfully, but these errors were encountered: