junos
/
rapids
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Deployed d7fbee59 to dev with MkDocs 1.2.1 and mike 1.0.1

gh-pages
github-actions 2021-07-01 21:04:20 +00:00
parent b90c540d76
commit f5353b360c
4 changed files with 72 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

85
dev/developers/test-cases/index.html
View File

@ -2036,9 +2036,9 @@
<tr>
<td>Phone Applications Foreground</td>
<td>RAPIDS</td>
<td>N</td>
<td>N</td>
<td>N</td>
<td>Y</td>
<td>Y</td>
<td>Y</td>
</tr>
<tr>
<td>Phone Battery</td>
@ -2606,7 +2606,7 @@ When generating test data, all traces for iOS device need to be unique otherwise
<h2 id="light">Light<a class="headerlink" href="#light" title="Permanent link">&para;</a></h2>
<p>Description</p>
<ul>
<li>The 4-day raw data is contained in <code>phone_light_raw.csv</code></li>
<li>The 4-day raw light data is contained in <code>phone_light_raw.csv</code></li>
<li>One episode for each daily segment (<code>night</code>, <code>morning</code>, <code>afternoon</code> and <code>evening</code>)</li>
<li>Two episodes locate in the same 30-min segment (<code>Fri 00:07:27.000</code> and <code>Fri 00:12:00.000</code>)</li>
<li>Two episodes locate in the same daily segment (<code>Fri 01:00:01.000</code> and <code>Fri 03:59:59.654</code>)</li>
@ -2677,25 +2677,72 @@ When generating test data, all traces for iOS device need to be unique otherwise
</ul>
<h2 id="application-foreground">Application Foreground<a class="headerlink" href="#application-foreground" title="Permanent link">&para;</a></h2>
<ul>
<li>The raw application foreground data file contains data for 1 day.</li>
<li>The raw application foreground data contains 7 - 9 rows of data
for each <code>epoch</code>. The records for each <code>epoch</code> contains apps that
are randomly selected from a list of apps that are from the
<code>MULTIPLE_CATEGORIES</code> and <code>SINGLE_CATEGORIES</code> (See
<a href="">testing_config.yaml</a>). There are also records in each epoch
that have apps randomly selected from a list of apps that are from
the <code>EXCLUDED_CATEGORIES</code> and <code>EXCLUDED_APPS</code>. This is to test
that these apps are actually being excluded from the calculations
of features. There are also records to test <code>SINGLE_APPS</code>
calculations.</li>
<li>Since application foreground is only available for Android there
is only one file that contains data for Android. All other files
(i.e. for iPhone) are empty data files.</li>
<li>The 4-day raw application data is contained in <code>phone_applications_foreground_raw.csv</code></li>
<li>One episode for each daily segment (night, morning, afternoon and evening)</li>
<li>Two episodes locate in the same 30-min segment (<code>Fri 10:12:56.385</code> and <code>Fri 10:18:48.895</code>)</li>
<li>Two episodes locate in the same daily segment (<code>Fri 11:57:56.385</code> and <code>Fri 12:02:56.385</code>)</li>
<li>One episode before the time switch (<code>Sun 00:07:48.001</code>) and one episode after the time switch (<code>Sun 05:10:30.001</code>)</li>
<li>Two custom category (<code>Dating</code>) episode, one at <code>Fri 06:05:10.385</code>, another one at <code>Fri 11:53:00.385</code></li>
</ul>
<p>Checklist:</p>
<table>
<thead>
<tr>
<th>time segment</th>
<th>single tz</th>
<th>multi tz</th>
<th>platform</th>
</tr>
</thead>
<tbody>
<tr>
<td>30min</td>
<td>OK</td>
<td>OK</td>
<td>Android</td>
</tr>
<tr>
<td>morning</td>
<td>OK</td>
<td>OK</td>
<td>Android</td>
</tr>
<tr>
<td>daily</td>
<td>OK</td>
<td>OK</td>
<td>Android</td>
</tr>
<tr>
<td>threeday</td>
<td>OK</td>
<td>OK</td>
<td>Android</td>
</tr>
<tr>
<td>weekend</td>
<td>OK</td>
<td>OK</td>
<td>Android</td>
</tr>
<tr>
<td>beforeMarchEvent</td>
<td>OK</td>
<td>OK</td>
<td>Android</td>
</tr>
<tr>
<td>beforeNovemberEvent</td>
<td>OK</td>
<td>OK</td>
<td>Android</td>
</tr>
</tbody>
</table>
<h2 id="activity-recognition">Activity Recognition<a class="headerlink" href="#activity-recognition" title="Permanent link">&para;</a></h2>
<p>Description</p>
<ul>
<li>The 4-day raw conversation data is contained in <code>plugin_google_activity_recognition_raw.csv</code> and <code>plugin_ios_activity_recognition_raw.csv</code>.</li>
<li>The 4-day raw activity data is contained in <code>plugin_google_activity_recognition_raw.csv</code> and <code>plugin_ios_activity_recognition_raw.csv</code>.</li>
<li>Two episodes locate in the same 30-min segment (<code>Fri 04:01:54</code> and <code>Fri 04:13:52</code>)</li>
<li>One episode for each daily segment (<code>night</code>, <code>morning</code>, <code>afternoon</code> and <code>evening</code>)</li>
<li>Two episodes locate in the same daily segment (<code>Fri 05:03:09</code> and <code>Fri 05:50:36</code>)</li>

5
dev/features/phone-applications-foreground/index.html
View File

@ -1866,6 +1866,10 @@
<td>An array of app categories to be <em>included</em> in the feature extraction computation. The special keyword <code>all</code> represents a category with all the apps from each participant. By default we use the category catalogue pointed by <code>[APPLICATION_CATEGORIES][CATALOGUE_FILE]</code> (see the Sensor parameters description table above)</td>
</tr>
<tr>
<td><code>[CUSTOM_CATEGORIES]</code></td>
<td>An array of collections representing your own app categories. They key of each element is the name of the in-house category and the value is an array of the package names (apps) included in that category.</td>
</tr>
<tr>
<td><code>[MULTIPLE_CATEGORIES]</code></td>
<td>An array of collections representing meta-categories (a group of categories). They key of each element is the name of the <code>meta-category</code> and the value is an array of member app categories. By default we use the category catalogue pointed by <code>[APPLICATION_CATEGORIES][CATALOGUE_FILE]</code> (see the Sensor parameters description table above)</td>
</tr>
@ -1940,6 +1944,7 @@
<p>Features can be computed by app, by apps grouped under a single category (genre) and by multiple categories grouped together (meta-categories). For example, we can get features for <code>Facebook</code> (single app), for <code>Social Network</code> apps (a category including Facebook and other social media apps) or for <code>Social</code> (a meta-category formed by <code>Social Network</code> and <code>Social Media Tools</code> categories).</p>
<p>Apps installed by default like YouTube are considered systems apps on some phones. We do an exact match to exclude apps where &ldquo;genre&rdquo; == <code>EXCLUDED_CATEGORIES</code> or &ldquo;package_name&rdquo; == <code>EXCLUDED_APPS</code>.</p>
<p>We provide three ways of classifying and app within a category (genre): a) by automatically scraping its official category from the Google Play Store, b) by using the catalogue created by Stachl et al. which we provide in RAPIDS (<code>data/external/stachl_application_genre_catalogue.csv</code>), or c) by manually creating a personalized catalogue. You can choose a, b or c by modifying <code>[APPLICATION_GENRES]</code> keys and values (see the Sensor parameters description table above).</p>
<p>We count <code>episodes</code> and <code>events</code> seperatly. Events are single logs, but episodes will span from a start to and end date time and they will be chunked across any overlapping time segments. And we also compute <code>top1global</code> seperatly. <code>top1global</code> of <code>episodes</code> might not be the same as the <code>top1global</code> of <code>events</code>.</p>
<p>The application episodes are calculated using the application foreground and screen unlock episode data. An application episode starts when the application is launched and ends when either, a new application is launched or the screen is locked.</p>
</div>

2
dev/search/search_index.json
View File

File diff suppressed because one or more lines are too long

BIN
dev/sitemap.xml.gz
View File

Binary file not shown.