Skip to content
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

[Feature Request] Provides file input for local testing #71

Open
shifeiwen opened this issue Jul 19, 2024 · 1 comment
Open

[Feature Request] Provides file input for local testing #71

shifeiwen opened this issue Jul 19, 2024 · 1 comment
Labels
question Please ask any questions on Slack. This issue will be closed once responded to.

Comments

@shifeiwen
Copy link

Is your feature request related to a problem? Please describe.
I am trying to run the llama2 demo. Through export.py, I get several .bin files of HTP. Can you provide the test input files of this model together so that I can run this model on my device using qnn-net-run. Test locally. I think there should be such files on the cloud device. Can I download them to the local computer? Thank you.

Describe the solution you'd like
export.py will export the compiled test input file

@bhushan23
Copy link
Contributor

Hi @shifeiwen that's a great suggestion.
We currently store user provided data (inference job's input dataset) and simply serialize it to numpy tensor to use along with qnn-net-run.

You can serialize input as follow

  1. For each value in input data serialize as numpy file
  2. Create input_list.txt file with key and local serialized data relative file path

You can refer to

input_prompt_processed = self.get_input_prompt_with_tags(
to get an understanding on how to convert input_prompt into tensors for input of a first model.
By running each model, you can quickly create inputs for sub-sequent model parts.

Let us know if this unblocks you running these models via qnn-net-run or have any follow up questions

@mestrona-3 mestrona-3 added the question Please ask any questions on Slack. This issue will be closed once responded to. label Aug 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Please ask any questions on Slack. This issue will be closed once responded to.
Projects
None yet
Development

No branches or pull requests

3 participants