Day 2 TensorFlow voter data project environment setup

Things are moving along. Right now I have 23 days left to submit my current project to the ⚡#PoweredByTF 2.0 Challenge!. That should not be a problem, but you never know what is going to happen. Right now I am fully registered and I setup a new GitHub project just for this effort.

  • My environment setup is going to be twofold for this project. My primary efforts will occur on the Google Cloud Platform and my secondary effort will occur on Colaboratory. If you have not heard of Colaboratory, then you are missing out on something awesome. It is a very easy to use free Jupyter notebook environment run by Google.
  • My initial build out included the following efforts on GCP:
    • GCP –> Artificial Intelligence –>  AI Platform –> Notebooks –> TensorFlow –> with GPU (us-west1-b, 4 vCPUs, 15 GB RAM, 1 NVIDIA Tesla K80, 100 GB Disk)
    • That yielded a strange error,  “Quota ‘GPUS_ALL_REGIONS’ exceeded. Limit: 0.0”.
    • The solution was to head out to the IAM & admin section of GCP and look up the quotas for my GPUS_ALL_REGIONS and request access to another GPU
    • I found the right global quota to change: GLOBAL Attribute | GPUS_ALL_REGIONS and asked for a quote increase using the handy dandy edit quotas button at the top of the IAM & admin –> Quotas screen
    • I got help from Julia over at Google support in the matter of a couple hours and then went back and made the notebook environment setup request again
    • Keep in mind that using this setup requires the commitment of funds to work on the project, but I wanted a dedicated GPU all to myself for the stretch run and it seemed like something that would bring me joy
      • The alternative here would be to use Colaboratory instead of paying for a dedicated GPU on GCP
    • Everything is now setup to run TensorFlow in a notebook on my own VM with a sweet NVIDIA Tesla K80 GPU
    • You can grab the instructions I used to true it up to 2.0.0-alpha0 here
  • Setting up on Colaboratory took a matter of seconds
    • Go check out https://colab.research.google.com/
    • I’m going to be running a parallel set of notebooks throughout the whole process. My primary development will occur over on GCP and I’ll test every one of the notebooks on Colaboratory and use the export to GitHub from that environment to save the project off for submission

Day 1 TensorFlow voter data project research

Today I started the process of conducting some literature searches and began digging into what work exists related to people using TensorFlow on voter data. The following observations are my notes entered in real-time for later review. Before I used EndNote to capture all my citations, but this time around I thought it might be better to just write it all down during this first pass at digging into what exists publicly.

Today I signed up for a #PoweredByTF 2.0 challenge contest

Earlier today it seemed like a good idea to sign up for a TensorFlow contest from DevPost that ends in about 27 days. My efforts are going to focus on using the TensorFlow 2.0 Alpha release code to model out changes in voting patterns. I’m going to train the model to look for irregularities. My best guess at the moment is that within the next 27 days I can setup my Google Cloud Platform instance and get the model running. The #PoweredByTF 2.0 Challenge on DevPost! will be a good test of my skills. Maybe jumping into a few coding challenges is a good way to push myself to move forward and enhance my programming toolkit.

Maybe this will be a good reason for me to go on a video diet for the next 27 days. For the most part, I have stopped consuming most social media. Maybe trying to avoid consuming video for the next 27 days is a good logical next step. It could be a good method to go about really digging in and doing some deep learning about TensorFlow. I have done a bunch of certifications and used it for a variety of reasons, but none of them were related to a GitHub project. This will be my first effort to post a bunch of notebooks on GitHub to allow people to replicate my work. Maybe this will be a good test of my coding skills and my paper writing skills at the same time.

I woke up wanting more today

Today was one of those days where I woke up wanting more. It was one of those days where I asked myself what was next. Some of that was about figuring out a really hard problem to tackle and really sinking my time and energy into finding a resolution. Part of it has been about moving beyond the daily grind of things that happen in a series vs. things that make a dent in the universe. The second question in that statement is much harder to achieve and rarely even attempted. We have to dig in and pick fights with the hardest problems. Standing down is not the way to figure out how to push past the edge of what is possible.

I’m in the market for a new Chromebook

Here we go again with some technology related challenges. My ASUS Chromebook flip C302 now has had two separate keys fail on it. The number 5 and 6 keys are not working at all. Both keys have been taken apart and I messed with them several times. None of that worked out. Right now I am working on a Google Docs file on my Pixel 3 XL smartphone typing on a Bluetooth keyboard. That could be the new normal for some time. This is one way to go about writing and it could be the path forward. It is for sure the lowest cost path forward given that I already have the phone and the Logitech Bluetooth keyboard. Maybe that is enough to seal the deal and drive me to writing on my phone. I had tried this before for a few days and it did not work out very well.

This time around might be different. I just went into the keyboard settings and turned off the onscreen keyboard when the physical keyboard is connected via Bluetooth. Just making that one change increases the amount of screen open to viewing words by about double. Maybe that will help make this more interesting this time around. My plan is to go back to writing for over and hour a day. Most of that writing time will happen at night right before bed. For better or worse that writing window has always been the best way to go about producing a large amount of words. This is one of those times where thinking out loud is probably the right way to go about things.