Deployed 4b8698a4 to dev with MkDocs 1.2.1 and mike 1.0.1

dev/developers/test-cases/index.html

@@ -1678,6 +1678,13 @@
     Keyboard
   </a>
   
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#application-episodes" class="md-nav__link">
+    Application Episodes
+  </a>
+  
 </li>
       
         <li class="md-nav__item">
@@ -1943,6 +1950,13 @@
     Keyboard
   </a>
   
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#application-episodes" class="md-nav__link">
+    Application Episodes
+  </a>
+  
 </li>
       
         <li class="md-nav__item">
@@ -2712,6 +2726,19 @@ randomly distributed throughout the <code>epoch</code>. </p>
  inferring time zone data for Keyboard from phone data can produce inaccurate results around the tz change. This happens because the device was on LA time until 11:59 and switched to NY time at 12pm, in terms of actual time 09 am LA and 12 pm NY represent the same moment in time so 09:00 LA and 12:01 NY are consecutive minutes.</p>
 </li>
 </ul>
+<h2 id="application-episodes">Application Episodes<a class="headerlink" href="#application-episodes" title="Permanent link">&para;</a></h2>
+<ul>
+<li>The feature requires raw application foreground data file and raw phone screen data file</li>
+<li>The raw data files contains data for 4 day.</li>
+<li>The raw conversation data contains records with difference in <code>timestamp</code> ranging from milliseconds to minutes.</li>
+<li>An app episode starts when an app is launched and ends when another app is launched, marking the episode end of the first one,
+or when the screen locks. Thus, we are taking into account the screen unlock episodes.</li>
+<li>There are multiple apps usage within each screen unlock episode to verify creation of different app episodes in each 
+screen unlock session. In the screen unlock episode starting from Fri 05:56:51, Fri 10:00:24, Sat 17:48:01, Sun 22:02:00, and Mon 21:05:00 we have multiple apps, both system and non-system apps, to check this.</li>
+<li>The 22 minute chunk starting from Fri 10:03:56 checks app episodes for system apps only.</li>
+<li>The screen unlock episode starting from Mon 21:05:00 and Sat 17:48:01 checks if the screen lock marks the end of episode for that particular app which was launched a few milliseconds to 8 mins before the screen lock.</li>
+<li>Finally, since application foreground is only for Android devices, this feature is also for Android devices only. All other files are empty data files</li>
+</ul>
 <h2 id="fitbit-calories-intraday">Fitbit Calories Intraday<a class="headerlink" href="#fitbit-calories-intraday" title="Permanent link">&para;</a></h2>
 <p>Description</p>
 <ul>