This could be more effort than it’s worth, but in the future when people are onboarded with this code it might be confusing that it isn’t grouped in with the gui and the pllr code. I just feel like it fits so cozily in with BrainBehaviorAnalytics. I know it’s Prad’s code so maybe it makes sense to keep it where it is for now, but I wanted to float the idea in case we think the organizational clarity is worth the migration effort. I do think at the very least it might be a good idea to fork it into the org and build on a version aligned with the gui.
This could be more effort than it’s worth, but in the future when people are onboarded with this code it might be confusing that it isn’t grouped in with the gui and the pllr code. I just feel like it fits so cozily in with BrainBehaviorAnalytics. I know it’s Prad’s code so maybe it makes sense to keep it where it is for now, but I wanted to float the idea in case we think the organizational clarity is worth the migration effort. I do think at the very least it might be a good idea to fork it into the org and build on a version aligned with the gui.