Deployed 895b707 to 0.1 with MkDocs 1.1.2 and mike 0.5.5

pull/106/head
github-actions 2020-11-17 22:28:47 +00:00
parent 982a3b9a90
commit 029c8680df
6 changed files with 22 additions and 8 deletions

File diff suppressed because one or more lines are too long

Binary file not shown.

View File

@ -797,12 +797,19 @@
<ol>
<li>Install RAPIDS and make sure your <code>conda</code> environment is active (see <a href="../../setup/installation">Installation</a>)</li>
<li>
<p>For the <a href="../../setup/configuration">Initial Configuration</a> steps do the following and use the example as a guide:</p>
<p>Make the changes listed below for the corresponding <a href="../../setup/configuration">Initial Configuration</a> step (we provide an example of what the relevant sections in your <code>config.yml</code> will look like after you are done)</p>
<div class="admonition info">
<p class="admonition-title">Things to change on each configuration step</p>
<p>1. Setup your database connection credentials in <code>.env</code>. We assume your credentials group is called <code>MY_GROUP</code>.</p>
<p>2. <code>America/New_York</code> should be the default timezone</p>
<p>3. Create a participant file <code>p01.yaml</code> based on one of your participants and add <code>p01</code> to <code>[PIDS]</code> in <code>config.yaml</code></p>
<p>3. Create a participant file <code>p01.yaml</code> based on one of your participants and add <code>p01</code> to <code>[PIDS]</code> in <code>config.yaml</code>. The following would be the content of your <code>p01.yaml</code> participant file:
<div class="highlight"><pre><span></span><code><span class="nt">PHONE</span><span class="p">:</span>
<span class="nt">DEVICE_IDS</span><span class="p">:</span> <span class="p p-Indicator">[</span><span class="nv">aaaaaaaa-1111-bbbb-2222-cccccccccccc</span><span class="p p-Indicator">]</span> <span class="c1"># your participant&#39;s AWARE device id</span>
<span class="nt">PLATFORMS</span><span class="p">:</span> <span class="p p-Indicator">[</span><span class="nv">android</span><span class="p p-Indicator">]</span> <span class="c1"># or ios</span>
<span class="nt">LABEL</span><span class="p">:</span> <span class="l l-Scalar l-Scalar-Plain">MyTestP01</span> <span class="c1"># any string</span>
<span class="nt">START_DATE</span><span class="p">:</span> <span class="l l-Scalar l-Scalar-Plain">2020-01-01</span> <span class="c1"># this can also be empty</span>
<span class="nt">END_DATE</span><span class="p">:</span> <span class="l l-Scalar l-Scalar-Plain">2021-01-01</span> <span class="c1"># this can also be empty</span>
</code></pre></div></p>
<p>4. <code>[DAY_SEGMENTS][TYPE]</code> should be the default <code>PERIODIC</code>. Change <code>[DAY_SEGMENTS][FILE]</code> with the path of a file containing the following lines:
<div class="highlight"><pre><span></span><code>label,start_time,length,repeats_on,repeats_value
daily,00:00:00,23H 59M 59S,every_day,0
@ -843,7 +850,7 @@ DEVICE_DATA:
############## PHONE ###########################################################
################################################################################
....
# ... other irrelevant sections
# Communication call features config, TYPES and FEATURES keys need to match
PHONE_CALLS:

File diff suppressed because one or more lines are too long

Binary file not shown.

View File

@ -797,12 +797,19 @@
<ol>
<li>Install RAPIDS and make sure your <code>conda</code> environment is active (see <a href="../../setup/installation">Installation</a>)</li>
<li>
<p>For the <a href="../../setup/configuration">Initial Configuration</a> steps do the following and use the example as a guide:</p>
<p>Make the changes listed below for the corresponding <a href="../../setup/configuration">Initial Configuration</a> step (we provide an example of what the relevant sections in your <code>config.yml</code> will look like after you are done)</p>
<div class="admonition info">
<p class="admonition-title">Things to change on each configuration step</p>
<p>1. Setup your database connection credentials in <code>.env</code>. We assume your credentials group is called <code>MY_GROUP</code>.</p>
<p>2. <code>America/New_York</code> should be the default timezone</p>
<p>3. Create a participant file <code>p01.yaml</code> based on one of your participants and add <code>p01</code> to <code>[PIDS]</code> in <code>config.yaml</code></p>
<p>3. Create a participant file <code>p01.yaml</code> based on one of your participants and add <code>p01</code> to <code>[PIDS]</code> in <code>config.yaml</code>. The following would be the content of your <code>p01.yaml</code> participant file:
<div class="highlight"><pre><span></span><code><span class="nt">PHONE</span><span class="p">:</span>
<span class="nt">DEVICE_IDS</span><span class="p">:</span> <span class="p p-Indicator">[</span><span class="nv">aaaaaaaa-1111-bbbb-2222-cccccccccccc</span><span class="p p-Indicator">]</span> <span class="c1"># your participant&#39;s AWARE device id</span>
<span class="nt">PLATFORMS</span><span class="p">:</span> <span class="p p-Indicator">[</span><span class="nv">android</span><span class="p p-Indicator">]</span> <span class="c1"># or ios</span>
<span class="nt">LABEL</span><span class="p">:</span> <span class="l l-Scalar l-Scalar-Plain">MyTestP01</span> <span class="c1"># any string</span>
<span class="nt">START_DATE</span><span class="p">:</span> <span class="l l-Scalar l-Scalar-Plain">2020-01-01</span> <span class="c1"># this can also be empty</span>
<span class="nt">END_DATE</span><span class="p">:</span> <span class="l l-Scalar l-Scalar-Plain">2021-01-01</span> <span class="c1"># this can also be empty</span>
</code></pre></div></p>
<p>4. <code>[DAY_SEGMENTS][TYPE]</code> should be the default <code>PERIODIC</code>. Change <code>[DAY_SEGMENTS][FILE]</code> with the path of a file containing the following lines:
<div class="highlight"><pre><span></span><code>label,start_time,length,repeats_on,repeats_value
daily,00:00:00,23H 59M 59S,every_day,0
@ -843,7 +850,7 @@ DEVICE_DATA:
############## PHONE ###########################################################
################################################################################
....
# ... other irrelevant sections
# Communication call features config, TYPES and FEATURES keys need to match
PHONE_CALLS: