Our paper has recently been accepted to a be presented at a workshop. It's a compiler paper that discusses how we generate code for a specific algorithm for a specific hardware accelerator. Unfortunately, that hardware accelerator won't be released to public soon, and our results are based on a simulator.
Two reviewers weakly accepted it, while the other two weakly rejected it. The main criticism is that while we say that we believe the ideas in the paper can be applied to public hardware, it's better to show experimental results on public hardware, which we didn't.
The honest answer to the question above is that I ran out of time to implement those ideas, and it wasn't in the company's best interest to spend time implementing that algorithm on different hardware.
The company found the code generator to be useful (at least as far as saving developer time goes, which was hard to quantify without a user study), but I'm not sure I can convince the public that these ideas are useful unless I reproduce the results on public hardware.
I was a research intern working for that hardware company when we wrote the paper. I don't work with the company any more. My PhD thesis focuses on a different topic, and I won't have the time to further carry out these experiments.
I have limited experience presenting papers. If somebody at the workshop comments or asks some version of the following questions, how should I answer them?
- Why don't you have results on public hardware?
- Do you have any plans to implement this on public hardware?
- I'm not convinced that these results are useful unless they are carried out on public hardware.
If you can also anticipate similar questions, I'd also like to know how to address them.
My full-time colleagues may not be present at the workshop, and I also think that they won't have the time to implement this "future work" either.
I've looked for similar questions, but wasn't able to find one. Hope this is not a duplicate.