Closed jdh8 closed 2 months ago
Can you please include how you expect ttnn call looks like after the conversion?
Conversion for other ops later expands (kw)args for the underlying ttnn
op.
However, with the error message above, kwargs
looks as is (a dictionary).
Invoked with: <ttnn._ttnn.operations.creation.arange_t object at 0x7fcf9895b230>, 4; kwargs: end=100, step=3, device=<ttnn._ttnn.deprecated.device.Device object at 0x7fcf58757970>
Moreover, ttnn
ops generally follow PyTorch function signatures. However, as per the spec and the error messages, ttnn.arange
takes stop
instead of end
, but the op conversion tries to fill in end
(using PyTorch naming).
arange(start: int = 0, stop: int, step: int = 1, dtype: ttnn.DataType = ttnn.bfloat16, device: ttnn.Device = None, memory_config: ttnn.MemoryConfig = ttnn.DRAM_MEMORY_CONFIG
-- https://docs.tenstorrent.com/tt-metal/latest/ttnn/ttnn/ttnn/arange.html
It is great to track such issues, but it is trivial to remap arguments and enable lowering
This issue is no longer valid. I got the errors because I was using an old version of tt-metal. Everything was fixed when I updated tt-metal.
Argument types mismatch while converting
aten.arange
tottnn.arange
: