search

ResearchOS / Biomech-Analysis-Platform-MATLAB

A GUI-based operating system framework to facilitate biomechanical data analysis. This platform attempts to manage the non-scientific part of coding without restricting the direction or method of scientific analysis.
MIT License
4 stars 0 forks source link

Propagate changes to all affected variables. #68

Closed mtillman14 closed 1 year ago

mtillman14 commented 2 years ago

Based off of #17. When changing a variable at all, if any other variables depend on it then I should prompt the user whether they want to propagate these changes. If they select not to at that time, then I should index which variables have not had changes propagated from their changed inputs for propagation at a later date.

When the user decides to propagate, the first question is did they change the analysis code itself (e.g. the specific numbered function) or just the set of input arguments used to generate an output argument.

  1. If they changed the analysis code, then other analyses within the project and even any other projects that use the same function and number will likely also need to have changes propagated to them.
  2. If they only changed the set of input arguments, then only functions that directly use the output argument(s) need to be propagated to. This will most likely be within the same analysis, but can also be in other analyses or projects.
  3. What if they change the output arguments? How do I propagate changes/what changes even should be propagated? Unclear.
mtillman14 commented 1 year ago

Closed because #147 is closed.