Diferență între revizuiri ale paginii „PC Lab 5”
De la WikiLabs
Jump to navigationJump to searchCbira (discuție | contribuții) |
Cbira (discuție | contribuții) |
||
| Linia 7: | Linia 7: | ||
# Run demo_ASIFT with the two included Adams as input images from the Sixtine Chapel. Horizontal result should look like this: [[Fișier:Hadam.png]] | # Run demo_ASIFT with the two included Adams as input images from the Sixtine Chapel. Horizontal result should look like this: [[Fișier:Hadam.png]] | ||
# Modify code to only do "compute_asift_keypoints" (matching is not interesting, since it was covered in the previous session) | # Modify code to only do "compute_asift_keypoints" (matching is not interesting, since it was covered in the previous session) | ||
| − | # Run the profiler | + | # Run the valgrind profiler |
| + | eg: | ||
| + | |||
| + | g++ -std=c++11 cpuload.cpp -o cpuload | ||
| + | |||
| + | // run the program with callgrind; generates a file callgrind.out.12345 that can be viewed with kcachegrind | ||
| + | |||
| + | valgrind --tool=callgrind ./cpuload | ||
| + | |||
| + | // open profile.callgrind with kcachegrind | ||
| + | |||
| + | kcachegrind profile.callgrind | ||
'''Note''': Valgrind is also great for checking memory leaks: | '''Note''': Valgrind is also great for checking memory leaks: | ||
Versiunea de la data 12 aprilie 2018 15:57
Session 5
Task: run an open-source profiler (valgrind & gprof or visual studio) and improve performance of keypoint extraction in ASIFT C++ code
- Download ASIFT project from here: http://www.ipol.im/pub/art/2011/my-asift/
- Run demo_ASIFT with the two included Adams as input images from the Sixtine Chapel. Horizontal result should look like this:
- Modify code to only do "compute_asift_keypoints" (matching is not interesting, since it was covered in the previous session)
- Run the valgrind profiler
eg:
g++ -std=c++11 cpuload.cpp -o cpuload
// run the program with callgrind; generates a file callgrind.out.12345 that can be viewed with kcachegrind
valgrind --tool=callgrind ./cpuload
// open profile.callgrind with kcachegrind
kcachegrind profile.callgrind
Note: Valgrind is also great for checking memory leaks:
valgrind --leak-check=full <path>
valgrind --tool=memcheck <path>
Points (out of 10) vs. expected performance ():
TBD
