<?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 Michael on Medium]]></title>
        <description><![CDATA[Stories by Michael on Medium]]></description>
        <link>https://medium.com/@michaeldnguyen?source=rss-dacb6312243e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*bw25kULdCE3i_nJ9fpP60A.jpeg</url>
            <title>Stories by Michael on Medium</title>
            <link>https://medium.com/@michaeldnguyen?source=rss-dacb6312243e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 17:54:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@michaeldnguyen/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[6 QA Tactics for Data Annotation Jobs]]></title>
            <link>https://medium.com/datatorch/6-qa-tactics-for-data-annotation-jobs-8a17b83a46e6?source=rss-dacb6312243e------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a17b83a46e6</guid>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[data-annotation-tools]]></category>
            <category><![CDATA[deep-learning]]></category>
            <category><![CDATA[computer-vision]]></category>
            <dc:creator><![CDATA[Michael]]></dc:creator>
            <pubDate>Tue, 02 Mar 2021 04:39:43 GMT</pubDate>
            <atom:updated>2021-03-02T16:10:49.034Z</atom:updated>
            <content:encoded><![CDATA[<h3>6 Tactics to Maximize the Quality of your Data Annotation</h3><h4>Learn techniques to make sure your data annotation tasks produce quality results</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mwOX3Kfvx1sabVN6-jfIKg.png" /><figcaption>Annotating MNIST in DataTorch. If it were always this easy, you wouldn’t be reading this article.</figcaption></figure><h3>1. Provide Example Sets</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dujhu1RLkDPw_NcjKDqRxg.png" /></figure><p>Also known as “golden”, “benchmark”, or “ground-truth” datasets, this is the most straightforward quality assurance technique you can employ. By presenting your annotators with example datasets containing perfectly annotated instances of each class you wish to label, you create a useful training tool as well as a baseline that enables you to calculate agreement metrics to evaluate each annotator’s accuracy. Seeing just a few examples can intuitively teach annotators each class’ defining characteristics. Including edge cases will provide clarity for them in situations where the label might be uncertain.</p><p>If you intend to calculate accuracy metrics with these example datasets, the composition of the classes within the dataset will be important; each class should either be represented equally, or have the same distribution as the data to be annotated.</p><h3>2. Calculate Normalized Agreement Metrics from Example Sets</h3><p>Once you have a good example dataset, you can use it to calculate metrics to determine a particular annotator’s performance.</p><p>The simplest accuracy metric you can calculate is to simply measure the proportion of annotations which agree with the example dataset. However, this value is typically adjusted to take into account the effect of randomly guessing. The normalization formula is as follows:</p><p><strong>(Raw Accuracy - Probability of Guessing Correctly) / (1 - Probability of Guessing Correctly)</strong></p><p>The “Probability of Guessing Correctly” can vary depending on what you want your normalization metric to be. For example, in a hypothetical task where the annotator has to mark whether people are left-handed or right-handed from a photo of people writing with their dominant hand, you could use 0.5 if you wanted your normalization metric to be a totally random guess, or 0.9 if you wanted the metric to be guessing the most common class — that is, guessing right-handedness every time (which results in a value of 0.9 because roughly 90% of people are right-handed). You could also consider using the frequency of the class as it occurs in the dataset.</p><p>It is also important to understand how to interpret these agreement statistics: The value ranges between -1 and 1. A value of 0 indicates that agreement is equivalent to random chance, while a value of 1 indicates perfect agreement. A value of -1 would indicate perfect disagreement. Any negative values indicate that the agreement is lower than random chance, and this usually indicates the annotator has a fundamental misunderstanding of the annotation task.</p><h3>3. Random Sampling QA</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GAyzSpBqNHq3B_0s76-wFg.png" /></figure><p>Once your data is annotated, you can then randomly sample subsets of your dataset and re-inspect it for accuracy, allowing you to gauge the general quality of your data. The amount of sampling you will want to employ depends on your needs and bandwidth, but this technique can go much deeper than simply analyzing the quality of your entire dataset.</p><p>For example, randomly sampling the same number of data points from two different annotators allows you to compare their performance. You can also randomly sample different classes to determine which examples are harder to annotate, or sample subsets of data that were collected in different manners, to determine if there was an effect on your data quality.</p><p>Annotation pipeline design is an often overlooked yet vital part of the data annotation process, as the composition of your pipeline can significantly impact the cost and quality of your dataset. Incorporating random sampling into your pipeline will give you a foundation of quality control that does not require the upfront work that providing example datasets will, but it will increase the time and effort needed to complete the annotation task.</p><h3>4. Perform Multiple Passthroughs</h3><p>Consider having each image (or file) annotated more than once by separate annotators. This may not be necessary for simple tasks which require minimal training. However, as the complexity of the task increases, the effectiveness of having multiple passthroughs will increase as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/518/1*NjgEHyOVpD02mvw1BpfNMA.jpeg" /></figure><p>Automated identification of diabetic retinopathy from images is a prototypical example of deep learning applied to medicine, and a perfect instance of where multiple passthroughs are necessary for complex annotations: <a href="https://pubmed.ncbi.nlm.nih.gov/8317359/">for trained doctors grading the severity of diabetic retinopathy from photographs</a>, the intra-rater agreement was only around 60% to 70% — with no correlation between agreement and the amount of experience the ophthalmologists had!</p><p>In cases where it is impractical to annotate each file multiple times, you can alternatively perform multiple passthroughs on a small portion of the original data, which will give you an indication of the overall health of the dataset. Some data annotation platforms, such as <a href="https://datatorch.io/">DataTorch</a>, actually have the ability to set the proportion of the dataset you wish to have repeated, and will distribute the work amongst your annotators automatically.</p><h3>5. Calculate Inter-Rater Agreement Metrics from Multiple Passthroughs</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/613/1*18GgdiFqYZZWlW4uc9rDaw.png" /></figure><p>Once you have done multiple passthroughs, you can to measure inter-rater agreeability, which quantifies “to what degree do my annotators agree with each other”.</p><p>This metric is applied to qualitative annotations that are mutually exclusive (for example, when tagging an entire image with metadata, or having multiple grades within a single label) and can be calculated using several different formulas, such as <strong>Cohen’s Kappa</strong> (for two annotators), <strong>Fleiss’ Kappa </strong>(for more than two annotators), and <strong>Krippendorff’s alpha </strong>(refined multi-annotator agreement metric)<strong>.</strong></p><p>We won’t go into the details of calculating these metrics, but there are plenty of resources online and in statistical literature. The formulas are very similar to the ones we used above to calculate agreement with our example datasets, and can be interpreted in a similar way. Generally speaking, a value above 0.8 for multi-annotator agreement metrics indicates high agreement and a healthy dataset for model training.</p><h3>6. Mark Edge Cases for Review</h3><p>When setting up your data annotation pipeline, there are various architectures you can implement involving any sequence or combination of in-house annotation teams, crowdsourced/outsourced annotations, trained experts, or automated annotations.</p><p>One issue with employing trained experts instead of crowdsourced/outsourced annotators is the increased cost and time burden associated with getting expert annotators. One way to circumvent this cost while also increasing the quality of your dataset is to design your pipeline in a way that outsourced annotators perform the initial pass of your dataset, and then mark edge cases for further inspection by an expert.</p><p>Determination of an “edge case” can be done either by thresholding the inter-rater metrics listed above, or flagging by individual annotators. Files marked as edge cases can then either be sent to expert annotators for final say, or alternatively pushed into a queue for multiple passthroughs for more rigorous inspection.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a17b83a46e6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/datatorch/6-qa-tactics-for-data-annotation-jobs-8a17b83a46e6">6 QA Tactics for Data Annotation Jobs</a> was originally published in <a href="https://medium.com/datatorch">DataTorch</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Create a Custom COCO Dataset from Scratch]]></title>
            <link>https://medium.com/datatorch/how-to-create-a-custom-coco-dataset-from-scratch-7cd28f0a2c88?source=rss-dacb6312243e------2</link>
            <guid isPermaLink="false">https://medium.com/p/7cd28f0a2c88</guid>
            <category><![CDATA[annotation-tools]]></category>
            <category><![CDATA[dataset]]></category>
            <category><![CDATA[coco]]></category>
            <category><![CDATA[computer-vision]]></category>
            <category><![CDATA[tutorial]]></category>
            <dc:creator><![CDATA[Michael]]></dc:creator>
            <pubDate>Wed, 20 Jan 2021 03:25:02 GMT</pubDate>
            <atom:updated>2021-01-22T17:03:29.488Z</atom:updated>
            <content:encoded><![CDATA[<h4>In this tutorial, you will learn how to collaboratively create a custom COCO dataset, starting with ideation.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aJFEyNNlRRGXx8i51xU9jw.jpeg" /><figcaption>Our Mission: Create a COCO dataset for Lucky Charms detection and classification.</figcaption></figure><p>Sometimes, you just want to use neural nets to build something cool. But one of the biggest barriers to entry for deep learning projects is the lack of relevant datasets to train your models on.</p><p>Building a custom dataset for computer vision isn’t actually that difficult, with the right tools. And if you have collaborators helping you, it can be downright easy.</p><p>That’s why, after stepping on the 1000th piece of Lucky Charms breakfast cereal left on the ground by my baby nephew, I had the idea to create a dataset for training models to automatically classify and detect these pieces of cereal.</p><p>This article is a step-by-step guide to building a COCO dataset from scratch with two collaborators (although you can do this on your own as well), using my journey in creating the Lucky Charms dataset with my little brother and sister helping me as an example.</p><h3>Tools</h3><ul><li>Team of 3 people (optional)</li><li>DataTorch</li><li>iPhone X</li></ul><p>We used a free tool called <a href="https://datatorch.io/">DataTorch</a> as our primary dataset creation tool. It makes it extremely easy to consolidate data and distribute annotation tasks, and it’s free to use collaboratively for teams of up to 3 people. Other than that, we will just be using our iPhone cameras to gather data.</p><h3><strong>Step 1: Plan Dataset</strong></h3><p>Sit down and really think about what you want your dataset to look like. What exactly do you want your annotation classes to be? You want numerous high-quality representations of each class (in our case, the 12 different types of cereal bits). Each class should be represented in a roughly equal distribution, so the model can train in an unbiased manner.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nnTb6X8LWf1l3d-d2ZOD4w.jpeg" /><figcaption>Our dataset had 12 classes total: 4 cereal classes (fish, cross, tree, bell) and 8 marshmallow classes (moon, unicorn, rainbow, balloon, heart, star, horseshoe, clover).</figcaption></figure><p>The amount of variation you want in regards to properties such as background, distance, and noise depends on your expected use case for the data; generally speaking, the more flexible you want your computer vision algorithm to be, the more variation you need to include in the training dataset. If you know the algorithm will be deployed in a tightly controlled environment, then simple examples that closely match that environment might work without the need for extra data.</p><p>For the Lucky Charms dataset, we decided it would be easiest to have several instances of cereal per photo (instead of just one piece per image), so each photo would just be a handful of Lucky Charms, around 20 or so, scattered on the ground. Since our house had both carpet and hardwood floors, we also wanted our dataset to include these backgrounds, and for each photo to be taken consistently at a distance of around 1 foot.</p><h3><strong>Step 2: Setup Project</strong></h3><p>Before taking pictures, you will need to create a project on <a href="https://datatorch.io/">DataTorch</a> and add your collaborators, which will give you a place to consolidate all of your images.</p><p>Create one account for each of your team members on DataTorch. Make sure they remember their usernames!</p><p>In one of the accounts, create a new project. In DataTorch, projects are like folders that encapsulate datasets, data sources, and annotations for a machine learning model. Follow the project creation steps and click “Create”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ef2oWku0Mh67Aod1i6fd0A.png" /></figure><p>Once this is done, you should be taken to the project summary page. Now you need to link your collaborators to the project, so they can also contribute data to the dataset.</p><p>To do this, click the “Members” tab in the bottom left corner of the sidebar, type in the usernames of your partners under the “Invite Members” section, and click the “add” icon on the right side to confirm these choices. Set the permission to Maintainer, then click “Add”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E6QDWeERrn4JORGj8pgbRw.png" /><figcaption>This is where you invite members to collaborate on your project.</figcaption></figure><p>Now, all of your collaborators will see your Project in their list as soon as they log in, and will be able to contribute data.</p><h3>Step 2.5: Define Annotation Classes</h3><p>While you are setting your project up, you can also define your annotation classes here while you are clicking around the project. This doesn’t necessarily have to be done right now; it can wait until you are actually annotating the data. However, defining the classes as part of your planning process is good practice and can also put you in the right mindset when doing the data collection step.</p><p>In DataTorch, annotation classes are called labels, and can be organized hierarchically.</p><p>In the sidebar, click “Labels”, then click the green plus sign to create a new label. Name your label whatever you want, don’t worry about the Custom ID section, set the color and parent if you want, and click “Create”. Do this for each of your classes until you have labels for all of them.</p><p>Click the “Hierarchy” tab to see a cool tree view of how your labels are organized. Here is what ours looks like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OJTfC0o8nif13w5-ZXozOg.png" /><figcaption>The Lucky Charms classification tree</figcaption></figure><p>To get a teaser of where we are going next, click Files (on the sidebar) &gt; DataTorch Storage &gt; Upload. This is where everyone will put their files for the dataset!</p><h3><strong>Step 3: Gather Data</strong></h3><p>Now you will need to actually gather the data for the dataset. If you had sound planning in Step 1, then this is just a matter of dividing up the work equally among your team members and executing.</p><p>In our case, we all used iPhone X cameras as our hardware and split the work among the three of us by assigning each person one of the three types of backgrounds we wanted in our dataset: one person would take pictures on carpets, one person would take pictures on hard floors, and one person would take pictures on anything else (tables, books, boxes, etc). This way, we would get a good mix of backgrounds that properly represented the floors of our house.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mn-QyaXeYUv8G7E9xGRCyQ.jpeg" /></figure><p>With each person assigned to take 50 images, and each image having at least 20 pieces of cereal, we would end up with at least 1000 instances of cereal per person, or 3000 total in the dataset, before augmentation. Not bad!</p><p>We also made sure that each picture used a different handful of cereal that was randomly selected from the cereal box population, but this ended up being somewhat of a mistake. Although this random sampling led to a distribution of classes similar to that of the actual population, <em>the distribution of classes in the population was not equal. </em>This goes against the principle of a good dataset having a roughly equal distribution of classes.</p><p>Simply put, we wanted our dataset to have an equal amount of each type of cereal. But a box of Lucky Charms has a lot more grains than marshmallows. Since we just took a handful of Lucky Charms for each picture, we ended up having a lot more grains than marshmallows in our dataset.</p><p>Lesson learned. Hopefully, since the marshmallows look so different from the grains, this won’t affect training so much. We can always add more data later.</p><h3>Step 4: Upload Files</h3><p>DataTorch actually provides each new project with free Azure Blob Storage in the cloud and automatically hooks it up without any prior setup. Every user gets up to 10 GB for free, so we will be using this to store our data.</p><p>When each team member is done gathering data, have them log into DataTorch and upload their images to the project’s provided DataTorch cloud storage:</p><p>Click Files (on the sidebar) &gt; DataTorch Storage &gt; Upload. Then, have each team member drag their images (as JPGs or PNGs) into the storage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L0TGolQy0J7DJi0ejrAUKg.png" /></figure><p>If you go to the “Explorer” tab next to “Upload” in the DataTorch Storage overview, you should see all of the files that have been uploaded.</p><h3>Step 5: Organize Files into Datasets</h3><p>Now that your files are in DataTorch, you need to organize it into a dataset.</p><p>Wait a second, you might be thinking…isn’t it already a dataset?</p><p>Not exactly. In DataTorch, dataset structure is organized separately from file storage. This is because DataTorch lets you plug in multiple cloud storages, and this allows you to create a dataset with files that span separate storages without needing to reorganize the actual location of the file.</p><p>Click “Datasets” on the sidebar, then click the green plus icon to create a new dataset. Name your dataset, then click “Create”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dd_WDUYmyuEElYT7Urbb6A.png" /><figcaption>Your should see this after creating a new dataset.</figcaption></figure><p>You should see an upload modal similar to the one in the Files tab. There are multiple ways to add files to a dataset, so you could have created the dataset first, then uploaded the files directly here. But since we uploaded the files first, we will have to go back and assign the files to the dataset we just created.</p><p>Go back to Files &gt; DataTorch Storage &gt; Explorer. Select the check mark box to check all of the files in the storage, then click on the blue database icon to assign the selected files to a dataset.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PVZozqRhpmR_1FMwFRz16g.png" /></figure><p>Pick the dataset you just created, click “Update” and you should see all of your files get assigned. Go back to the Datasets tab and check it out!</p><p>If you want to organize your files into multiple datasets or rearrange files, DataTorch makes it really easy to do so. And best of all, your files don’t ever need to move from their original locations.</p><h3>Step 6: Distribute Annotation Tasks</h3><p>Right now, your dataset is essentially just a folder of raw images. You need to annotate the images, so that your classes can be identified to train a computer vision model.</p><p>Collaborating on annotation work with multiple people can get messy pretty quickly, especially with larger teams, but luckily DataTorch has a feature that simplifies the process of divvying up annotation work, called Jobs.</p><p>Go to “Jobs” in the sidebar, then click on “New Job”. Enter in a name and due date, don’t worry about the Description and Details section (but feel free to put something there, if you want). Click through to “Members”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WlBo7I2BWk59vzFobJYGpw.png" /><figcaption>A job with three labelers, and one reviewer.</figcaption></figure><p>Here, you will assign Labelers and Reviewers to the job. A Labeler is someone who does annotations. A Reviewer is an optional worker who must approve annotations before the work is considered complete. This is useful where there is a high level of quality control or domain knowledge necessary in the annotation work, such as with medical data.</p><p>Assign you and your two collaborators as Labelers, and add Reviewers if you want (but it isn’t necessary). Click through to “Files”, select your dataset, and click through to “Distribute”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AM6PW95Df1wWJKiu5I7KXg.png" /></figure><p>This last tab determines how much overlap you want each Labeler to have. Setting the number of passthroughs to 1 means the work will be evenly divided up between all of the labelers. On the other end, you can move the slider all the way to the right and set the number of passthroughs to the number of labelers, which will make each of the labelers annotate the entire dataset; the maximum amount of overlap.</p><p>Setting some overlap is good for calculating consensus, especially in cases where it can be easy to misinterpret or overlook an annotation. For basic annotation jobs, just 1 passthrough should be fine, so keep the slider all the way to the left and click “Create”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wQFC5CVPCeh2Y7PKjPZWqg.png" /><figcaption>You should see something similar to this after creating your job.</figcaption></figure><p>You will see the job conveniently split into separate annotation tasks. You should be able to see the files and comments surrounding each task, but you will only be able to annotate within the task assigned to you. Click the task assigned to you, then click the “Annotate” button in the top right corner to start working!</p><h3>Step 7: Annotate Data</h3><p>The annotator in DataTorch has many advanced features, but you can use it as a simple tool as well. Since you already created your labels previously, you should be able to start annotating right away.</p><p>You can read a more in-depth coverage of the tools in <a href="https://lindseyviann.medium.com/image-annotation-with-datatorch-io-4698506283f8">this article</a>, but for now, we will just be covering the basics for bounding box annotations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Egvx-vSPDMncuNqpE-MWmQ.png" /><figcaption>Annotator with key portions highlighted.</figcaption></figure><p>In the top right corner, you should see the currently selected label. This indicates what label any annotation you create will have. To change the currently selected label, press “A” on your keyboard and select the label you want from the dropdown.</p><p>Go ahead and switch the label to a class that is present in your image. On the right side of the annotator, you should see a few tool icons. Select the bounding box tool (it looks like a square). Draw a box around the instance of the class in your image. You should see the annotation pop up in the “Stack” module of your annotator, if it is present in your view. If it isn’t, go to Window &gt; Stack to enable it.</p><p>Repeat this process until all of the annotations are complete for all the classes in that image. If you mess up, click the little trash can next to the annotation to delete it. When you are finished, click the check mark in the upper right hand corner to indicate that the image is complete.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nURdWNFFSdxqfXrExgc3Nw.png" /><figcaption>The same image as above, annotated.</figcaption></figure><p>Once you mark all of your assigned files as complete, you should see your task also marked as complete:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lna20yynhvL4F9hG5Q5RMA.png" /></figure><p>When all of the tasks in the job are done, the job will be marked as complete, and your dataset will be fully annotated!</p><h3><strong>Step 8: Export Annotations</strong></h3><p>Once all of your data has been annotated, you will probably be excited to put your new dataset to good use. DataTorch lets you easily export annotations made on the platform to different annotation formats (in this case COCO) in just a few simple clicks.</p><p>DataTorch generates exports based on something called schemas, which are essentially conditional statements that define the annotations and files which you want to include in your export.</p><p>Click “Exports” in the sidebar and click the green “New Schema” button.</p><p>Name the new schema whatever you want, and change the Format to COCO. Leave Storage as is, then click the plus sign under “Where annotations” to create a new condition.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bgMlzigMbtdTNZtAraqX_g.png" /></figure><p>Set the condition to Created, Before, and set the date to a week in the future. You can click on “Calculate Schema Metrics” to get an idea of what your output will look like.</p><p>When you are done, click “Create” to create your schema. Once it is created, click on it, then click “Run Export” to tell it to execute.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wPRXB-oHrO1kWeIobZM3Tw.png" /></figure><p>Depending on the size of the schema, it might take some time to run, but the State indicator will change depending on the status. When it says “Success”, click on it and then click the “Download” button in the top right corner. Your COCO JSON file will download with all of the annotations included!</p><h3>Conclusion</h3><p>In this article, you learned how to collaborate on a COCO dataset from scratch using nothing but a few friends, a smartphone camera, and free online software. We:</p><ul><li>planned a dataset,</li><li>setup a project,</li><li>gathered data,</li><li>uploaded files,</li><li>organized files into datasets,</li><li>distributed the annotation tasks,</li><li>annotated data,</li><li>exported annotations,</li></ul><p>and created a cool dataset for building a Lucky Charms cereal classifier in the process.</p><p>I hope you found this tutorial useful, I hope you use it to build some cool new datasets for your own projects! I encourage you to leave a comment, or get in touch with me directly through email at michael@datatorch.io.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aCmds2QWw6rcJY2YKIQ5YQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7cd28f0a2c88" width="1" height="1" alt=""><hr><p><a href="https://medium.com/datatorch/how-to-create-a-custom-coco-dataset-from-scratch-7cd28f0a2c88">How To Create a Custom COCO Dataset from Scratch</a> was originally published in <a href="https://medium.com/datatorch">DataTorch</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>