-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
reference code for the dataset generation method #53
Comments
Hi, thanks for your interests to nn-Meter! We have the plan to release the code of data generation. Due to other features with higher priority, the dataset generation code is planed to be released in about May, 2022. |
Hi, I am customizing a new predictor to try nn-Meter out. To make things easier, I only changed to another Cortex cpu and still using the benchmark_model_cpu_v2.1 profiler you provided. Now I am at the final steps of Build Kernel Latency Predictor , and I realize that I won't be able test the accuray of the predictor. So I wonder how could I create my own benchmark datasets? Is it the dataset generation code you mentioned above? @JiahangXu |
That's right. To test the model level prediction accuracy, you should generate some sample based on different network architecture. We plan to release the code of data generation in about May. The idea of dataset generation is change configs, such as the output channel of every building block in Mobilenet, and the kernel size for dwconv operation, based on one fixed network architecture. After generating models in |
Hi there. I tried to profile models in pb_models.zip with benchmark_model_cpu_v2.1 on my CortexA73 device, but I can't convert the pb model to tflite format. The code I am using for example is: |
Did the dataset generation code release? I didn't find it. And could you please share the code to create the nasbench201 models? I can't create the nasbench201 models with tensorflow. |
Hi, does the reference code of dataset generation method release?
The text was updated successfully, but these errors were encountered: