This repository contains the protocol for the Mind Trails Movement study, and all the code required to build the protocol from scratch.
- 📁make -- Contains the CSV and Python scripts to "remake" the study surveys and sessions.
- 📁validate -- Contains Python scripts to check if all Json is properly formatted
- 📁src -- Contains the raw files that will be copied to device when a participant enrolls in the study
This protocol can be downloaded in the Digital Trails app using the study code "MTM" on the initial startup screen.
All of the studie's custom content are described by JSON files. To recreate these files:
- Delete the folders in
src/flows/(note: you should only delete the folders). - Run
make/scripts/microdoses.py,make/scripts/surveys.py, andmake/scripts/resources.py. - Copy the folders generated by Step 2. The folders will be in the
make/~out/directory. - Paste the output copied in Step 3 into
src/flows
Follow these steps to make protocol changes availalbe in Digital Trails.
-
Desired protocol changes should be made in the
srcdirectory -
After finishing your changes commit them to this repository
-
Once the desired changes have been committed and pushed to GitHub navigate to Releases
-
On the Releases page there will be a "Draft a New Release" in the top right
-
On the Release draft page: (a) enter a new "tag" to identify the release, (b) give it a title, and (c) click "Publish Release"
-
After publishing it will take about 2 minutes before the protocol will be ready to download in Digital Trails
-
You can monitor the publish process by clicking on Action tab at the top.
-
In the Action tab, the publication process will appear at the top of the workflow list. Once the workflow is green it can be downloaded in Digital Trails.
In addition to releasing a primary protocol (downloaded with MTM study code) it is also possible to release protcol versions. To do this:
-
Create a new Release as described above, but this time be sure to unclick "Set as the latest release"
-
In Digital Trails enter your study code followed by an @ plus your release tag. For example, if your release tag was
1.0-betayou'd enter: -
You can have as many release versions as you want, but only one "latest release". The "latest release" is always the default download.

