search

dr-consulting / ibi_VizEdit

Programming Components for Modeling & Editing Heart Rate Data
0 stars 3 forks source link

Users should be able to pre-assign directoy and file information inside an active R console, before GUI is launched #67

Open matgbar opened 5 years ago

matgbar commented 5 years ago

SCENARIO: ALEX or LOGAN want to analyze a set of reliability codes scored using a defined coding scheme and the relevant data are stored in a filesystem accessible via an active R console

GIVEN: ALEX or LOGAN have a properly formatted set of coding and code scheme data sets and have successfully installed IBI_VizEdit

AND: They have stored both the target behavioral codes data set and the coding scheme definition file in the same directory

WHEN: They run...

IBI_VizEdit::run_app(
dir = "~/path/to/some/folder", 
ppg_file = "raw_ppg_filename", 
ibi_file = "raw_ibi_filename",
timing_file = "condition_timing_filename" 
)

THEN: The app should initiate with this information pre-populated

AND: The function should contain built-in logic that opens a version of IBI_VizEdit for use with raw PPG files vs raw IBI files depending on what sort of data ALEX or LOGAN want to edit.

AND: The function should also contain built-in logic that opens a version of IBI_VizEdit that works with single condition files (i.e., there are not multiple different conditions that can/should be used to break up the heart rate file).

AND WHEN: They leave any argument in the run_app() function empty

THEN: Those fields will not be pre-populated and ALEX or LOGAN can use the defualt GUI to specify the relevant information