I have written a simple script (script.sh) like this for profiling just one test image:
./build/examples/cpp_classification/classification.bin \ models/bvlc_reference_caffenet/deploy.prototxt \ models/bvlc_reference_caffenet/bvlc_reference_caffenet.caffemodel \ data/ilsvrc12/imagenet_mean.binaryproto
\ data/ilsvrc12/synset_words.txt \ examples/images/cat.jpg
And another script (script_100.sh) to classify 100 test images:
for file in *
./classification.bin deploy.prototxt bvlc_reference_caffenet.caffemodel imagenet_mean.binaryproto synset_words.txt $file
If I don’t attach the script in the “File” option, rather type in the executable “classification.bin” and provide the arguments in the “Arguments” space, it profiles the app without any issues. But if I give the script.sh or script_100.sh as the “File”, it runs the script with the expected output but throws the error message without giving me any profiling data.
The --profile-all-processes works for 100 test images. My concern here is that we can’t attach a shell script to the “File” option. I was wondering if this is a bug in NVVP or am I missing something here?