magistraleinformaticanetworking:spm:spm1617knl
Differenze
Queste sono le differenze tra la revisione selezionata e la versione attuale della pagina.
Prossima revisione | Revisione precedente | ||
magistraleinformaticanetworking:spm:spm1617knl [21/12/2016 alle 07:11 (8 anni fa)] – Marco Danelutto | magistraleinformaticanetworking:spm:spm1617knl [19/01/2017 alle 16:10 (8 anni fa)] (versione attuale) – [OpenCV] Marco Danelutto | ||
---|---|---|---|
Linea 1: | Linea 1: | ||
- | ====== KNL howto ====== | + | ====== |
+ | |||
+ | |||
+ | ===== README FIRST ===== | ||
+ | //**In case you see messages on the terminal(s) used requiring you to leave the machine from any one of the following users: | ||
+ | |||
+ | * mau | ||
+ | * cisterni | ||
+ | * marcod | ||
+ | * torquati | ||
+ | |||
+ | please logout immediately after killing all your processes (foreground and backgroud). The machine is provided by the ITC and it may be the case it will be needed for short demos and experiments. **// | ||
+ | |||
+ | ===== Then read this ... ===== | ||
==== Machine address ==== | ==== Machine address ==== | ||
The machine address is **ninja.itc.unipi.it** | The machine address is **ninja.itc.unipi.it** | ||
+ | |||
+ | ==== Differences with the KNC (old machine) ==== | ||
+ | |||
+ | This is machine that directly boots as a Xeon PHI KNL. No need to ssh micX or to compile with the -mmic flag. To run on the 64 cores, just use icc (with any of the " | ||
+ | < | ||
+ | icc -std=c++11 mymain.cpp -pthread -o mymain | ||
+ | ./mymain | ||
+ | </ | ||
+ | |||
==== Tools ==== | ==== Tools ==== | ||
Linea 10: | Linea 32: | ||
in order to be able to use the compiler. | in order to be able to use the compiler. | ||
- | The machine also has a g++ compiler, but for the project you have to use the Intel compiler. | + | The machine also has a g++ compiler, but for the project you **must** |
+ | |||
+ | ==== Java ==== | ||
+ | Standard Java JDK 8 is installed under | ||
+ | < | ||
+ | / | ||
+ | </ | ||
+ | Please consider adding / | ||
+ | < | ||
+ | export PATH=/ | ||
+ | </ | ||
+ | (to be executed in the shell or added to the .bashrc) | ||
+ | |||
+ | ==== Programming framework ==== | ||
+ | The cores in the machines are "kind of" Atom cores. Therefore the sequential performance of the single core is poor. You'll experience this while compiling. It takes seconds to compile simple C++ programs with the -O3 enabled. | ||
+ | |||
+ | ==== OpenCV ==== | ||
+ | The library is installed under | ||
+ | < | ||
+ | Refer to the documentation at | ||
+ | < | ||
+ | to look for configuration and compile options, library functions and parameters etc. | ||
+ | |||
+ | Remember the library may be used **only** | ||
+ | * to read frames from a video file | ||
+ | * to convert the frames to bitmaps | ||
+ | * to convert bitmaps to frames | ||
+ | * to write the frames to the output video file | ||
+ | that is for video file I/O. | ||
+ | |||
+ | All the filters used should be implemented by yourself. | ||
+ | ==== ffmpeg ==== | ||
+ | I installed ffmpeg under < | ||
+ | ==== Video filters ==== | ||
+ | For the " | ||
+ | * blur | ||
+ | * sobel | ||
+ | for the two stages of the filtering process. | ||
+ | You may consider alternatively: | ||
+ | * a filter transforming the video in a black and white video | ||
+ | * a threshold filter | ||
+ | Even if OpenCV provides the filters natively, you have to implement your own filters. |
magistraleinformaticanetworking/spm/spm1617knl.1482304295.txt.gz · Ultima modifica: 21/12/2016 alle 07:11 (8 anni fa) da Marco Danelutto