<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>DSpace Collection:</title>
    <link>http://localhost:8080/xmlui/handle/123456789/2738</link>
    <description />
    <pubDate>Tue, 23 Jun 2026 06:29:23 GMT</pubDate>
    <dc:date>2026-06-23T06:29:23Z</dc:date>
    <item>
      <title>LARGE SCALE PERSON RE-IDENTIFICATION USING PART BASED DEEP HASHING</title>
      <link>http://localhost:8080/xmlui/handle/123456789/2739</link>
      <description>Title: LARGE SCALE PERSON RE-IDENTIFICATION USING PART BASED DEEP HASHING
Authors: Jain, P.; Jain, E.; Dadhich, S.; Tonpe, S.; Kolapkar, A. V.
Abstract: It is important to perform real time search while Large scale Person re-identification on a large gallery. The&#xD;
conventional methods use to focus on discriminative learning which is probabilistic approach of learning. In this&#xD;
proposed project we attempt to use deep learning while integrating it with hashing which provides a framework to&#xD;
evaluate productivity, precision and reliability of Large scale Person re-identification. We use augmentation for creating&#xD;
artificial training images through different ways of processing or combination of multiple processing such as random&#xD;
rotation, shifts, shear and flips etc. We propose Part based deep Hashing (PDH) in which augmented images are the&#xD;
input of deep learning architecture. All the augmented images have different identity. We are using whole image and use&#xD;
it for training deep hashing architecture. We use a ternion loss function which calculates the hamming distance of the&#xD;
pedestrian image. The hamming distance of the images with same identity is smaller than the one with different identity.&#xD;
In this project we use standard large scale dataset specifically Market-1501 &amp; Market-1501 +500K.</description>
      <pubDate>Thu, 01 Mar 2018 00:00:00 GMT</pubDate>
      <guid isPermaLink="false">http://localhost:8080/xmlui/handle/123456789/2739</guid>
      <dc:date>2018-03-01T00:00:00Z</dc:date>
    </item>
  </channel>
</rss>

