<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Amit Kumar on Medium]]></title>
        <description><![CDATA[Stories by Amit Kumar on Medium]]></description>
        <link>https://medium.com/@amkr?source=rss-c30643800fb4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*I3TVlReeOfdM4G5vTN3QQA.png</url>
            <title>Stories by Amit Kumar on Medium</title>
            <link>https://medium.com/@amkr?source=rss-c30643800fb4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 22:51:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@amkr/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Face Recognition using Deep learning]]></title>
            <link>https://medium.com/kuzok/face-recognition-using-deep-learning-4b9eccd08558?source=rss-c30643800fb4------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b9eccd08558</guid>
            <category><![CDATA[kuzok]]></category>
            <category><![CDATA[face-recognition]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[deep-learning]]></category>
            <category><![CDATA[machine-learning]]></category>
            <dc:creator><![CDATA[Amit Kumar]]></dc:creator>
            <pubDate>Thu, 12 Sep 2019 16:15:47 GMT</pubDate>
            <atom:updated>2019-09-12T16:19:53.168Z</atom:updated>
            <content:encoded><![CDATA[<p>Let’s start with the most basic question.</p><p>What is deep learning?</p><p>Deep learning is a sub-field of Machine Learning and a significant branch of Artificial Intelligence. It aims to infer high-level abstractions from raw data by using a deep graph with multiple processing layers composed of multiple linear and non-linear transformations. Several deep learning architectures such as convolutional deep neural networks (CNNs), and recurrent neural networks have been applied to computer vision, speech recognition, natural language processing, and audio recognition to produce state-of-the-art results on various tasks.</p><p>Now coming to face recognition, It is a sequence of processes which involves first face detection followed by extraction of facial features. Below is a rough pipeline of a complete face recognition API system where you input an image and get face recognized.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/931/1*ppcmiS-2UBhfU9nmdEd6aw.png" /><figcaption>face recognition API pipeline</figcaption></figure><p>Here in this implementation, I will be using <strong>FaceNet</strong> which is a face recognition system developed in 2015 by researchers at Google that achieved then state-of-the-art results on a range of face recognition benchmark datasets.</p><p>Let’s explore about face embeddings little bit. So, what does a face embedding is exactly? Each face is compactly represented by a 128-dimensional byte vector. Now why it’s 128 why not 256 or 64? 128 is selected because according to[FaceNet] paper they performed experiments with these dimensions and below is the result.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/429/1*ZVnotdzy7ClVV7R5Cn-V4g.png" /><figcaption>Source:FaceNet (<a href="https://arxiv.org/abs/1503.03832">https://arxiv.org/abs/1503.03832</a>)</figcaption></figure><p>The differences in the performance reported above are statistically insignificant. Therefore they selected 128. However, it is possible that higher dimension requires more training to achieve the same accuracy. What kind of values is present in the 128D embedding array? It contains floating point values [0.03861399, -0.04976186, … ,0.09530648 -0.05199577].</p><p>Let’s check how the numbers actually look like.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/924/1*q7igmywnpJC60_Ait2LSHg.png" /></figure><p>Above each image is 8x16 pixels image, therefore, have total of 128dimensions each holding the value of one specific pixel. You can somewhat tell the difference between FaceID0 and FaceID1 . Below is the representation of 128D{high dimension} into 2D dimension using the result of PCA(Principle Component Analysis) which is actually used to reduce the dimensionality of a dataset. PCA uses eigenvalues and eigenvectors of the data-matrix. These eigenvectors of the covariance matrix have the property that they point along the major directions of variation in the data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/955/1*I2hYuY0b8xd-fhG4YWrEqA.png" /><figcaption>PCA</figcaption></figure><p>You can observe how similar face embeddings are being closer to each other while being apart from different kinds of faces embedding. The difference is huge because above is a representation of of a women’s and a men’s face embeddings.</p><p>Let’s explore by using t-SNE(t-Distributed Stochastic Neighbouring Entities), 3D representation of the same embeddings. t-SNE uses a probablistic approach instead of a mathematical technique.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/914/1*zV-09iK7OynAS2exGRp4WQ.png" /><figcaption>t-SNE</figcaption></figure><p>Having said so much about face embeddings let’s dive into creating APIs</p><p>An application program interface (API) is a set of routines, protocols, and tools for building software applications. Basically, an API specifies how software components should interact. A <strong>RESTful API</strong> is an application program interface (<strong>API</strong>) that uses HTTP requests to GET, PUT, POST and DELETE data. REST is an architectural style,REST stands for <strong>RE</strong>presentational <strong>S</strong>tate <strong>T</strong>ransfer. It means when a RESTful API is called, the server will <em>transfer</em> to the client a <em>representation</em> of the <em>state</em> of the requested resource.</p><p>There are a few key options for a REST API request:</p><ul><li>GET — The most common option, returns some data from the API based on the endpoint you visit and any parameters you provide</li><li>POST — Creates a new record that gets appended to the database</li><li>PUT — Looks for a record at the given URI you provide. If it exists, update the existing record. If not, create a new record</li><li>DELETE — Deletes the record at the given URI</li><li>PATCH — Update individual fields of a record</li></ul><h3>Why I did select Django REST Framework?</h3><p>Because creating APIs in Django is so easy! DRF makes serialization very easy!</p><p>Here is a small glimpse of the view inheritance of DRF</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2shEECQwNbpxMV-HGP3GHQ.png" /><figcaption>Image Source: reddit.com/<a href="https://www.reddit.com/user/sheldon392/">u/sheldon392</a></figcaption></figure><p>For more details check out the project on GitHub, Project link: <a href="https://github.com/pymit/Rekognition">https://github.com/pymit/Rekognition</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b9eccd08558" width="1" height="1" alt=""><hr><p><a href="https://medium.com/kuzok/face-recognition-using-deep-learning-4b9eccd08558">Face Recognition using Deep learning</a> was originally published in <a href="https://medium.com/kuzok">Kuzok</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Final Work Submission | GSoC’19 | CCExtractor Development]]></title>
            <link>https://medium.com/@amkr/final-work-submission-gsoc19-ccextractor-development-40a2b6c6a946?source=rss-c30643800fb4------2</link>
            <guid isPermaLink="false">https://medium.com/p/40a2b6c6a946</guid>
            <category><![CDATA[gsoc]]></category>
            <category><![CDATA[ccextractor-development]]></category>
            <category><![CDATA[final-report]]></category>
            <dc:creator><![CDATA[Amit Kumar]]></dc:creator>
            <pubDate>Wed, 21 Aug 2019 20:03:13 GMT</pubDate>
            <atom:updated>2019-08-23T16:11:35.688Z</atom:updated>
            <content:encoded><![CDATA[<p>Final Work Submission | GSoC’19 | CCExtractor Development</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iacB40sb5bf7nU2qA3Gnmw.png" /><figcaption>Image Source: <a href="https://ccextractor.org/"><strong>https://ccextractor.org</strong></a></figcaption></figure><p>Hello folks,</p><p>And thus, GSoC ends. So, I guess this marks one of the last blog posts for the Google Summer of Code 2019. And, now the task is to finally submit my work. With this blog post, I’d like to comprehensively document all of my work done through the entire Google Summer of Code 2019. This post contains all the links to major PRs and repository.</p><p><strong>Repositories:</strong></p><blockquote><strong>Poor Man’s Rekognition</strong>:</blockquote><blockquote>GitHub <a href="https://github.com/pymit/Rekognition">Link</a>: <a href="https://github.com/pymit/Rekognition">https://github.com/pymit/Rekognition</a></blockquote><blockquote><strong>Front-end for Poor Man’s Rekognition</strong>:</blockquote><blockquote>GitHub <a href="https://github.com/pymit/RekoUI">Link</a>: <a href="https://github.com/pymit/RekoUI">https://github.com/pymit/RekoUI</a></blockquote><ol><li><strong>Pull Requests:</strong> in<strong> </strong><a href="https://github.com/pymit/Rekognition"><strong>Poor Man’s Rekognition</strong></a></li></ol><p><strong><em>Merged PRs</em></strong></p><ul><li><a href="https://github.com/pymit/Rekognition/pull/4">#4: addition of FaceNet lib</a></li><li><a href="https://github.com/pymit/Rekognition/pull/5">#5: Multiface Detection &amp; Recognition</a></li><li><a href="https://github.com/pymit/Rekognition/pull/6">#6: Integration of DjangoRestFramework</a> for creating RESTful APIs for image and shifting of video processing from cv2 with scikit-video.</li><li><a href="https://github.com/pymit/Rekognition/pull/7">#7: RESTful APIs for video </a>enhancement in video processing</li><li><a href="https://github.com/pymit/Rekognition/pull/8">#8: Refactoring</a> the codebase &amp;<a href="https://github.com/pymit/Rekognition/pull/23">#23: Code Refactor</a></li><li><a href="https://github.com/pymit/Rekognition/pull/10">#10: Video feature </a>enhancement and code optimisation +<a href="https://github.com/pymit/Rekognition/pull/11"> #11</a> (related)</li><li><a href="https://github.com/pymit/Rekognition/pull/13">#13: RESTful APIs for Embeddings </a>(GET &amp; POST methods)</li><li><a href="https://github.com/pymit/Rekognition/pull/14">#14: fixing corsheader issue</a></li><li><a href="https://github.com/pymit/Rekognition/pull/15">#15: Django models and serializers</a></li><li><a href="https://github.com/pymit/Rekognition/pull/18">#16: improvement of Django models</a></li><li><a href="https://github.com/pymit/Rekognition/pull/22">#22: Integration of redis and celery</a> &amp; asynchronous execution</li><li><a href="https://github.com/pymit/Rekognition/pull/24">#24: Adding Docstrings</a> &amp; related PRs <a href="https://github.com/pymit/Rekognition/pull/34">#34</a> <a href="https://github.com/pymit/Rekognition/pull/36">#36</a> <a href="https://github.com/pymit/Rekognition/pull/38">#38</a> <a href="https://github.com/pymit/Rekognition/pull/43">#43</a></li><li><a href="https://github.com/pymit/Rekognition/pull/31">#31: creating Feedback feature</a>’s RESTful APIs <a href="https://github.com/pymit/Rekognition/pull/37">#37: related</a> PR</li><li><a href="https://github.com/pymit/Rekognition/pull/33">#33: Facial Expression </a>integration</li><li><a href="https://github.com/pymit/Rekognition/pull/39">#39: face Recognition in YouTube videos</a></li><li><a href="https://github.com/pymit/Rekognition/pull/40">#40: NSFW Classifier Integration</a></li><li><a href="https://github.com/pymit/Rekognition/pull/41">#41: Face Comparision Feature</a></li></ul><p><strong><em>Unmerged PRs:</em></strong></p><ul><li><a href="https://github.com/pymit/Rekognition/pull/45">#45: addition of unit test</a> [Work in progress]</li><li><a href="https://github.com/pymit/Rekognition/pull/44">#44: Django user authentication</a> [Work in progress]</li></ul><p><strong>2. Pull Requests:</strong> in<strong> </strong><a href="https://github.com/pymit/RekoUI"><strong>Front-end for Poor Man’s Rekognition</strong></a><strong>:</strong></p><p><strong><em>Merged PRs</em></strong></p><ul><li><a href="https://github.com/pymit/RekoUI/pull/1">#1: Listing all available embeddings or faceID,</a> create and show using cards, and integration of Image &amp; Video View components.</li><li><a href="https://github.com/pymit/RekoUI/pull/3">#3: UI for embedding creation</a></li><li><a href="https://github.com/pymit/RekoUI/pull/4">#4: Feedback feature</a> + Routing + Basic UI for video playback &amp; <a href="https://github.com/pymit/RekoUI/pull/6">related PR</a><a href="https://github.com/pymit/RekoUI/pull/6">#6</a></li><li><a href="https://github.com/pymit/RekoUI/pull/8">#8: Similar Face</a></li><li><a href="https://github.com/pymit/RekoUI/pull/9">#9: NSFW component</a> in main Image view component.</li><li><a href="https://github.com/pymit/RekoUI/pull/10">#10: API Documentation </a>and view for How to use it. <a href="https://github.com/pymit/RekoUI/pull/13">Related PR #13</a></li></ul><p><strong><em>Unmerged PRs:</em></strong></p><p><a href="https://github.com/pymit/RekoUI/pull/14">#14: User Authentication </a>[WIP]</p><blockquote><strong>All commits</strong> <a href="https://github.com/pymit/Rekognition/commits/master">https://github.com/pymit/Rekognition/commits/master</a></blockquote><p><strong><em>How to setup this project locally?</em></strong></p><blockquote><a href="https://github.com/pymit/Rekognition/wiki/Project-Setup-in-Ubuntu-18.04"><strong>This wiki link</strong></a><strong> will guide you set up the project locally.</strong></blockquote><p><strong>Links to previous report blogs</strong></p><ul><li><a href="https://medium.com/@amkr/gsoc19-with-ccextractor-development-8a69a8ae78fc">Blog Link 1</a>: GSoC with CCExtractor Development</li><li><a href="https://medium.com/@amkr/week-1-gsoc19-ccextractor-development-eab8c4c1fda8">Blog Link 2</a>: Project Architecture | Tools Selection</li><li><a href="https://medium.com/@amkr/week-2-gsoc19-ccextractor-development-e4ffb6d54376">Blog Link 3</a>: Video Processing | Embedding Visualization</li><li><a href="https://medium.com/@amkr/week-3-gsoc19-ccextractor-development-e6be1d1e1fb4">Blog Link 4</a>: Video Processing Improvement</li><li><a href="https://medium.com/@amkr/week-4-gsoc19-ccextractor-development-df890ffa2b46">Blog Link 5</a>: Frontend with ReactJS</li><li><a href="https://medium.com/@amkr/week-5-gsoc19-ccextractor-development-ff895a985d9c">Blog Link 6</a>: Celery | Redis | Asynchronous Execution</li><li><a href="https://medium.com/@amkr/week-6-7-gsoc19-ccextractor-development-8173ce62a0bf">Blog Link 7</a>: TensorFlow Serving | Facial Expression</li><li><a href="https://medium.com/@amkr/final-phase-gsoc19-ccextractor-development-4d9f5d5aefb0">Blog Link 8</a>: Final Phase work submission</li><li><a href="https://medium.com/@amkr/final-work-submission-gsoc19-ccextractor-development-40a2b6c6a946">Blog Link 9</a>: Final Report</li></ul><h4>Future with Rekognition</h4><p>These past three months were a journey of a steep learning curve. A lot of things has been achieved in this period but yet the path doesn’t end here. Lots of improvement and the integration of new features can be achieved in this project. Here are few things which I think will improve this project.</p><ul><li>A more robust video processing method.</li><li>Integration of object scene detection.</li><li>Natural language processing</li><li>Docker &amp; Kube support for the main repository.</li><li>Better unit tests.</li><li>Deployment of the project</li></ul><p><a href="https://github.com/pymit/Rekognition/projects">GitHub kanban board link</a> which lists all the future upgrades, work in progress and all the works done with corresponding commits and PRs mentioned.</p><h3><strong>Conclusion</strong></h3><p>I’ve had a wonderful time during these 3 months and have learned plenty of things. I am thankful to my primary mentor <a href="https://github.com/jlochter">Johannes Lochter</a>, and<a href="https://github.com/cfsmp3"> Carlos Fernandez Sanz </a>, for providing me this opportunity and all the help and support they provided. I’m also grateful to all the members of <strong>CCExtractor Development</strong> for their quick responses, open interactions, healthy and constructive discussions.</p><p>And most importantly, I express my gratitude to the <strong>people behind the Google Summer of Code</strong>. I had a very enjoyable experience working in GSoC 2019 with <strong>CCExtractor Development</strong>. <strong>I will definitely</strong> <strong>keep contributing in open-source world!</strong></p><p>Happy Coding!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=40a2b6c6a946" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Final Phase | GSoC’19 | CCExtractor Development]]></title>
            <link>https://medium.com/@amkr/final-phase-gsoc19-ccextractor-development-4d9f5d5aefb0?source=rss-c30643800fb4------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d9f5d5aefb0</guid>
            <category><![CDATA[reactjs]]></category>
            <category><![CDATA[final-phase]]></category>
            <category><![CDATA[ccextractor-development]]></category>
            <category><![CDATA[gsoc]]></category>
            <category><![CDATA[rekognition]]></category>
            <dc:creator><![CDATA[Amit Kumar]]></dc:creator>
            <pubDate>Wed, 21 Aug 2019 20:00:42 GMT</pubDate>
            <atom:updated>2019-08-21T20:00:42.644Z</atom:updated>
            <content:encoded><![CDATA[<p>Final Phase | GSoC’19 | CCExtractor Development</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iacB40sb5bf7nU2qA3Gnmw.png" /><figcaption>Image Source: <a href="https://ccextractor.org/"><strong>https://ccextractor.org</strong></a></figcaption></figure><p>Hello!</p><p>I’m back with my latest post on Google Summer of Code! Till the second evaluation, I have successfully integrated all the features as mentioned in the proposal. I’m really grateful to my mentor <a href="https://medium.com/u/6ce7e14d73c8">Johannes Lochter</a> who very genuinely gives feedback to my work and always show a path of improvements. This post summarises all the integration and improvements accomplished after the second evaluation. I had 0 experience in ReactJS but after using it for a while, It really amazed me with it’s workflow. I had fun working with ReactJS and it really helped me to achieve what I had really conceptualized initially. Along with it, I worked upon the backend side of the project and integrated some features. Below are the features I integrated into it.</p><p><strong>1.Youtube video processing:</strong></p><p>The first step involves the preprocessing of youtube link to get the id of the video. This is achieved by a small method in JS in the frontend part. It can handle all types of format of youtube link provided to this function and outputs the video id.</p><pre><em>function</em> GetVideoID(url) {<br>url = url.split(/(vi\/|v=|\/v\/|youtu\.be\/|\/embed\/)/);<br>return url[2] !== undefined ? url[2].split(/[⁰-9a-z_\-]/i)[0]:url[0]<br>}</pre><p>After getting the videoID a POST method call is made at <strong><em>/api/ytstream/</em></strong><em> </em>which then uses youtube-dl library to download the video which is further pipelined to main video processing module in Rekognition and it finally gives the output.</p><p><strong>2.NSFW Classifier:</strong></p><p>As the project architecture is so well designed that adding a new deep learning model has become very smooth. I had mentioned in my project proposal about the integration of NSFW classifier based on <a href="https://github.com/yahoo/open_nsfw">Yahoo’s open_NSFW</a> classification.So, I used already trained TensorFlow model and integrated to TensorFlow Serving. Finally created a REST APIs to use it.</p><p><strong>3.Similar Face Search:</strong></p><p>This feature provides the functionality to search a reference face in an image containing multiple faces. The motivation for integrating this feature came from Google Photos which creates a gallery of photos having a particular face common to all the image. REST APIs has also been created for this as well.</p><p><strong>4. User Authentication:</strong></p><p>Unmerged PR no. <a href="https://github.com/pymit/Rekognition/pull/44">#44</a> contains the feature of adding user authentication. I have held it because a lot of changes have to be made in main project as well as the ReactJS frontend for APIs calls rendering. I’m still experimenting with it. I will merge it only when the PR will become suitable for the project’s agile development.</p><p><strong>5. Frontend:</strong></p><p>Working with ReactJS is a charm. I documented all the use cases of all the APIs with examples in a very concise and elegant manner. This project’s user experience no doubt can be improved a lot but yet I have given a simple, user-friendly UI.</p><p>Is it finally the endgame of this project with the end of such a cool summer? The answer is a big NO. This project has just started it’s journey. It has lots of areas which can be improved and a new feature can be integrated. I will keep contributing and adding new features to it. If you find this project really interesting and wants to contribute then you’re welcome! <a href="https://github.com/pymit/Rekognition">Here </a>is the link of the project.</p><p>Happy coding!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d9f5d5aefb0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[week 6&7 | GSoc’19 | CCExtractor Development]]></title>
            <link>https://medium.com/@amkr/week-6-7-gsoc19-ccextractor-development-8173ce62a0bf?source=rss-c30643800fb4------2</link>
            <guid isPermaLink="false">https://medium.com/p/8173ce62a0bf</guid>
            <category><![CDATA[python]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[tensorflow]]></category>
            <category><![CDATA[gsoc]]></category>
            <category><![CDATA[tensorflow-serving]]></category>
            <dc:creator><![CDATA[Amit Kumar]]></dc:creator>
            <pubDate>Sun, 14 Jul 2019 15:35:12 GMT</pubDate>
            <atom:updated>2019-07-14T15:43:54.299Z</atom:updated>
            <content:encoded><![CDATA[<p>week 6&amp;7 | GSoC’19 | CCExtractor Development</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iacB40sb5bf7nU2qA3Gnmw.png" /><figcaption>Image Source: <a href="https://ccextractor.org/"><strong>https://ccextractor.org</strong></a></figcaption></figure><p>For the past two weeks I was involved in two major tasks I worked upon</p><ul><li>Training facial expression deep learning model</li><li>Implementing TensorFlow Serving</li></ul><p>For facial expression recognition, I used fer2013 dataset and Google colab to train the model. You may find the Colab Link<a href="https://colab.research.google.com/drive/1U7Mr3Wjl3CemNlp5bQItQfm0uhahvuo1"> here</a>. I had initially planned to integrate this model into the existing Django app, But deploying models this way was a very naive approach and inefficient way to deploy deep learning models. The second choice that I had was TensorFlow Serving. TFS(TensorFlow Serving) is a flexible, high-performance serving system for machine learning models, designed for production environments. TFS allows us to seamlessly serve our machine learning models. It also provides the option to serve multiple version of the same deep learning model.</p><p>A small overview of TFS , Manager is responsible for loading, unloading, lookup and lifetime management and handle the full lifecycle of Servables, Servables are the underlying objects that clients use to perform computation (for example, a lookup or inference). Manager may wait to unload until a newer version finishes loading, based on a policy to guarantee that at least one version is loaded at all times. Below is the workflow TFS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eoMCFDmk-EIATA5o8jLfUQ.png" /><figcaption>source: <a href="https://www.tensorflow.org/tfx/serving/architecture">https://www.tensorflow.org/tfx/serving/architecture</a></figcaption></figure><p>For more information, How TFS works, You may visit the link provided in the Resources down below.</p><p>The first step is to make Docker(recommended) ready environment for the deployment of the model. Here is the<a href="https://www.tensorflow.org/tfx/serving/docker"> link </a>that you will find it helpful in making your Docker environment ready. Now ,it’s time to make the trained model ready for TFS below provided gist will help you to make your model ready for Tensorflow Serving.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a181b675d381439c2bd115b1a81ba9ec/href">https://medium.com/media/a181b675d381439c2bd115b1a81ba9ec/href</a></iframe><p>Once it’s successfully run, you may check the signature definitions of the model by running the below command in terminal:</p><pre>saved_model_cli show — dir {export_path} — all </pre><p>{export_path: is the base directory which should be same as it was defined while saving the model}.</p><p>It will show output like below, Here you will find information about the servable.</p><pre>MetaGraphDef with tag-set: ‘serve’ contains the following SignatureDefs:</pre><pre>signature_def[‘serving_default’]:<br> The given SavedModel SignatureDef contains the following input(s):<br> inputs[‘input_image’] tensor_info:<br> dtype: DT_FLOAT<br> shape: (1, 48, 48, 1)<br> name: prefix/image:0<br> The given SavedModel SignatureDef contains the following output(s):<br> outputs[‘final_output’] tensor_info:<br> dtype: DT_FLOAT<br> shape: (1, 6)<br> name: prefix/softmax:0<br> Method name is: tensorflow/serving/predict</pre><p>Now it’s time to check How our deployed model is working. Now let’s make our TFS ready for work</p><pre>docker run -it -p 8500:8500 -p 8501:8501 -v /Users/amit/Desktop/test/exportpath/:/home/ tensorflow/serving:nightly-devel</pre><ul><li>-p 8501:8501 : Publishing the container’s port 8501 (where TF Serving responds to REST API requests) to the host’s port 8501</li><li>-p 8500:8500 : Publishing the container’s port 8500 (where TF Serving responds to gRPC requests) to the host’s port 8500</li><li>-v /Users/amit/Desktop/test/exportpath/ : where the models are saved</li><li>/home/ : This directory is mounted under which the model directory will be present</li><li>tensorflow/serving:nightly-devel : Running a Docker container based on the serving image “tensorflow/serving:nightly-devel”</li></ul><p>go to root dir (using cd ..)</p><pre>tensorflow_model_server — rest_api_port=8501 — model_name=fer2013 — model_base_path=”/home/fer2013/models/”</pre><p>Now TFS is ready to listen a client request.Below is the python client to call a REST API requests .</p><pre>import json<br>data = json.dumps({“signature_name”: “serving_default”, “instances”: img.tolist()}) #img is of shape (1,48,48,1)</pre><pre>import requests<br>headers = {“content-type”: “application/json”}<br>json_response = requests.post(‘<a href="http://localhost:8501/v1/models/fer2013:predict&#39;">http://localhost:8501/v1/models/fer2013:predict&#39;</a>, data=data, headers=headers)<br>predictions = json.loads(json_response.text)[“predictions”]</pre><p>Hola! You will get the result.</p><p>Future work may include the integration of kubernetes cluster to scale as the load starts increasing on the app.</p><p>I did face some challenges while implementing the TensorFlow Serving but I hope going through official documentation and doing one or two online tutorial examples you may find it easy to work with TFS. I hope you will find this article helpful.</p><p>Thanks for reading :)</p><p><a href="https://www.linkedin.com/in/amkr/">LinkedIn</a> <a href="https://github.com/pymit">GitHub</a> <a href="https://twitter.com/amit2rockon">Twitter</a></p><p>References:</p><p><a href="https://www.tensorflow.org/tfx/serving/architecture">https://www.tensorflow.org/tfx/serving</a>/</p><p><a href="https://medium.com/tensorflow/serving-ml-quickly-with-tensorflow-serving-and-docker-7df7094aa008">https://medium.com/tensorflow/serving-ml-quickly-with-tensorflow-serving-and-docker-7df7094aa008</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8173ce62a0bf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[week 5| GSoc’19 | CCExtractor Development]]></title>
            <link>https://medium.com/@amkr/week-5-gsoc19-ccextractor-development-ff895a985d9c?source=rss-c30643800fb4------2</link>
            <guid isPermaLink="false">https://medium.com/p/ff895a985d9c</guid>
            <category><![CDATA[celery]]></category>
            <category><![CDATA[tensorflow]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[asynchronous]]></category>
            <category><![CDATA[gsoc]]></category>
            <dc:creator><![CDATA[Amit Kumar]]></dc:creator>
            <pubDate>Sun, 14 Jul 2019 15:32:34 GMT</pubDate>
            <atom:updated>2019-07-14T15:36:03.429Z</atom:updated>
            <content:encoded><![CDATA[<p>week 5| GSoc’19 | CCExtractor Development</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iacB40sb5bf7nU2qA3Gnmw.png" /><figcaption>Image Source: <a href="https://ccextractor.org/"><strong>https://ccextractor.org</strong></a></figcaption></figure><p>Concurrency, Parallelism, Threads, Processes, Async and Sync 🤔</p><figure><img alt="Plant trees , it will surely help nature to survive!" src="https://cdn-images-1.medium.com/max/730/1*X8I0CiT3O-RM1Bu4osAFug.jpeg" /><figcaption>Message: Plant trees, source: www.earth.com</figcaption></figure><p>Video processing takes huge time to process a single video which means when a user send a request to process a video, the client will wait for it’s response. But the problem arises when response time is greater than the connection time. Also you won’t like your user to be handcuffed only with the processing bar followed by failed user-client connection. So I guess it’s better to ask user to have coffee and come back after a few minutes. Let’s solve this issue while the user takes a sip of coffee. Since Django is not pre-built to work asynchronously now you got to find a solution for this. The first and foremost picture of solution that comes into mind is of Celery because it is the all time champion so far for executing tasks asynchronously. You may relate async tasks as the classical producer/consumer problem. Producer places a job in queue and Consumer checks the head of the queue for the awaiting jobs and picks the head one and execute it.</p><p>When you come around Celery you will notice a term broker, the concept of a broker is simply a queue. RabbitMQ, Redis and SQS are few examples. Since our user is very short tempered and has zero patience and almost finished his first coffee cup we can’t wait anymore to implement Celery in our Django app. Below the post, reference links are provided to get more detailed information. I followed Celery’s documentation to implement the feature for Django and selected Redis as the broker. I was very happy till when I found except for the main purpose i.e Inference part everything worked well. Celery community on irc is not so active I asked help from almost everywhere. I was unable to find the real reason behind this issue. I checkout the Celery FAQs where I found this statement</p><blockquote>Why is Task.delay/apply*/the worker just hanging?</blockquote><blockquote>Answer: There’s a bug in some AMQP clients that’ll make it hang if it’s not able to authenticate the current user, the password doesn’t match or the user doesn’t have access to the virtual host specified. Be sure to check your broker logs (for RabbitMQ that’s /var/log/rabbitmq/rabbit.log on most systems), it usually contains a message describing the reason</blockquote><p>My approach was to segment a video into n chunks and then inference parallelly with multiprocessing by leveraging the max CPU cores available.But except for the inference, every other functions call were working just fine. why is it so?</p><p>Here is the reason:</p><blockquote>Python multiprocessing cannot be used to pass a tensorflow session into multiprocessing pool because the session is not serializable and the session may be managing GPU memory and other similar states as well.</blockquote><p>But before this fact was known to me I kept on trying Celery to work. Finally this piece of command worked.</p><pre>celery -A Rekognition worker -l info — without-gossip — without-mingle — without-heartbeat -O fair — pool=solo</pre><p>The most important argument here is <em>— pool=solo ,</em> Now let me explain briefly about Celery Execution Pool.</p><p>Celery spawns child processes to process any task but not by itself. These child processes (or threads) are also known as the execution pool. Execution pools are of four types supported by Celery, In which I will be discussing <em>prefork </em>and <em>solo</em> especially. The <em>prefork</em> pool implementation is based on Python’s multiprocessing package. This is where my tensorflow model was hanging to process. <em>Prefork</em> creates child processes to process the tasks. while ’solo’ pool is neither threaded nor process-based. It runs inside the worker process. It runs inline which make it faster. But the problem is not still solved since it executes the tasks sequentially. But one thing that can be done to utilize the fact is to create multiple workers with <em>solo</em> pool. With experiment, I found this method reduces the time of processing when compared with a single pool as well as passing a whole video instead of <em>n</em> chunks. Multiple <em>solo</em> pools come with high memory usage issue. So this part is still in an experimental part of the project.</p><p>Then one thing struck to my head i.e. How the tornado web framework’s asynchronous system is designed?</p><p>What I found that almost all asynchronous python frameworks use python’s standard library: asyncio underneath. So the 😃wow moment came now. But wait before I could jump into it let me tell you something more about async in python, the concept of asynchronous programming was introduced into python 3.4. It was introduced very late due to a fundamental python concept — Global Interpreter Lock (GIL) which blocked it from being asynchronous. In simple words in simple words, GIL a mutex (or a lock) that allows only one thread to hold the control of the Python interpreter.</p><p>“The event loop is the core of every asyncio application. Event loops run asynchronous tasks and callbacks, perform network IO operations, and run subprocesses.”</p><p>You may can add tasks to this loop and it executes them on a FIFO fashion</p><p>How to implement this event loop?</p><pre>loop = asyncio.get_event_loop()<br>loop.run_until_complete(tasks())<br>#To define a async function :<br>async def foo():<br>   pass</pre><p>So I implemented one thread for each async method and finally solved a small yet major issue in asynchronous execution of the video processing part. Now user is not supposed to be handcuffed . He/She can put the video on the process and leave the desk to have another cup of coffee or add another video on the process.</p><p>Thank you for reading :)</p><p><a href="https://www.linkedin.com/in/amkr/">LinkedIn</a> <a href="https://github.com/pymit">GitHub</a> <a href="https://twitter.com/amit2rockon">Twitter</a></p><p><strong>References:</strong></p><ul><li><a href="http://www.celeryproject.org/">Homepage | Celery: Distributed Task Queue</a></li><li><a href="https://www.distributedpython.com/">Celery how-tos and tutorials</a></li><li><a href="https://www.tornadoweb.org/en/stable/guide/async.html">Asynchronous and non-Blocking I/O - Tornado 6.3.2 documentation</a></li></ul><p><a href="https://realpython.com/">https://realpython.com</a>/</p><p><a href="https://docs.python.org/3/library/asyncio-eventloop.html">https://docs.python.org/3/library</a>/</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ff895a985d9c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[week 4| GSoc’19 | CCExtractor Development]]></title>
            <link>https://medium.com/@amkr/week-4-gsoc19-ccextractor-development-df890ffa2b46?source=rss-c30643800fb4------2</link>
            <guid isPermaLink="false">https://medium.com/p/df890ffa2b46</guid>
            <category><![CDATA[reactjs]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[gsoc]]></category>
            <category><![CDATA[ccextractor-development]]></category>
            <category><![CDATA[week-4]]></category>
            <dc:creator><![CDATA[Amit Kumar]]></dc:creator>
            <pubDate>Sun, 23 Jun 2019 17:52:14 GMT</pubDate>
            <atom:updated>2019-07-14T15:44:31.347Z</atom:updated>
            <content:encoded><![CDATA[<p>week 4 | GSoC’19 | CCExtractor Development</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iacB40sb5bf7nU2qA3Gnmw.png" /><figcaption>Image Source: <a href="https://ccextractor.org/"><strong>https://ccextractor.org</strong></a></figcaption></figure><p>Finally towards the final week of the first evaluation. Till now, It has been a great journey of learning, experimenting and implementing the stuff. Up to now I have been very much strict with the GSoC proposal’s timeline and successfully implemented all the features.</p><p>While in search of tools for building the UI for the project I forgot to mention about ReactJS in the proposal. I wanted to keep the backend side and frontend side apart as well as elegant. So finally I started working with ReactJS this week. This tool was new to me back a few days ago but now I’m really amazed by it’s simplicity in writing code and it’s elegant output. I’m using material design along with bootstrap. This week a small yet significant part of the UI has been completed. I created a new repo for this UI part . You can find the link to the GitHub repo <a href="https://github.com/pymit/RekoUI">here</a>. Let me show you some of the current view of the UI.</p><p>To add a new face embedding.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*_RpQxQ8OhdqaC4dgIkoZEQ.gif" /></figure><p>To recognize faces in an Image</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nAVaY0NSDDevOQP20BHs8g.gif" /></figure><p>Currently, only two features in UI are added, I will complete the remaining in coming days.</p><p>While in backend side, I worked on Django models particularly this week to enhance the API call results and it’s usage.</p><p>for the next evaluation, I’m having a huge milestone to cover. I’m really very much excited about the coming features. Stay tuned :)</p><p>Profile links <a href="https://www.linkedin.com/in/amkr/">LinkedIn</a> <a href="https://github.com/pymit">GitHub</a> <a href="https://twitter.com/amit2rockon">Twitter</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df890ffa2b46" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[week 3 | GSoc’19 | CCExtractor Development]]></title>
            <link>https://medium.com/@amkr/week-3-gsoc19-ccextractor-development-e6be1d1e1fb4?source=rss-c30643800fb4------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6be1d1e1fb4</guid>
            <category><![CDATA[week-3]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[scikit-video]]></category>
            <category><![CDATA[ccextractor-development]]></category>
            <category><![CDATA[gsoc]]></category>
            <dc:creator><![CDATA[Amit Kumar]]></dc:creator>
            <pubDate>Sun, 23 Jun 2019 16:03:01 GMT</pubDate>
            <atom:updated>2019-07-14T15:44:46.386Z</atom:updated>
            <content:encoded><![CDATA[<p>week 3 | GSoC’19 | CCExtractor Development</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iacB40sb5bf7nU2qA3Gnmw.png" /><figcaption>Image Source: <a href="https://ccextractor.org/"><strong>https://ccextractor.org</strong></a></figcaption></figure><p>This week I started working on UI side, But soon I realized that the core part of the project needs lots of improvement and UI part can be done later on may be in between last few weeks or better after GSoC period. Therefore I particularly started working on this core part. This week I achieved a great milestone in especially in video processing part by introducing a simple local cache memory for the embeddings. You can check the problem I faced and the solution mentioned on GitHub <a href="https://github.com/pymit/Rekognition/projects/3">kanban board</a> . Here local cache means, I maintained a local dictionary to the function in which all the faces and embeddings are kept. First, it checks whether the embeddings of the faces in current frames were present in the previous frames or not. If there is a hit then it moves to identify the next face else It looks globally for the face embeddings and on hit, current face embedding is added to the local cache. This simple solution gave a huge boost in performance.</p><p>Let me show you result on this youtube <a href="https://www.youtube.com/watch?v=-VcCzKjXs-8">video</a>,</p><p>Video metadata:</p><pre>fps : 29.97002997002997 <br>total_no_of_frames : 2188.0 <br>duration: 73.006267 seconds<br>frame_hops : 2 <br>min_frame_dur gap in ms : 300.3000013711151</pre><p>output:</p><pre>Time taken by<strong> previous method </strong>: 782.4210019111633 seconds</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JLz9aTBnd500K0ebO4C3wA.png" /><figcaption>output without cache</figcaption></figure><p>Output</p><pre>Time taken by <strong>new method</strong> : 656.1480021476746 seconds — </pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*scglo92i6JVIBtOly5eZog.png" /></figure><p>This is video has two main characters, 1) Elon Musk, 2) Unknown.</p><p>You can clearly see the difference in output accuracy of detected faces. The current database had 1295 embeddings.</p><p>You can find the patch for this feature in <a href="https://github.com/pymit/Rekognition/pull/11">#PR11</a></p><p>Concurrently I also worked on APIs part and also improved the code quality for the APIs service.</p><p>If you really enjoyed this post and also following my earlier blogs then I’m sure I’m pretty lucky. If this project intrudes you and want to contribute then join the CCExtractor channel and have a discussion :) and stay tuned 😎.</p><p>Profile links <a href="https://www.linkedin.com/in/amkr/">LinkedIn</a> <a href="https://github.com/pymit">GitHub</a> <a href="https://twitter.com/amit2rockon">Twitter</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6be1d1e1fb4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[week 2| GSoc’19 | CCExtractor Development]]></title>
            <link>https://medium.com/@amkr/week-2-gsoc19-ccextractor-development-e4ffb6d54376?source=rss-c30643800fb4------2</link>
            <guid isPermaLink="false">https://medium.com/p/e4ffb6d54376</guid>
            <category><![CDATA[scikit-video]]></category>
            <category><![CDATA[ccextractor-development]]></category>
            <category><![CDATA[face-recognition]]></category>
            <category><![CDATA[week-2]]></category>
            <category><![CDATA[gsoc]]></category>
            <dc:creator><![CDATA[Amit Kumar]]></dc:creator>
            <pubDate>Sat, 15 Jun 2019 17:49:48 GMT</pubDate>
            <atom:updated>2019-07-14T15:45:07.313Z</atom:updated>
            <content:encoded><![CDATA[<p>week 2 | GSoC’19 | CCExtractor Development</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iacB40sb5bf7nU2qA3Gnmw.png" /><figcaption>Image Source: <a href="https://ccextractor.org/"><strong>https://ccextractor.org</strong></a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*4mSGUkd_G2dFUO1GSvzD4A.png" /><figcaption>Image Credit: DigitalOcean</figcaption></figure><p>Continuing with the last blog, This week my most of the time was put on making a clean code for the RESTful APIs. I restructured the project in the way that in future if new core library is supposed to be added then it can be easily integrated. In PR #<a href="https://github.com/pymit/Rekognition/pull/6">5</a> Firstly I created a new Django app to keep core end APIs of the project. This time I was very much strict to DRY principle, I restructured the project’s module wherever the repetition of snippets was present.</p><p>Concurrently I was also working on the video processing part. I will give a small glimpse over its algorithm. So whenever a video is given as input, first and foremost the metadata of the video is parsed. The main metadata are frame per second (fps in short), total no. of frames, duration of the input video. To get the timestamp of each frame, frame no is divided by fps. I also chose an option to give the extent of precision a user wants the result in output. Here precision means no. of frames a user wants to process in second (like if video is of 30fps and user wants to process 24fps). But this option is currently not in direct control of user but later I’ll make this option available. Each frame is processed and a dictionary is maintained which keeps the face_id as the key and timestamps array as it’s value. Then after processing all the frames, this dictionary is sent for further processing. Now the coalescence of timestamps here takes place. suppose two timestamps are very much closer then they are chained. The coalescence of timestamps threshold is automatically determined based on the selection of no. of frames to be processed.</p><p>But I was not satisfied with the current approach as it is very time-consuming. I recently came across scikit-video which uses ffmpeg behind the scene.</p><p>Here is the benchmark of scikit-video and opencv python .<br>to load a single frame</p><pre>time taken by scikit-video : 0.005018000000000189<br>time taken by cv2 : 0.0228900000000003</pre><p>time taken to load 5637 frames sequentially</p><pre>time taken by scikit-video 8.149045999999998<br>time taken by cv2 : 55.439571</pre><p>clearly, it was an indicator of changing the hammer right now.I also found that the current method (scikit-video)proved to be more robust.</p><p>Currently,Now I’m using <em>vreader() </em>method in scikit-video which gives a generator while<em> vread()</em> can be used to load the whole video in one go and outputs numpy array, which I find more useful. I can still optimize at this point also since I’m not actually reducing the frame size of the input. Not only this In future I’m having a more robust way to decrease the time taken and also the increase the accuracy . Want to know the method? stay tuned for coming blogs. For the latest update, I also actively update the GitHub kanban board.</p><p>Let’s explore about face embeddings little bit. So, what does a face embedding is exactly? Each face is compactly represented by a 128-dimensional byte vector. Now why it’s 128 why not 256 or 64? 128 is selected because according to[FaceNet] paper they performed experiments with these dimensions and below is the result.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/429/1*_vcOQpKbqvGdIAFc0Yo-fg.png" /><figcaption>Source:FaceNet (<a href="https://arxiv.org/abs/1503.03832">https://arxiv.org/abs/1503.03832</a>)</figcaption></figure><p>The differences in the performance reported above are statistically insignificant. Therefore they selected 128. However, it is possible that higher dimension requires more training to achieve the same accuracy. What kind of values is present in the 128D embedding array? It contains floating point values [0.03861399, -0.04976186, … ,0.09530648 -0.05199577].</p><p>Let’s check how the numbers actually look like.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/924/1*wp7rR2MAfmXvcG7iJnaUxg.png" /><figcaption>matplotlib</figcaption></figure><p>Above each image is 8x16 pixels image, therefore, have total of 128dimensions each holding the value of one specific pixel. You can somewhat tell the difference between FaceID0 and FaceID1 . Below is the representation of 128D{high dimension} into 2D dimension using the result of PCA(Principle Component Analysis) which is actually used to reduce the dimensionality of a dataset. PCA uses eigenvalues and eigenvectors of the data-matrix. These eigenvectors of the covariance matrix have the property that they point along the major directions of variation in the data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/955/1*VNBukWmkRWl5e0N8G7YF2Q.png" /><figcaption>using PCA</figcaption></figure><p>You can observe how similar face embeddings are being closer to each other while being apart from different kinds of faces embedding. The difference is huge because above is a representation of of a women’s and a men’s face embeddings.</p><p>Let’s explore by using t-SNE(t-Distributed Stochastic Neighbouring Entities), 3D representation of the same embeddings. t-SNE uses a probablistic approach instead of a mathematical technique.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/914/1*vZu2x8opOTx7hcprUpDijA.png" /><figcaption>using t-SNE</figcaption></figure><p>All the above outputs are a result of scikit-learn, seaborn and matplotlib and numpy. In coming blogs I write more insightful blogs so, stay tuned for coming blogs!</p><p>Profile links <a href="https://www.linkedin.com/in/amkr/">LinkedIn</a> <a href="https://github.com/pymit">GitHub</a> <a href="https://twitter.com/amit2rockon">Twitter</a></p><p>References:</p><p><a href="http://www.scikit-video.org/">http://www.scikit-video.org/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e4ffb6d54376" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[week 1 | GSoc’19 | CCExtractor Development]]></title>
            <link>https://medium.com/@amkr/week-1-gsoc19-ccextractor-development-eab8c4c1fda8?source=rss-c30643800fb4------2</link>
            <guid isPermaLink="false">https://medium.com/p/eab8c4c1fda8</guid>
            <category><![CDATA[gsoc]]></category>
            <category><![CDATA[ccextractor-development]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[week-1]]></category>
            <dc:creator><![CDATA[Amit Kumar]]></dc:creator>
            <pubDate>Mon, 03 Jun 2019 01:19:41 GMT</pubDate>
            <atom:updated>2019-07-14T15:45:23.807Z</atom:updated>
            <content:encoded><![CDATA[<p>week 1 | GSoC’19 | CCExtractor Development</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iacB40sb5bf7nU2qA3Gnmw.png" /><figcaption>Image Source: <a href="https://ccextractor.org/"><strong>https://ccextractor.org</strong></a></figcaption></figure><p>Hello guys, I’m here with my second blog on reaching the first-week milestone of the GSoC period. Firmly gripping the bow and holding the arrow in the right direction will certainly increase the probability of getting the arrow at the right aim.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*7A2XxFePOob0qh93zMtGSA.jpeg" /><figcaption><strong>Photo Credit:</strong> <a href="http://huntingactivity.com/">huntingactivity.com</a></figcaption></figure><p>I’m using this analogy to create a fine relation between project, the right tech tools, and project architecture design respectively which will help to accomplish the main goal of the project at the end.</p><p>My first week of the GSoC period was a great milestone for me not because I only baked some code but also took my time to give a glance at various current tech stacks available which can make the project more efficient. This exploring of tech stack was the main part of my GSoC Community Bounding period. Of course, There is no doubt that CCExtractor Development is a great community. This time they have taken a great initiative of distributing any technical book on demand to the selected students. What could be more blissful way better than this to start summer coding 😀. Wait, did I forget to introduce you to my project? err…😬 .</p><p>Okay, Let’s first start with the introduction of the project <strong><em>Poor Man’s Rekognition.</em></strong> This project aims at providing a free alternative to Amazon’s Rekognition services. The main aim is to provide simple and easy to use API that can quickly analyze any image. This time this project has been particularly focused on Face recognition. But I have planned to extend it furthermore ,I’ll will update this in coming weeks. You can also find a short description of the project at the official CCExtractor’s Website <a href="https://www.ccextractor.org/public:gsoc:poormanrekognition">link</a>. To discuss it furthermore you can join the slack channel of CCExtractor Development by requesting an invitation using <a href="https://ccextractor.org/public:general:support">link</a>. Our mentor for this project is ​<strong>Johannes Von Lochter.</strong> He is well known for his research paper publications in International Conference on Machine Learning and Applications (ICMLA) and other great conferences as well :).</p><p>Technical insight: This week so far, I have done setting up the project locally and GitHub repo <a href="https://github.com/pymit/Rekognition">link </a>. I’m using GitHub’s Kanboard to organize and manage the milestones of the project (<a href="https://github.com/pymit/Rekognition/projects">link</a>). Here’s a very basic sketch of the project structure,</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/931/1*N4HkytJ5KKuUBcLtglVa1Q.png" /></figure><p>It has lots of integration coming in future weeks (: excited) and will update it on coming weeks or you can also keep eye on the kanban board. After setting up the environment, I also integrated some of the already implemented features of proof of concept of the PMR (Poor Man’s Rekognition). This week I worked on extending the support for png image format so that tensor input could easily fit the network architecture. I also worked on multi-face detection and recognition in a single frame merged PR#5 (Pull Request ) <a href="https://github.com/pymit/Rekognition/pull/5">link</a> . Currently, the project has a long way to be worked upon.</p><p>So, To further push the limits of enthusiasm for the project. I have planned to integrate the ReactJS for frontend. <em>Week2 schedule</em>: I will be focused on designing and creating the end RESTful APIs for the current features implemented using django-rest-framework. Concurrently, I’m also working on the video feature part and will update work around this in the coming blogs.</p><p>If you find this project intriguing then you can also start contributing. Stay tuned!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eab8c4c1fda8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GSoC’19 with CCExtractor Development]]></title>
            <link>https://medium.com/@amkr/gsoc19-with-ccextractor-development-8a69a8ae78fc?source=rss-c30643800fb4------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a69a8ae78fc</guid>
            <category><![CDATA[blog]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[gsoc19]]></category>
            <category><![CDATA[gsoc]]></category>
            <dc:creator><![CDATA[Amit Kumar]]></dc:creator>
            <pubDate>Fri, 10 May 2019 02:41:48 GMT</pubDate>
            <atom:updated>2019-07-22T02:37:19.596Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*qPJ1UqlzHaJ0bivakaYYAg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/224/1*NDY8xWfejwVOt-HnWerUWg.png" /><figcaption>image source: Internet</figcaption></figure><p>Hi folks</p><p>I’m Amit Kumar, people usually call me opensource evangelist but officially I’m an undergraduate at Indian Institute of Information Technology, Kalyani major in Computer Science and Engineering. I’m really excited about, this summer that I’m a member of the prestigious Google Summer of Code ’19 program. My proposal for GSoC’19 under CCExtractor Development has been accepted and I’ll be working to make open source version of Amazon’s Rekognition APIs services.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/259/1*hoxPwQFnBur0qSK9mGdOfQ.png" /><figcaption>image source: Internet</figcaption></figure><p>My love for opensource ❤ is since a long time and here on Medium platform, I will be sharing my all technical learnings, approaches, and experiences gained throughout this cool summer.</p><p>A glimpse of past attempt in GSoC : <em>mistakes to learn from</em></p><p>So, I came to know about this prestigious program sponsored by Google in late 3rd semester of my academic career. I started figuring out more about GSoC in the starting days of January 2018. I was very much interested in projects which included Deep learning / Python particularly. I searched for some of the previous project&#39;s archive available on GSoC official website to start contributing. I found some organizations which had projects inclined towards my interest and started going through the project’s code base.</p><blockquote>Don’t be panicked at first glance of the project’s code base. Start from fixing firstcomer bug or raise issue if you find any bug and give PR for that as well if you can fix it.</blockquote><p>if you find any bug and finding it difficult to get started with it. Google about it, collect more information about the bug, visit StackOverflow, Discuss with project maintainer or mentor. Avoid asking very general question to the project mentor. While asking doubt t<em>ry to be as much as specific and precise about the bug. </em>Be familiar with at least basic use of git, you may find <a href="https://git-scm.com/docs">this</a> link useful.<em> </em>You may really find a great no. of online resources around these topics.</p><p>While selecting projects, I came across Mozilla’s autowebcompat project. This project was a part of GSoC’18. I was very much excited about the project. I started discussing about the project with the mentor. I started solving the issues. With no time other contributors also joined and I was becoming like a more competitor than a contributor.</p><blockquote>OpenSource is all about constructive collaboration of all others not like other competition. The better understanding and more meaningful contributions you have into the project the higher is the chances that you will be selected for it.</blockquote><p>and finally, in 2018, it turned out to be an unsuccessful attempt to GSoC’18. Again this time 2019 , I was more confident about myself. I had more experience in tech skill sets I was expecting to work on. I again started searching for projects and came across a new project <a href="https://www.ccextractor.org/public:gsoc:poormanrekognition">Poor Man’s Rekognition</a> under CCExtractor Development. I submitted my proof of concept for the project. Yeah, This time I made it. I’m really very much thankful to <a href="https://medium.com/u/5ef5954afb57">Carlos Fernandez Sanz</a> who gave me this opportunity and a few of my close friends who have always seen a +ve side of mine and boost confidence. I’m really very much excited for this summer to work upon this project.</p><p>You may find the GitHub repo link for the project <a href="https://github.com/pymit/Rekognition">here</a> .</p><p>Stay tuned and you may connect with me on <a href="https://www.linkedin.com/in/amkr/">LinkedIn</a> and <a href="https://twitter.com/amit2rockon">Twitter</a> :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a69a8ae78fc" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>