Closed dbirman closed 1 month ago
so this means to make new subsets, we add columns to the CSV file, and if we want to add new items to a list (e.g. more emg options) we update the CSV? I'm a little reluctant on this as I think keeping the CSV static will be more robust. I can imagine that we have one list of EMG muscles, but another group has a different list of body parts they want to use, and we then end up with different versions of the csv floating around.
I see that negative for sure. The positive I was thinking about is that it's not very user friendly to generate the subset lists right now since the model.ATTRIBUTE
values aren't visible when you're writing code. When I wrote the EMG list I was basically tabbing back and forth between the CSV and the code file and manually turning the names into the capital + underscore versions that get attached to the model. I believe the tests fail if you make a typo, but this would be robust to that.
2024/09/05 - discussed w/ Saskia, pulling in David to discuss issues around very large CSV files (100k+ rows)
PR adds an option to generate a subset group, previously done with:
By:
and putting a "1" in a new column EMG_MUSCLES in the CSV file in each row that should be included.
We could go one step further and auto-generate subsets for any column that shows up in SCREAM_CASE?