Hello,
Creating this issue to suggest a small improvement on the database/protocol saving. It would be nice to have the database/protocol file saved more often to reduce the issue in the eventuality of a MATLAB crash.
Here are a few examples I encountered recently while we had an issue with our NAS.
-
If you change protocol and explore it, if MATLAB crashes, then when re-opening Brainstorm, Brainstorm doesn't load the last protocol open, but the one that was open before that. When changing protocol, to be sure that things are saved, one currently needs to close Brainstorm and re-open it. So if MATLAB crash, Brainstorm reopens the correct protocol.
-
If a subject is created, and MATLAB crashes later. Then, when re-opening Brainstor,m the subject is not in the database until a complete reload is done.
I think in both cases, it would be useful to trigger a database save when both action occurs. Additionally, it might be nice to have a 'save' button in the File menu to make sure everything is saved (without the need to close and restart MATLAB)
In general, i think every change in the database should be 'fully' saved and not wait for Brainstorm to be closed, so that if Brainstorm crashes, reopening it should bring back Brainstorm to the state it was before MATLAB was closed without the need for the extra database reload (which can cause some undesired anxiety lol)
Hello,
Creating this issue to suggest a small improvement on the database/protocol saving. It would be nice to have the database/protocol file saved more often to reduce the issue in the eventuality of a MATLAB crash.
Here are a few examples I encountered recently while we had an issue with our NAS.
If you change protocol and explore it, if MATLAB crashes, then when re-opening Brainstorm, Brainstorm doesn't load the last protocol open, but the one that was open before that. When changing protocol, to be sure that things are saved, one currently needs to close Brainstorm and re-open it. So if MATLAB crash, Brainstorm reopens the correct protocol.
If a subject is created, and MATLAB crashes later. Then, when re-opening Brainstor,m the subject is not in the database until a complete reload is done.
I think in both cases, it would be useful to trigger a database save when both action occurs. Additionally, it might be nice to have a 'save' button in the File menu to make sure everything is saved (without the need to close and restart MATLAB)
In general, i think every change in the database should be 'fully' saved and not wait for Brainstorm to be closed, so that if Brainstorm crashes, reopening it should bring back Brainstorm to the state it was before MATLAB was closed without the need for the extra database reload (which can cause some undesired anxiety lol)