<?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 Jake Yeager on Medium]]></title>
        <description><![CDATA[Stories by Jake Yeager on Medium]]></description>
        <link>https://medium.com/@jakeyeager?source=rss-eb6e82475272------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*BQzXqP8jLYvoezMi.</url>
            <title>Stories by Jake Yeager on Medium</title>
            <link>https://medium.com/@jakeyeager?source=rss-eb6e82475272------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 03:52:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jakeyeager/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[Earthquake Forecast: Green Light for >M8 Event]]></title>
            <link>https://medium.com/@jakeyeager/earthquake-forecast-green-light-for-m8-event-6ec5d78601fc?source=rss-eb6e82475272------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ec5d78601fc</guid>
            <category><![CDATA[earthquake]]></category>
            <category><![CDATA[seismic]]></category>
            <category><![CDATA[forecasting]]></category>
            <dc:creator><![CDATA[Jake Yeager]]></dc:creator>
            <pubDate>Wed, 14 Jun 2017 18:09:57 GMT</pubDate>
            <atom:updated>2017-06-14T18:09:57.418Z</atom:updated>
            <content:encoded><![CDATA[<p>I don’t really expect anyone to read this forecast. I’m honestly just after the timestamp for the article generated from a system that is not under my direct control, or could be manipulated by myself (like Facebook). Forecasting earthquakes is a *&amp;@# and verification is worst because people seem to have a problem with displaying failure. Failure is part of the learning. My problem seems to be just writing the f***g forecast at all. I’ve mailed them to myself to get the “poor mans copyright” Postmark. That has become a weird stumbling block as, mentally, I don’t have the time to print out and mail myself a letter, but totally have time to write PHP for hours on end #codersknowitstrue #dohashtagsworkonmedium. Plus I then had to scan the letters and upload them somewhere. Let’s try a little piece on Medium and see how it goes!</p><p>The following screenshots are from an app I created to track seismic activity. I’m not quite sure how to best protect this intellectual property, so I will be a little non-specific (some might say cagey) about some of the collection parameters. Let’s just say that each plotted day collects volume (total count) of seismic activity from a discreet, and non-disclosed length of time. This period is consistently tracked for all days and all charts. The charts also track specific earthquake magnitudes, broken out and color coded. Orange is M5.0 to M5.9; red is M6.0 to M6.9; purple is M7.0 to M7.9; black is M8.0 to M8.9 . Some of the charts are cut off, but this app was designed really for me and not to publish as screenshots, but here I am screenshooting… #thatslife. Now that we have some apologies, disclaimers and labeling out of the way, here is what I’m seeing as a developing pattern:</p><h3>This is 2013</h3><p>2013 had two &gt;M8 events: one near <a href="https://earthquake.usgs.gov/earthquakes/eventpage/usc000f1s0#executive">Lata</a> on Feb 6thUTC, and one near <a href="https://earthquake.usgs.gov/earthquakes/eventpage/usb000h4jh#executive">Okhotsk</a> on May 24th UTC. In the following screenshot you can see them peeking up in the chart cut off at the bottom. Prior to both events there is a gradual dip in activity in the smaller event ranges followed by a marked increase just before the M8. In this example, the Feb Lata event displays this pattern more clearly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fxSFin7YL7_pelPqHB5TwA.png" /></figure><h3>This is 2014</h3><p>In 2014 we had a <a href="https://earthquake.usgs.gov/earthquakes/eventpage/usc000nzvd#executive">M8.2 event near Chile</a> on April 1st UTC. In the charts below you can see that this event is followed by a whole pile of &gt;M7 events. Again, there is the dip and sudden surge in the days/weeks pervious to the M8 event. Those of you seeing this and still reading will say “<em>what about that June plunge in the &gt;M6 chart?</em>” Well, I’m glad you asked because that single &gt;M7 event hanging out in the middle of the purple line is <a href="https://earthquake.usgs.gov/earthquakes/eventpage/usc000rki5#executive">a M7.9</a> that occurred in the Aleutian Islands. It also deviates slightly from the pattern we are tracking as there is the dip, but no rise. Just BAM.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3nCxnNWarIThwkjozl7yEw.png" /></figure><h3>This is 2015</h3><p>In 2015 we again had a <a href="https://earthquake.usgs.gov/earthquakes/eventpage/us20003k7a#executive">Chile earthquake at M8.3</a> on Sept 16th UTC. We can again see the dip-and-surge prior to this event. Interestingly as well we can see the gradual slide of the &gt;M5 range earlier in the year which bottoms out just before the pile of &gt;M7 events that bloom in late April into June. The &gt;M6 range in corresponding early-year timeframe shows the opposite rising trend. The leading event of this April M7 bloom was the <a href="https://earthquake.usgs.gov/earthquakes/eventpage/us20002926#executive">damaging M7.8 Nepal event</a> on April 25th UTC.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0kqVJRrPdGqHA7QF5XYdpA.png" /></figure><h3>This is 2016</h3><p>2016 had a pause in &gt;M8 events but made up for activity in &gt;M7 events. We can see our dip-and-surge in late April and early May just before the almost back-to-back <a href="https://earthquake.usgs.gov/earthquakes/eventpage/us20005iis#executive">M7.0 Japan event</a> and <a href="https://earthquake.usgs.gov/earthquakes/eventpage/us20005j32#executive">M7.8 Ecuador event</a>. The pattern repeats in a soft mirroring June and Aug, but the marked dramatic pattern in Oct precedes the Nov Gisborne M7.0 and <a href="https://earthquake.usgs.gov/earthquakes/eventpage/us1000778i#executive">Amberley M7.8</a> events.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mHUQ24AZ78HuC45vSd1LuQ.png" /></figure><h3>This is 2017</h3><p>Currently we can see that &gt;M5 range has dipped down, and &gt;M6 is not far behind. We have had a few M6 events in the last week, in <a href="https://earthquake.usgs.gov/earthquakes/eventpage/us20009ly0#executive">Greece</a> and <a href="https://earthquake.usgs.gov/earthquakes/eventpage/us20009mbt#executive">Central America</a>. This might be maintenance energy releases in the lithosphere, or could be the surge after the dip. The ominous fact is that we are weeeeeell beyond the average period for a &gt;M7 &amp; &gt;M8 event. They are late. My guess is that we are in for a whomp end of June, early July.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mOcLJV5vs_nnr71zOkz2sQ.png" /></figure><p>I post more“short-read” forecast updates on <a href="https://www.facebook.com/quakehunter">Quakehunter Facebook</a> and and <a href="https://twitter.com/thequakehunter">Quakehunter Twitter</a> if you want to stay connected to these developments. I don’t do <a href="https://www.wired.com/2013/05/earthquakes-patterns-and-predictions/">syzygy or super-moons</a> so if you’re looking for that stuff you might be disappointed. Maybe not.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ec5d78601fc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Yikes… hello world]]></title>
            <link>https://medium.com/@jakeyeager/yikes-hello-world-33a47d01692c?source=rss-eb6e82475272------2</link>
            <guid isPermaLink="false">https://medium.com/p/33a47d01692c</guid>
            <dc:creator><![CDATA[Jake Yeager]]></dc:creator>
            <pubDate>Sun, 24 Jul 2016 04:17:58 GMT</pubDate>
            <atom:updated>2017-05-25T04:03:40.591Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<p>Guess I’ll use this for something important in a minute.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/231/1*PX3KJ0QFaCQXOy-2wuXzlg.png" /><figcaption>Is this a static or dynamic Mag5 image…? I added it 2017–05–24 20:53…</figcaption></figure><p>I’m using this as a dev piece to figure out how to add/update content in Medium.</p><iframe src="https://cdn.embedly.com/widgets/media.html?type=text%2Fhtml&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;schema=instagram&amp;url=https%3A//www.instagram.com/p/BUdjAJjj05Y/&amp;image=https%3A//i.embed.ly/1/image%3Furl%3Dhttps%253A%252F%252Fscontent.cdninstagram.com%252Ft51.2885-15%252Fs640x640%252Fsh0.08%252Fe35%252F18644938_1829032167423314_8619114367880790016_n.jpg%26key%3D4fce0568f2ce49e8b54624ef71a8a5bd" width="640" height="640" frameborder="0" scrolling="no"><a href="https://medium.com/media/c2b2e0c2a438c9954b5e81bb1dd415cd/href">https://medium.com/media/c2b2e0c2a438c9954b5e81bb1dd415cd/href</a></iframe><p>This is something that is learned the hard way. Also ‘=’ vs ‘==’ vs ‘===’. I saw a meme for this equals business, as well. It involved AI robots killing everyone, but I can’t find it now.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=33a47d01692c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>