Replies: 1 comment 2 replies
|
Hi @lpyjt13, Thanks for the post. I am unclear where the FOV came from? A. did charm finished correctly? On our end, it works well. When setting up your ROI in the optimizer, please make sure that your definition is within the coordinates of the model. Regarding the report, should be fixed soon. We will release a new version with fixed reporting within the week. In the meantime, do not worry about the report, the flex-search automatically creates files for easy integration with the simulator. So you can view those regarding the electrode naming and coordinates. You can also pipe those to the simulator. Thanks, |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi,
I have had some issues using the MNI152 model for flex search and simulations. The first issue I encountered was this "ERROR! FOV=282.000 > 256" when preprocessing. So I used my own MNI template that had an acceptable FOV. After preprocessing, I ran flexsearch for my ROI, with the optional simulations and EEG mapping, however, the reports failed to generate any EEG mapping or did it output an optimized electrode configuration.
Is there anything I can do to fix these errors, especially the visualisation of the flex search?
Many thanks.
All reactions