Deliverable 5.2 - the School of Engineering and Design - Brunel ...
Deliverable 5.2 - the School of Engineering and Design - Brunel ... Deliverable 5.2 - the School of Engineering and Design - Brunel ...
ICT Project 3D VIVANT– Deliverable 5.2Contract no.:248420Search & Retrieval Mechanisms &Toolsname under the “descr” folder. Moreover, under each descriptor folder there are two subfolders (seeFigure 6): one for the extracted features (“features” folder) and one for the bag-of-words vector(“words” folder) that will be generated for each feature file, using a generated codebook (see section3.3).The Search and Retrieval Framework supports the following descriptor extraction algorithms for theextraction of local features of the multimedia objects:1. CSIFT: Colour SIFT2. OSIFT: Opponent SIFT. A Colour SIFT variant where a different colour model is used.3. GB: Geometric Blur4. SSIM: Self Similarity5. PI: Projection Images. Applicable only in depth dataThe User Interface for extracting descriptors (see Figure 7) enables the user to select whether thesystem will generate descriptors for one descriptor algorithm or for all of them. Based on the selectionof the user, the system triggers one or multiple threads that extract descriptors for the same raw data(under “data” directory) in parallel. From this step until the finish of the final descriptors the systemworks without the need for user intervention. The extraction of the local descriptors is a lengthyprocess and thus a progress bar informs the user for the progress of the computations (Figure 8).Moreover, the console window prints log messages to give more information on the runningprocesses.Figure 7: Descriptors Extraction User Interface4/03/2013 14
ICT Project 3D VIVANT– Deliverable 5.2Contract no.:248420Search & Retrieval Mechanisms &ToolsFigure 8: Descriptor extraction is a lengthy process. The console prints logs on the progress of the processAs it was stated above, each descriptor extraction algorithm generates its own local feature vectorsand stores them under the “descr” directory in the corresponding name. To unify the process of datastorage and ease the Input /Output processes we chose to have a unique format for all the availablelocal features files. The format include the algorithm name, the dimensions of the feature vector, thenumber of the local features in the file and then one vector per line along with the positioninginformation for each local feature vector. The file format is presented in Figure 9.Figure 9: file format for the local features fileWhen the descriptor extraction processes finish, the bag-of-words histogram should be computed. Tocalculate this final histogram a codebook is needed. Section 3.3 discusses this process.4/03/2013 15
- Page 1 and 2: ICT Project 3D VIVANT- Deliverable
- Page 3 and 4: ICT Project 3D VIVANT- Deliverable
- Page 5 and 6: ICT Project 3D VIVANT- Deliverable
- Page 7 and 8: ICT Project 3D VIVANT- Deliverable
- Page 9 and 10: ICT Project 3D VIVANT- Deliverable
- Page 11 and 12: ICT Project 3D VIVANT- Deliverable
- Page 13: ICT Project 3D VIVANT- Deliverable
- Page 17 and 18: ICT Project 3D VIVANT- Deliverable
- Page 19 and 20: ICT Project 3D VIVANT- Deliverable
- Page 21 and 22: ICT Project 3D VIVANT- Deliverable
- Page 23 and 24: ICT Project 3D VIVANT- Deliverable
- Page 25 and 26: ICT Project 3D VIVANT- Deliverable
ICT Project 3D VIVANT– <strong>Deliverable</strong> <strong>5.2</strong>Contract no.:248420Search & Retrieval Mechanisms &ToolsFigure 8: Descriptor extraction is a lengthy process. The console prints logs on <strong>the</strong> progress <strong>of</strong> <strong>the</strong> processAs it was stated above, each descriptor extraction algorithm generates its own local feature vectors<strong>and</strong> stores <strong>the</strong>m under <strong>the</strong> “descr” directory in <strong>the</strong> corresponding name. To unify <strong>the</strong> process <strong>of</strong> datastorage <strong>and</strong> ease <strong>the</strong> Input /Output processes we chose to have a unique format for all <strong>the</strong> availablelocal features files. The format include <strong>the</strong> algorithm name, <strong>the</strong> dimensions <strong>of</strong> <strong>the</strong> feature vector, <strong>the</strong>number <strong>of</strong> <strong>the</strong> local features in <strong>the</strong> file <strong>and</strong> <strong>the</strong>n one vector per line along with <strong>the</strong> positioninginformation for each local feature vector. The file format is presented in Figure 9.Figure 9: file format for <strong>the</strong> local features fileWhen <strong>the</strong> descriptor extraction processes finish, <strong>the</strong> bag-<strong>of</strong>-words histogram should be computed. Tocalculate this final histogram a codebook is needed. Section 3.3 discusses this process.4/03/2013 15
Change language