-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BrainEntropy: Move to the plugin manager? #389
Comments
Hello, I'll raise the question during our MEM meeting tomorrow morning. Personnally, i won't have time before early april. Édouard |
I copy here the list of other requests I posted on the forum:
|
Hello @ftadel
|
Wouldn't there be Matlab-only alternatives for the optimization functions you need? |
Hello @ftadel
Thanks |
This test doesn't work: it tests for what the license allows, not for what is installed on the computer.
You should replace this test with a much simpler:
It would be great for the future compatibility of this library, thanks. |
Hello @ftadel Indeed, as you note, one may have a license for a toolbox but not have it installed and the test that you propose catches partially this case, and I agree that it should be added. Thanks |
It should be working now, both with the Matlab and the compiled versions of Brainstorm. The work left to do includes only documentation:
|
Hello @ftadel, |
@multifunkim @aliobaibk @YounesZ @klacourse
I added a new solution for managing the packages downloaded by Brainstorm:
It would be great if we could also move the BrainEntropy toolbox to this framework, in order to have everything managed in a centralized way. This will also allow to have automated builds including all the dependencies, to have the BE toolbox compiled with Brainstorm.
Having the MEM included in the compiled distribution of Brainstorm has been requested recently on the forum:
https://neuroimage.usc.edu/forums/t/best-toolbox-in-brainstorm-compiled-version/25898
Who could help me with this task?
Maybe we could organize a short meeting to plan these changes?
The text was updated successfully, but these errors were encountered: