visual3d:documentation:reports:scripting_report_templates
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
visual3d:documentation:reports:scripting_report_templates [2024/06/19 12:53] – sgranger | visual3d:documentation:reports:scripting_report_templates [2024/07/17 15:46] (current) – created sgranger | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | {{{{{{{{====== | + | ====== |
- | ===== introduction | + | ===== Scripting Report Templates |
- | report | + | ==== Introduction ==== |
+ | |||
+ | Report | ||
\\ | \\ | ||
- | **note:** using this method requires a prior knowledge of writing pipeline scripts, and it is suggested to complete the pipeline tutorials prior to testing this method.\\ | + | **NOTE:** Using this method requires a prior knowledge of writing pipeline scripts, and it is suggested to complete the pipeline tutorials prior to testing this method.\\ |
- | ===== download ===== | + | ==== Download |
- | **you may download the sample reporting script and sample data files [[https:// | + | **You may download the sample reporting script and sample data files [[https:// |
- | **the entire script may also be seen [[visual3d:documentation:reports:scripting_report_templates_example|here]].** | + | **The entire script may also be seen [[Visual3D:Documentation:Reports:Scripting_Report_Templates_Example|here]].** |
- | ====== using the script ====== | + | ===== Using the Script |
- | ===== naming convention ===== | + | ==== Naming Convention |
- | this example is meant to serve as a starting point for others to work off. the sample script will create a report template for signals following this naming convention: | + | This example is meant to serve as a starting point for others to work off. The sample script will create a report template for signals following this naming convention: |
- | rankleangle | + | RAnkleAngle |
- | as with any scripting language, consistency is key. the following example works because | + | As with any scripting language, consistency is key. The following example works because |
- | the signal names are indicated based on r/l | + | The signal names are indicated based on R/L |
- | the events are plotted based on the side (r/l) and the event hs (or on) | + | The events are plotted based on the side (R/L) and the event HS (or ON) |
- | the graph colors are based on the side (r/l) | + | The graph colors are based on the side (R/L) |
- | if the user would like to use right/left instead of r/l, these parameters will need to be changed throughout the entire script.\\ | + | If the user would like to use Right/Left instead of R/L, these parameters will need to be changed throughout the entire script.\\ |
\\ | \\ | ||
- | the benefit to using a script such as the following, is that the color may be changed by modifying the parameters "color_r" and "color_l" | + | The benefit to using a script such as the following, is that the color may be changed by modifying the parameters "COLOR_R" and "COLOR_L" |
- | ===== example | + | ==== Example |
- | to plot kinematics, the signals | + | To plot kinematics, the signals |
\\ | \\ | ||
- | parameters | + | Parameters |
\\ | \\ | ||
- | the following commands will prompt the user (images of prompt below): | + | The following commands will prompt the user (images of prompt below): |
< | < | ||
- | prompt_for_multiple_pipeline_parameter_values | + | Prompt_For_Multiple_Pipeline_Parameter_Values |
- | /pipeline_parameter_name=page_count+column+row+event_1+event_2 | + | /PIPELINE_PARAMETER_NAME=PAGE_COUNT+COLUMN+ROW+EVENT_1+EVENT_2 |
- | +signal_type+signal_folder+color_r+color_l | + | +SIGNAL_TYPE+SIGNAL_FOLDER+COLOR_R+COLOR_L |
- | +graph_trial_style+graph_mean+graph_stddev | + | +GRAPH_TRIAL_STYLE+GRAPH_MEAN+GRAPH_STDDEV |
- | /datatype=s+s+s+s+s+s+s+s+s+s+s+s | + | /DATATYPE=s+s+s+s+s+s+s+s+s+s+s+s |
- | /default_value=1+1+1+hs+hs+link_model_based+original+990000+109900+null+true+true | + | /DEFAULT_VALUE=1+1+1+HS+HS+LINK_MODEL_BASED+ORIGINAL+990000+109900+NULL+TRUE+TRUE |
; | ; | ||
- | set_pipeline_parameter | + | Set_Pipeline_Parameter |
- | ! list of signals that will be graphed | + | ! List of signals that will be graphed |
- | ! | + | ! |
- | /parameter_name=data_name_list | + | /PARAMETER_NAME=DATA_NAME_LIST |
- | /parameter_value=ankleangle+kneeangle+hipangle | + | /PARAMETER_VALUE=AnkleAngle+KneeAngle+HipAngle |
; | ; | ||
- | set_pipeline_parameter | + | Set_Pipeline_Parameter |
- | ! list of signals that will be graphed | + | ! List of signals that will be graphed |
- | ! | + | ! |
- | /parameter_name=data_name_list | + | /PARAMETER_NAME=DATA_NAME_LIST |
- | /parameter_value=&:&:&:: | + | /PARAMETER_VALUE=&:&:&:: |
- | /multi_pass=true | + | /MULTI_PASS=TRUE |
; | ; | ||
</ | </ | ||
- | the previous commands prompt the user for the graph parameters and the signals to be graphed: | + | The previous commands prompt the user for the graph parameters and the signals to be graphed: |
- | | | + | | |
- | ===== example | + | ==== Example |
- | to plot kinetics, the signals | + | To plot kinetics, the signals |
\\ | \\ | ||
- | parameters | + | Parameters |
\\ | \\ | ||
- | the following commands will prompt the user (images of prompt below): | + | The following commands will prompt the user (images of prompt below): |
< | < | ||
- | prompt_for_multiple_pipeline_parameter_values | + | Prompt_For_Multiple_Pipeline_Parameter_Values |
- | /pipeline_parameter_name=page_count+column+row+event_1+event_2 | + | /PIPELINE_PARAMETER_NAME=PAGE_COUNT+COLUMN+ROW+EVENT_1+EVENT_2 |
- | +signal_type+signal_folder+color_r+color_l | + | +SIGNAL_TYPE+SIGNAL_FOLDER+COLOR_R+COLOR_L |
- | +graph_trial_style+graph_mean+graph_stddev | + | +GRAPH_TRIAL_STYLE+GRAPH_MEAN+GRAPH_STDDEV |
- | /datatype=s+s+s+s+s+s+s+s+s+s+s+s | + | /DATATYPE=s+s+s+s+s+s+s+s+s+s+s+s |
- | /default_value=4+1+1+on+hs+link_model_based+original+990000+109900+null+true+true | + | /DEFAULT_VALUE=4+1+1+ON+HS+LINK_MODEL_BASED+ORIGINAL+990000+109900+NULL+TRUE+TRUE |
; | ; | ||
- | set_pipeline_parameter | + | Set_Pipeline_Parameter |
- | ! list of signals that will be graphed | + | ! List of signals that will be graphed |
- | ! | + | ! |
- | /parameter_name=data_name_list | + | /PARAMETER_NAME=DATA_NAME_LIST |
- | /parameter_value=anklemoment | + | /PARAMETER_VALUE=AnkleMoment |
; | ; | ||
- | set_pipeline_parameter | + | Set_Pipeline_Parameter |
- | ! list of signals that will be graphed | + | ! List of signals that will be graphed |
- | ! | + | ! |
- | /parameter_name=data_name_list | + | /PARAMETER_NAME=DATA_NAME_LIST |
- | /parameter_value=&:&:&:: | + | /PARAMETER_VALUE=&:&:&:: |
- | /multi_pass=true | + | /MULTI_PASS=TRUE |
; | ; | ||
</ | </ | ||
- | the previous commands prompt the user for the graph parameters and the signals to be graphed: | + | The previous commands prompt the user for the graph parameters and the signals to be graphed: |
+ | |||
+ | | {{: | ||
- | | setpipelineparameter_kinetics_graphparameters.png\\ | ||
- | }}}}}}}} |
visual3d/documentation/reports/scripting_report_templates.1718801620.txt.gz · Last modified: 2024/06/19 12:53 by sgranger