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

Merge branch 'master' of https://github.com/carissalow/rapids

pull/95/head
Meng Li 2020-05-28 17:19:56 -04:00
parent 9c889938fb bbaf649cb8
commit cbd7729457
3 changed files with 8 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/usage/faq.rst
View File

@ -24,19 +24,19 @@ Frequently Asked Questions
**Solution:**
Please make sure the ``MY_GROUP`` in ``config.yaml`` and ``.env`` are the same.
Please make sure the ``MY_GROUP`` in ``config.yaml`` and ``.env`` match.
2. Cannot start mysql for linux via ``brew services start mysql``
2. Cannot start mysql in linux via ``brew services start mysql``
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
use the following code instead:
use the following command instead:
``mysql.server start``
3. Every time I run ``snakemake -R download_dataset`` all rules are executed
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
This is expected behavior. The advantage of using ``snakemake`` under the hood is that every time a file containing data is modified every rule that depends on that file will be re-executed to update their results. In this case, since ``download_dataset`` updates all the raw data, every single rule that depends on those raw files will be executed.
This is expected behavior. The advantage of using ``snakemake`` under the hood is that every time a file containing data is modified every rule that depends on that file will be re-executed to update their results. In this case, since ``download_dataset`` updates all the raw data, and you are forcing the rule with the flag ``-R`` every single rule that depends on those raw files will be executed.
4. Got an error like ``Table XXX doesn't exist`` while running the download_dataset rule.
4. Got an error ``Table XXX doesn't exist`` while running the download_dataset rule.
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
::
@ -46,4 +46,4 @@ This is expected behavior. The advantage of using ``snakemake`` under the hood i
Execution halted
**Solution:**
Please make sure your database do have table with the same name of SENSORS list in config.yaml file.
Please make sure the sensors listed in SENSORS in ``config.yaml`` match your database tables.

2
docs/usage/installation.rst
View File

@ -138,7 +138,7 @@ Once RAPIDS is installed, follow these steps to start processing mobile data.
#. Configure the sensors to process:
- The variable ``SENSORS`` in the ``config.yaml`` file_ should match existent sensor tables in your Aware database (See :ref:`rapids-structure` for more information). Each sensor in this list will be processed in RAPIDS.
- See :ref:`Minimal Working Example<minimal-working-example>`. The variable ``SENSORS`` in the ``config.yaml`` file_ should match existent sensor tables in your Aware database (See :ref:`rapids-structure` for more information). Each sensor in this list will be processed in RAPIDS.
.. note::

1
docs/usage/quick_rule.rst
View File

@ -1,3 +1,4 @@
.. _minimal-working-example:
Minimal Working Example
=======================