<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Uberhip</title><link>http://uberhip.com/</link><description>Recent content on Uberhip</description><generator>Hugo -- 0.136.1</generator><language>en-us</language><lastBuildDate>Thu, 14 Mar 2024 00:00:00 +0000</lastBuildDate><atom:link href="http://uberhip.com/index.xml" rel="self" type="application/rss+xml"/><item><title>🌵⚾️ Spring Training Calendar</title><link>http://uberhip.com/spring-training/</link><pubDate>Thu, 14 Mar 2024 00:00:00 +0000</pubDate><guid>http://uberhip.com/spring-training/</guid><description>&lt;p>Welcome to my page for my 🌵⚾️ tickets for the &lt;a href="https://www.sfgiants.com/springtraining">2025 Spring Training season for
the San Francisco Giants&lt;/a> at
Scottsdale Stadium.&lt;/p>
&lt;h2 id="the-calendar">The Calendar&lt;/h2>
&lt;p>The calendar and table below shows the ticket availability for the 2025 Spring
Training season.&lt;/p>
&lt;p>&lt;spring-training-calendar>&lt;/spring-training-calendar>&lt;/p>
&lt;h2 id="the-seats">The Seats&lt;/h2>
&lt;p>I have four seats in Section 103, Row A Seat 6, and Row B
Seats 5, 6, and 7. This section sits right behind home plate, so it&amp;rsquo;s a great
place to watch the game.&lt;/p></description></item><item><title>Webxr Stack Diagram</title><link>http://uberhip.com/posts/2021-12-03-webxr-stack-diagram/</link><pubDate>Fri, 03 Dec 2021 06:43:44 -0700</pubDate><guid>http://uberhip.com/posts/2021-12-03-webxr-stack-diagram/</guid><description>&lt;p>I am working on an &lt;a href="https://www.meetup.com/Phoenix-VR-For-Good-Meetup/events/282439401/">Intro to WebXR presentation for the Phoenix VR Meetup group&lt;/a>.
As part of this I&amp;rsquo;ve been trying to make a diagram of the WebXR technology
stack. These sorts of things are always oversimplifications. With feedback
from several people on the WebXR Discord, I was able to come up with a decent
diagram which is shown below.&lt;/p>
&lt;p>&lt;img alt="WebXR Technology Stack" loading="lazy" src="http://uberhip.com/webxr-stack-v1.png" title="WebXR Technology Stack">&lt;/p>
&lt;p>This diagram is split roughly into the blue/green &amp;ldquo;Application Layer&amp;rdquo;, the
orange &amp;ldquo;Browser Layer&amp;rdquo; and the red &amp;ldquo;Hardware Layer&amp;rdquo; at the bottom. The
WebGL and WebXR boxes are the &amp;ldquo;new&amp;rdquo; APIs that browsers have implemented
which provide access to the relevant GPU/XR hardware. Of course Javascript
and WASM are both browser APIs, but I omit them since, despite their importance,
they aren&amp;rsquo;t the new enabling technologies.&lt;/p></description></item><item><title>The Missing Link to the Metaverse</title><link>http://uberhip.com/posts/2021-10-28-metaverse-missing-link/</link><pubDate>Thu, 28 Oct 2021 07:30:00 -0700</pubDate><guid>http://uberhip.com/posts/2021-10-28-metaverse-missing-link/</guid><description>&lt;p>Last week &lt;a href="https://twitter.com/auradeluxe">Tony Parisi&lt;/a> shared the
&lt;a href="https://medium.com/meta-verses/the-seven-rules-of-the-metaverse-7d4e06fa864c">Seven Rules of the Metaverse&lt;/a>
which &lt;a href="https://twitter.com/kentbye/status/1452047797394440194">Kent Bye (host of the Voices of VR Podcast)&lt;/a>
endorsed as &lt;a href="https://voicesofvr.com/parisis-metaverse-manifesto-unpacking-his-seven-rules-for-the-metaverse/">&amp;ldquo;Tony Parisi&amp;rsquo;s Metaverse Manifesto&amp;rdquo;&lt;/a>.&lt;/p>
&lt;p>These seven rules and the entire manifesto really resonated with me and bear
repeating here.&lt;/p>
&lt;ul>
&lt;li>Rule #1. There is only one Metaverse.&lt;/li>
&lt;li>Rule #2: The Metaverse is for everyone.&lt;/li>
&lt;li>Rule #3: Nobody controls the Metaverse.&lt;/li>
&lt;li>Rule #4: The Metaverse is open.&lt;/li>
&lt;li>Rule #5: The Metaverse is hardware-independent.&lt;/li>
&lt;li>Rule #6: The Metaverse is a Network.&lt;/li>
&lt;li>Rule #7: The Metaverse is the Internet.&lt;/li>
&lt;/ul>
&lt;h2 id="the-problem">The Problem&lt;/h2>
&lt;p>Inspired, I threw together some &lt;a href="https://aframe.io/">A-Frame&lt;/a>
code, donned my headset, eager to leap from page to page, but alas there was
sadness in my virtual land. It seems that the state of link traversal in
WebXR is no better today than it was in 2017 when I first picked up my headset.
&lt;strong>When following a link between two web pages in &amp;ldquo;vr mode&amp;rdquo; the user is kicked
out of &amp;ldquo;vr mode&amp;rdquo; to see the 2D browser window and URL bar. This is bad, how
do we fix this missing link?&lt;/strong>&lt;/p></description></item><item><title>Astrophotography - Getting Started</title><link>http://uberhip.com/posts/2019-02-16-starting-astrophotography/</link><pubDate>Sat, 16 Feb 2019 06:28:00 +0000</pubDate><guid>http://uberhip.com/posts/2019-02-16-starting-astrophotography/</guid><description>&lt;p>&lt;img alt="m42 and m43 nebulae" loading="lazy" src="http://uberhip.com/images/m42-large.png">&lt;/p>
&lt;p>The above image is a smaller version of the first decent picture I took with my
recently acquired astrophotography setup. It was taken on Feb 11th, 2019 from,
my driveway in Tempe, AZ, in the middle of the Phoenix, AZ metropolitan area.
The image is a composite of 19 x 30s exposures, stacked with the free Windows
program, &lt;a href="http://deepskystacker.free.fr/english/index.html">DSS&lt;/a>, and a little
histogram tweaking in Photoshop. The image is of the
&lt;a href="https://en.wikipedia.org/wiki/Orion_Nebula">Orion nebula (M42)&lt;/a> and
&lt;a href="https://en.wikipedia.org/wiki/Messier_43">M43&lt;/a>. More info and the full
resolution image can be found where I uploaded the image to
&lt;a href="https://www.astrobin.com/390498/0/">Astrobin&lt;/a>.&lt;/p></description></item><item><title>Experiment - Rogers Ruins</title><link>http://uberhip.com/posts/2017-12-09-experiment-rogers_ruins/</link><pubDate>Sat, 09 Dec 2017 06:28:00 +0000</pubDate><guid>http://uberhip.com/posts/2017-12-09-experiment-rogers_ruins/</guid><description>&lt;p>Recently, in my free time, I&amp;rsquo;ve been playing with VR/AR related technologies.
My interests have mostly been building photorealistic scenes or models using
photogrammetry tools like &lt;a href="http://www.agisoft.com/">Agisoft Photoscan&lt;/a>. I may
start sharing more of my experiments, like this one, here in the future.&lt;/p>
&lt;p>&lt;img alt="Superstition Mountains" loading="lazy" src="http://uberhip.com/images/south-central-superstitions.jpg">&lt;/p>
&lt;p>In November 2017 friends and I went for a hike deep into the Superstition
Mountains in central Arizona to 600 year old Native American Indian ruins
called &amp;ldquo;Rogers Canyon Ruins&amp;rdquo; (&lt;a href="https://hikearizona.com/map.php?QX=6728">GPS route&lt;/a>).
I documented the hike with a few 360 photos along the trail using my 2016
Samsung Gear 360 camera and used Google&amp;rsquo;s &lt;a href="http://www.marzipano.net/">Marzipano&lt;/a>
to create this &lt;a href="http://uberhip.com/misc/rr/">360 Tour of Roger&amp;rsquo;s Trough Trail hike&lt;/a>&lt;/p></description></item><item><title>Installing GQRX on OS X 10.11, El Capitan, for HackRF.</title><link>http://uberhip.com/posts/2015-10-17-os_x_el_capitan_gqrx_hackrf/</link><pubDate>Sat, 17 Oct 2015 10:14:02 +0000</pubDate><guid>http://uberhip.com/posts/2015-10-17-os_x_el_capitan_gqrx_hackrf/</guid><description>&lt;p>I have recently created two &lt;a href="http://brew.sh/">Homebrew&lt;/a> formulas to help OS X
users install GQRX on 10.11, El Capitan. Fortunately most of the dependencies
are already available so all I had to do was create a formula for
&lt;a href="http://gqrx.dk/">GQRX&lt;/a> and &lt;a href="http://sdr.osmocom.org/trac/wiki/GrOsmoSDR">Osmosdr&lt;/a>.
The source to these formulas can be found in my
&lt;a href="https://github.com/godber/homebrew-godber">homebrew-godber&lt;/a> github project.
Though to install GQRX all you have to do is setup my &amp;rsquo;tap&amp;rsquo; and then install the
package as shown below:&lt;/p></description></item><item><title>Open Source ANTLR4 Grammar for NASA's PDS3 Label Format</title><link>http://uberhip.com/posts/2015-01-18-pds3_antlr_grammar/</link><pubDate>Sat, 17 Jan 2015 09:14:02 +0000</pubDate><guid>http://uberhip.com/posts/2015-01-18-pds3_antlr_grammar/</guid><description>&lt;p>At the November 2014 &lt;a href="http://desertpy.com">DesertPy&lt;/a> meeting I learned
about &lt;a href="http://www.antlr.org/">ANTLR the parser generator&lt;/a> and thought
that would be the proper way to approach writing a parser for the labels
of NASA&amp;rsquo;s PDS3 file format. I spent some time and read &lt;a
href="http://www.amazon.com/gp/product/1934356999/ref=as_li_tl?ie=UTF8&amp;camp=1789&amp;creative=390957&amp;creativeASIN=1934356999&amp;linkCode=as2&amp;tag=uberhipcom-20&amp;linkId=XLNAY4K5CBVP35GF">The
Definitive ANTLR 4 Reference&lt;/a>&lt;img
src="http://ir-na.amazon-adsystem.com/e/ir?t=uberhipcom-20&amp;l=as2&amp;o=1&amp;a=1934356999"
width="1" height="1" border="0" alt="" style="border:none !important;
margin:0px !important;" /> (affiliate link) and have pieced together a
grammar that works fairly well at this point.&lt;/p>
&lt;p>The ANTLR grammar and corresponding generated Python parser are Open
Source, BSD Licensed and are available on GitHub:&lt;/p></description></item><item><title>Packages 404 Errors when using debmirror with ubuntu.</title><link>http://uberhip.com/posts/2014-11-26-ubuntu-debmirror-packages-404-error/</link><pubDate>Wed, 26 Nov 2014 09:14:02 +0000</pubDate><guid>http://uberhip.com/posts/2014-11-26-ubuntu-debmirror-packages-404-error/</guid><description>&lt;p>This is one of those blog posts a person writes in hopes of eventually
finding it&amp;rsquo;s contents via a Google search when an error is encountered
again. So, hello Austin, you have found the answer to your &amp;lsquo;debmirror
ubuntu package 404&amp;rsquo; error problem.&lt;/p>
&lt;p>I have my own Ubuntu mirror for precise and trusty packages. This
mirror is maintained with the &lt;code>debmirror&lt;/code> program. There are
occasionally situations where it starts reporting 404 errors for
&lt;code>Packages&lt;/code> files when there are &lt;code>Packages.gz&lt;/code> and &lt;code>Packages.bz2&lt;/code> files
that it should be using. These errors look like this when running my
mirror script:&lt;/p></description></item><item><title>Warping Brien - Image Reprojection with Python OpenCV</title><link>http://uberhip.com/posts/2014-10-26-warping-brien/</link><pubDate>Sun, 26 Oct 2014 07:14:02 +0000</pubDate><guid>http://uberhip.com/posts/2014-10-26-warping-brien/</guid><description>&lt;blockquote>
&lt;p>NOTE: This post was converted from HTML generated from an Jupyter Notebook to
markdown so it includes discussion of using Jupyter notebook, I left this
language in the post itself.&lt;/p>
&lt;/blockquote>
&lt;h1 id="image-reprojection">Image reprojection&lt;/h1>
&lt;p>My friend Brien is a bit of an artist and a bit of a tech nerd so he thought it
would be a great idea to make a timelapse video of him drawing. So he put the
&lt;a href="http://chdk.wikia.com/wiki/CHDK">CHDK firmware&lt;/a> on his Canon S90 camera and
set it up to take an exposure every 2-3 seconds. He reprojected the drawing
portion of the image back into a rectangle and made a video out of it. He
managed to do the original video using only &lt;a href="http://www.imagemagick.org/">ImageMagick&lt;/a>
command line tools. You can watch his
&lt;a href="https://www.youtube.com/watch?v=BPijRAK2NHg">Timelapse Drawing 1&lt;/a> on YouTube.&lt;/p></description></item><item><title>Using update-alternatives to make docker.io accessible as docker.</title><link>http://uberhip.com/posts/2014-08-02-docker-command-on-ubuntu/</link><pubDate>Sat, 02 Aug 2014 07:14:02 +0000</pubDate><guid>http://uberhip.com/posts/2014-08-02-docker-command-on-ubuntu/</guid><description>&lt;p>I&amp;rsquo;ve seen some people ask about making the &lt;a href="https://www.docker.com/">Docker&lt;/a> command
&lt;code>docker.io&lt;/code> on Ubuntu work like it does in the examples: &lt;code>docker&lt;/code>. I
found this inconvenient too, but fortunately, Ubuntu and Debian have
had a solution to this for a long time, it&amp;rsquo;s called
&lt;a href="http://www.debian-administration.org/article/91/Using_the_Debian_alternatives_system">alternatives&lt;/a>. In
this particular case, there is already an Ubuntu package called &lt;code>docker&lt;/code>
which is why they are trying to de-conflict executable names by using
&lt;code>docker.io&lt;/code> in the first place. Ironically, the original &lt;code>docker&lt;/code>
package doesn&amp;rsquo;t even contain an executable named &lt;code>docker&lt;/code>. Or at least
it doesn&amp;rsquo;t as of Ubuntu 14.04.&lt;/p></description></item></channel></rss>