Closed chensy7 closed 10 months ago
Hi Siyuan,
Thank you for bringing up this issue.
We've identified that the problem arises when a layer dimension is mapped to multiple hardware dimensions. I'm pleased to inform you that we have addressed and resolved this issue in the latest update.
In terms of the mapping file, I think in the ZigZag version released in September, the spatial_mapping
dictionary must be provided (you can refer to inputs/mapping/default.py for an example). However, in the current version, this requirement has been relaxed, and the spatial mapping will be automatically generated if omitted. In such cases, it is advisable to provide the spatial_mapping_hint
dictionary instead (you can refer to tests/main/test_with_mix_spatial_mapping/test_tesla_npu_like.py for an example). Omitting both dictionaries will result in a fully flexible spatial mapping searching space, which may not accurately represent a real hardware system.
Please rerun your script with the latest ZigZag version and let us know if you encounter any further issues.
Best regards, Jiacong
Hi Jiacong,
Thanks for your reply and for taking a look at the issue. I can verify that the bug has been fixed on my end too. I'm closing the issue.
Siyuan
Hello Zigzag team,
I'm running spatial mapping search on the Edge TPU example using Zigzag, and I'm getting the following error:
Here is the code to reproduce this run:
and the mapping file I used is simply:
This seems to happen for all examples with 4 levels of MACs (Edge TPU, Tesla NPU, Meta and Ascend) running Alexnet/Resnet18/MBNetv2, but not for the TPU example with 2 levels. Also FWIW, this happened after I pulled from the Zigzag repo yesterday. I don't get this error with a local copy of Zigzag timestamped Sep 25th.
Am I doing something wrong? Any help is appreciated. Thanks! Siyuan