Closed mlp6 closed 3 years ago
Reconsidering the need for this as the Verasonics way of using their Matlab-based setup scripts are to define the parameters w/i the scripts themselves. To stay consistent w/ that workflow, going to table doing this (for now).
Right now, a
par
data structure is defined in AnalyzeAllAcquisitions.m, which mixes parameters with some execution code, which isn't ideal. Would like to migrate to using aprocessing_params.json
type input file to separate the code from the parameters.