<?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 Roberto Merlos on Medium]]></title>
        <description><![CDATA[Stories by Roberto Merlos on Medium]]></description>
        <link>https://medium.com/@ramg7?source=rss-20c4bcbac33c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*4FByf6uKMgAB2L5wRcUX4A.jpeg</url>
            <title>Stories by Roberto Merlos on Medium</title>
            <link>https://medium.com/@ramg7?source=rss-20c4bcbac33c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 18:24:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ramg7/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[Android User Preferences Simplified — Preferences DataStore with Hilt]]></title>
            <link>https://medium.com/@ramg7/android-user-preferences-simplified-preferences-datastore-with-hilt-c08da9691667?source=rss-20c4bcbac33c------2</link>
            <guid isPermaLink="false">https://medium.com/p/c08da9691667</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[jetpack-datastore]]></category>
            <category><![CDATA[kotlin]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[dagger-hilt]]></category>
            <dc:creator><![CDATA[Roberto Merlos]]></dc:creator>
            <pubDate>Thu, 24 Mar 2022 14:11:09 GMT</pubDate>
            <atom:updated>2022-03-31T23:44:03.873Z</atom:updated>
            <content:encoded><![CDATA[<h3>Android User Preferences Simplified — Preferences DataStore with Hilt</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mSk-OG35GF2eb7Maomkgtw.png" /></figure><p>Hi, welcome! This article covers a way to save simple user preferences using <em>DataStore</em> and the repository pattern in an Android application using dependency injection and some modern components.</p><p>We’ll cover how to save local data using Preferences DataStore using the repository pattern and dependency injection.</p><p>I will mostly cover how to store a string, but you can try with other primitive types. You can even store a JSON string with the help of GSON or Moshi. Even if this approach does not provide type safety in regards to JSON strings (which is not necessarily a bad thing), you can accomplish cool things in a simple way.</p><p>⚠️ Some pre-requisites to consider:</p><ul><li>Kotlin 1.5.0+ to be able to use the Result class.</li><li>Coroutines including Flow.</li><li>Hilt for dependency injection.</li></ul><p>If you have not idea what Hilt is or you are curious or have not set it up in your project, you can learn more about it here: <a href="https://dagger.dev/hilt/">https://dagger.dev/hilt/</a></p><p>You can follow this guide to learn how to set up Hilt here: <a href="https://developer.android.com/training/dependency-injection/hilt-android">https://developer.android.com/training/dependency-injection/hilt-android</a></p><p>First, if you are not familiar with DataStore I would suggest you to take a look at the official DataStore guide at: <a href="https://developer.android.com/topic/libraries/architecture/datastore">https://developer.android.com/topic/libraries/architecture/datastore</a></p><p>Now, let’s get into it ! … assuming you have Hilt setup :)</p><p>We are all familiar with SharedPreferences and its possible pains. DataStore was introduced to mitigate those pains and to make your Android life easier.<br>In this article, I’ll cover one of the two implementations of DataStore and the most similar to the old SharedPreferences: preferencesDataStore</p><blockquote><strong>Preferences DataStore</strong> stores and accesses data using keys. This implementation does not require a predefined schema, and it does not provide type safety.</blockquote><p>Now, go ahead and open your Android Studio project (or create a new one if you do not have one).</p><h3><strong>What dependencies do I need?</strong></h3><p>You can go ahead and add the following dependency in your dependencies block in your build.gradle (module level):</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/23dfe2498528de509b5af4fa5434d8aa/href">https://medium.com/media/23dfe2498528de509b5af4fa5434d8aa/href</a></iframe><p>The store has to be available through the entire application lifecycle. Hence, we will put it somewhere it makes sense. For me, it makes sense to define it in the same file where my Hilt module is. Your Hilt module should start looking like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a277b673865dbc0939e22966bbc6e2de/href">https://medium.com/media/a277b673865dbc0939e22966bbc6e2de/href</a></iframe><p>We will get back to this file and see how the entire file will look like once we set up the repository.</p><h3>Repository</h3><p>I mentioned earlier that we will use the repository pattern. To implement a fully working flow, you’ll need a view component, a view model, and repository.<br>If you don’t know already, data store preferences run asynchronously (you’ll also learn how to make them run synchronously later on). This calls out for coroutines. We will be using suspend functions along with flow to make this work.</p><p>For simplicity, I will keep the domain and data layers in the same file but perhaps you should not do this.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a0c3608de9439b489fbea50bc0636c93/href">https://medium.com/media/a0c3608de9439b489fbea50bc0636c93/href</a></iframe><p>This might look a bit scary if you are looking at it for the first time (understandable). The .data is a flow of data. There are cases where we might actually need multiple values. However, some times when dealing with preferences we just want a single value and flow has a handy method .first() or the safe version .firstOrNull()to make this possible.</p><h3>Hilt module</h3><p>We talked a bit about a Hilt module but did not want to give you the code where we provide the repository without first creating it.<br>So now, let’s look at the entire module that will provide both, the repository and the DataStore instance.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/cb17eb14e8d1ceb94223b3e2fd41f885/href">https://medium.com/media/cb17eb14e8d1ceb94223b3e2fd41f885/href</a></iframe><h3><strong>Example of Repository Usage (Demo)</strong></h3><p>That was not too bad right? Now all that is left to do is inject the repository in your view model and do whatever you have to do with it. If you need LiveData, flow has a .asLiveData() method. If you are happy with flow you can also observe the flow without any conversions. To give you an example of how a view model would look like, I will give you a dummy view model and a dummy activity with some dummy events.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8847e29cf5b92eb0d865d85142bee43f/href">https://medium.com/media/8847e29cf5b92eb0d865d85142bee43f/href</a></iframe><h3>Asynchronous vs Synchronous</h3><p>By default, all the method calls that we make from the repository will be asynchronous. Perhaps sometimes we might have the need for some reason to make them synchronous, for example, when testing. How do we accomplish this? We could use the runBlocking coroutine. Simply wrap the target suspend function method call like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/790e2d49d42e8e1bda59b8454424efad/href">https://medium.com/media/790e2d49d42e8e1bda59b8454424efad/href</a></iframe><h3><strong>Next Steps</strong></h3><p>I really hope that was not too bad. Most of this stuff perhaps might look a bit complex but if you have good understanding of coroutines and dependency injection, you should have a good base. If it went bad, maybe I did a poor job at explaining but either way, I hope you learned something.</p><p>Feel free to provide any feedback or ask any questions and clap if you can 😊</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c08da9691667" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Classifying Clothes with Scikit-learn and TensorFlow using F-MNIST.]]></title>
            <link>https://medium.com/cuny-csi-mth513/classifying-clothes-with-scikit-learn-and-tensorflow-using-f-mnist-f950f8e61837?source=rss-20c4bcbac33c------2</link>
            <guid isPermaLink="false">https://medium.com/p/f950f8e61837</guid>
            <category><![CDATA[fashion]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[mnist]]></category>
            <category><![CDATA[tensorflow]]></category>
            <category><![CDATA[keras]]></category>
            <dc:creator><![CDATA[Roberto Merlos]]></dc:creator>
            <pubDate>Tue, 16 Apr 2019 02:04:57 GMT</pubDate>
            <atom:updated>2020-08-09T23:32:37.505Z</atom:updated>
            <content:encoded><![CDATA[<h3>Overview</h3><p>In a world where machine learning is becoming the next real thing, we humans who desire some help from machines to tell us which clothes look better on us and to make sure that the machine knows that we are not putting a shirt in our heads instead of a hat, that machine must be able to identify and classify each piece of cloth according to its real value.</p><p>Classification is a really important task in the world of machine learning and data science and we are going to try to make a machine tell us either if we are wearing a 👕 in our 🧠 (←head … there is not a head emoji 😔) — anyways, let’s go back to happy mood … 🙂 …. So, what I was saying is that we are going to try to make a machine tell us either if we are wearing a shirt in our head or not. 🤓</p><p>Let’s get into it!</p><h3>F-MNIST</h3><p>You might be wondering what F-MNIST is and those who don’t know what it is might be taking an educated guess and thinking we are talking about some kind of UFO or something up there related to passionate stories that make us get goosebumps. Anyways, F-MNIST is nothing like that.</p><p>In the F-MINST Github page where the original data set is found we can find what F-MINST really is. I will quote it here so you don&#39;t have to search it up 😇</p><blockquote>Fashion-MNIST is a dataset of <a href="https://jobs.zalando.com/tech/">Zalando</a>&#39;s article images—consisting of a training set of 60,000 examples and a test set of 10,000 examples. Each example is a 28x28 grayscale image, associated with a label from 10 classes. We intend Fashion-MNIST to serve as a direct drop-in replacement for the original <a href="http://yann.lecun.com/exdb/mnist/">MNIST dataset</a> for benchmarking machine learning algorithms. It shares the same image size and structure of training and testing splits.</blockquote><blockquote>Here’s an example how the data looks (<em>each class takes three-rows</em>):</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*GNLB2jtcfb_xTqgQd9ntJA.png" /><figcaption><a href="https://github.com/zalandoresearch/fashion-mnist">Fashion-MNIST</a></figcaption></figure><p>Now I think it would be a super amazing if you visited Zalando Research’s Github by clicking the link below the picture or by clicking <a href="https://github.com/zalandoresearch/fashion-mnist">here</a> and you will learn more about it.</p><p>I also could not hold myself from getting this really cool animation from their Github … Trust me, it’s not your mouse or trackpad or whatever you might be using to control your computer doing all that movement, it’s a simple a gif. 😀</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*ASBL6bFOdz1KWLAgfKwsvw.gif" /><figcaption><a href="https://github.com/zalandoresearch/fashion-mnist">Fashion-MNIST</a></figcaption></figure><p>Now that you know a little bit more about F-MNIST, let’s for real get to coding!</p><p>Just before we start doing some futuristic related stuff 🤖 I want to mention that the dataset has a label for each cloth described here in ascending order:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5d64792d7ea0f5e7e907a4efb0cabcf3/href">https://medium.com/media/5d64792d7ea0f5e7e907a4efb0cabcf3/href</a></iframe><h3><strong>Coding </strong>👨‍💻👩‍💻</h3><p>In the title I mentioned about Scikit-learn and TensorFlow. We will use both approaches and see what we can do to make our machine be more accurate. Remember: we don’t want to end up with a shirt in our heads. Sadly, there is no hats in the data set but we have sneakers and the same reasoning applies: we don’t want to end up with a 👟 in our head.</p><p>It’s important to mention that for both approaches we will be using Python 🐍 Let’s finally get into it!</p><h4>A) Using Scikit-learn aka sklearn<strong>.</strong></h4><p>First off, let’s create a python file using your favorite editor such as Spyder or PyCharm. Let’s start by importing some libraries to start with.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/cd4ef0227cdff1b87a3149b8eefa941c/href">https://medium.com/media/cd4ef0227cdff1b87a3149b8eefa941c/href</a></iframe><p>Now, it’s time to load the test and training data using pandas. The CSV files originally downloaded from <a href="https://www.kaggle.com/zalando-research/fashionmnist">Kaggle</a> can be found <a href="https://drive.google.com/drive/folders/1D0FjGcngMxyQQJxe1ccq1vP8atfrwLTG?usp=sharing">here</a>.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9ecaf8132e7985c9da1e4b48ab26c244/href">https://medium.com/media/9ecaf8132e7985c9da1e4b48ab26c244/href</a></iframe><p>Now let’s get our models ready by creating a dictionary containing each model and let’s create a list that will hold each score initially having a score of 0. Also let’s get the pretty table ready and let’s give it a title and let’s define its columns. In the next section we will see which one works best! 😀</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3f4a30aac61629f55e6032d6ad3368aa/href">https://medium.com/media/3f4a30aac61629f55e6032d6ad3368aa/href</a></iframe><p>If you are confused of what is going on up there, I don’t blame you. If your face look like any of the following 😳 🤨 🤯 🥺 please now that I simply defined a dictionary called models and each line that looks like models[&quot;blahblah&quot;] = blehbleh is simply an addition to the models dictionary using key blahblah and value blehbleh which is a model. 😃</p><p>Now let’s go through all models using a loop and let’s see who beats who. 💪</p><p>First we do a cross validation in the training data and see which score will be the highest so we can use that model to compare it with the test data.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e6823fb42c1ee3a3997ee2062d434dee/href">https://medium.com/media/e6823fb42c1ee3a3997ee2062d434dee/href</a></iframe><p>We don’t want to check every single score that we get. So, we only check a score if it’s greater than the maximum score in our scores list. If it is, then we proceed and make a prediction accordingly with the test data excluding the Id, generating a results CSV file which results in some predictions.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/387cc52d97c85f8b85e0a594210ce714/href">https://medium.com/media/387cc52d97c85f8b85e0a594210ce714/href</a></iframe><p>After a long long wait ⏱ (if you don’t have GPU capabilities) we get the following results with our amazing pretty table:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4c13a98b2f923fec7d68e5b5e1c53cc5/href">https://medium.com/media/4c13a98b2f923fec7d68e5b5e1c53cc5/href</a></iframe><p>BOOM! Finally! … AND THE WINNER IS, OUR DEAR FRIEND FROM ENSEMBLE:GRADIENT BOOSTING CLASSIFIER ! *</p><p>DONE! 🎊 … a balloon doesn’t hurt so here we go → 🎈</p><p>Now we can be sure at least that our probability of wearing a 👟 in our head has decreased thanks to the GBC. 🙏</p><pre>* The 89.2% reflected is based on the cross-validation. The actual score would be less than that. It would oscillate between the 80s.</pre><h4>B) Using TensorFlow … with Keras.</h4><p>For this approach we will be using Keras which is a neural-network library written in Python.</p><p>Let’s start the same way we started before. Let’s import some important libraries!</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3f5a7fbeb83897c5dc307b785ba483ca/href">https://medium.com/media/3f5a7fbeb83897c5dc307b785ba483ca/href</a></iframe><p>If you followed the first part, you already know why we import pandas and the matplotlib library. After we import those libraries, we take some stuff from our neural network Keras. <a href="https://keras.io/callbacks/">EarlyStopping</a> will simply stop the training process when a monitored quantity stops improving. In this way we will have less risk of overfitting our data. The <a href="https://keras.io/models/sequential/">Sequential</a> model is a linear stack of layers and we will stack some layers.📚 The <a href="https://keras.io/layers/core/">core layers</a> we will be using are Dense, Dropout, Flatten, and Reshape. Additionally, we will be using a 2D <a href="https://keras.io/layers/convolutional/">convolutional layer</a> i.e. Conv2D and a 2D <a href="https://keras.io/layers/pooling/">pooling layer</a> i.e. MaxPooling2D. We will also test some <a href="https://keras.io/optimizers/">optimizers</a> and see which one works best.</p><p>Before we apply all of the above, let’s load our data. Again, the data can be found <a href="https://drive.google.com/drive/folders/1D0FjGcngMxyQQJxe1ccq1vP8atfrwLTG">here</a>. We will also define a list of class names and split our training data in two.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/535f4eb0ea8e56db7cf57e5d9a625876/href">https://medium.com/media/535f4eb0ea8e56db7cf57e5d9a625876/href</a></iframe><p>Now let’s put all those layers together using the sequential model 😀📚</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2fecd9656147277d651c31a0fa258bcb/href">https://medium.com/media/2fecd9656147277d651c31a0fa258bcb/href</a></iframe><p>Now let’s let’s compile our model and let’s choose an optimizer.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/031eb657625e71ca33fda718daa4bc1a/href">https://medium.com/media/031eb657625e71ca33fda718daa4bc1a/href</a></iframe><p>Now, it’s finally time to train our data. We normalize each pixel of the X_train data and we run it the fitting process for 7 epochs with 200 samples per gradient update (batch size) validating on 1% of the data and having patience = 2 which means that if after 2 epochs, a epoch has finished and there’s no improvement, the training process will be stopped. You might be wondering why 7 epochs and the answer to that is that such a number is arbitrary and that is what seemed to work best for me in the model we created.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d6597b742cb3b7a3b6b63dee71f476c5/href">https://medium.com/media/d6597b742cb3b7a3b6b63dee71f476c5/href</a></iframe><p>Now that the model has been trained, we can generate a results CSV file which results in some prediction and is ready for some testing.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/61bdc90aa220f12aeb10a41143ecd3c1/href">https://medium.com/media/61bdc90aa220f12aeb10a41143ecd3c1/href</a></iframe><p>Submitting our results to Kaggle for example where the real Y is we get a score of …</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M_RbLcldyufl1JpKJV3q-g.png" /></figure><p>… 89.4% !!! 🤯 We just beat the GBC!!!</p><p>Let’s see if we can improve it a little bit more. Let’s try something different. Let’s change the optimizer.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f4e7fa911273525bdc6bafb2e271f5d5/href">https://medium.com/media/f4e7fa911273525bdc6bafb2e271f5d5/href</a></iframe><p>Obviously we did that for a reason and you guessed right. The result improved!!! Now we get two of these → 🤯🤯</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pPtzktT7Xb63jj6D5ZWlnQ.png" /></figure><p>90.1% !!! 🤯 Does this — does this mean goodbye GBC? We’ll kindly put GBC aside. Let’s give a kind farewell to our dear friend GBC:</p><pre>Sorry GBC 😕 but we have to be sure we are not wearing a 👟 in our head and our dear neural network Keras seems to have beaten you today but don’t lose faith 💪😃</pre><p>… Anyways, excuse all of that. Now let’s do some predictions with X_test who we have not forgotten about !!!</p><p>Now we will ask our machine what images 6 – 11 in X_test are. Let’s see how well our machine performs and let’s plot those results.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/abfe679126b1dd4914da3c7e45b090b2/href">https://medium.com/media/abfe679126b1dd4914da3c7e45b090b2/href</a></iframe><h4>Now it’s time to see what in the world we have created and what things our 🤖 🧠 (robotic mind) thinks about the different images.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/305/1*TEpvRr3X85b9k81IzqoXEw.png" /><figcaption>Shirt 👔</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/305/1*WS8ReVtVCMhwKLfEqqM4bg.png" /><figcaption>Bag 👜</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/305/1*ZNZdTzvY9Kp-iEbXVONuAg.png" /><figcaption>Coat 🧥</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/305/1*bkb5yWhAa9wo8euHAYGxcg.png" /><figcaption>Sandal 👠</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/305/1*4RvAL4dwB7eRDOLZWhALww.png" /><figcaption>T-shirt/Top 👕</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/305/1*Q8tUMKQjI7plZtzEQ3Khaw.png" /><figcaption>Dress 👗</figcaption></figure><p>Tadaaaaa! Those results seem impressive, don’t they? Our machine seems to be very sure about what it’s doing. Would your amazing human mind classify those clothes in the same category? I would 🖐</p><h4>(Optional)</h4><p>Even though everything is optional if you think about it, this is optional 2x. If you have decided to try this last part, welcome! Let’s just simply try something else. I promise this is the last thing. Let’s search for some images and let’s see what our machine thinks about them. I will test a sneaker and a pair of trousers. 👟👖</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*rYUc62nRq-VqV3mKM9bx2Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*L92LlAN_ntwM7zBT2j-0hg.png" /></figure><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/962d698c20d68a163ea82966b1228129/href">https://medium.com/media/962d698c20d68a163ea82966b1228129/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/528/1*o4TNQlVWgFSWL_BRA_982g.png" /></figure><p>This results are not as impressive as the other ones. However, I would say our image conversion perhaps was not the best so I don’t blame our machine. There’re in fact humans who would misclassify those grayish looking images (I’m one of them 🤓). Therefore, there’s still more we can do to make our <strong>🤖 </strong>even better! 😃</p><p>I hope you enjoyed this “conversation” about fashion and clothes and brains and robots and whatever else you think we talked about. It was a pleasure to do some ML with fashion!</p><p>Clap if needed 👏😇.</p><pre><strong>I wish you an amazing day — full of robots 🤖</strong>🤖🤖</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f950f8e61837" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cuny-csi-mth513/classifying-clothes-with-scikit-learn-and-tensorflow-using-f-mnist-f950f8e61837">Classifying Clothes with Scikit-learn and TensorFlow using F-MNIST.</a> was originally published in <a href="https://medium.com/cuny-csi-mth513">CUNY CSI MTH513</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>