Skip to content
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

improve consistency of forward and inverse modeling documentation #571

Open
robertoostenveld opened this issue Jul 8, 2022 · 6 comments
Labels
enhancement New feature or request figure Improve the figures

Comments

@robertoostenveld
Copy link
Member

As discussed with @mcpiastra.

The different pages should better use the same terminology, the same (or similar) figures to explain concepts, and link to each other through tags and explicit links in the "see also" sections.

@mcpiastra
Copy link
Contributor

Hi,

some points. I started working on "Tutorial" pages only.
1.
As discussed together, the naming of the sections here
Screenshot from 2022-07-13 11-09-54
should be more consistent, i.e.,

  • Construct a singleshell heamodel for MEG source analysis
  • Construct a BEM heamodel for EEG source analysis
  • Construct a FEM heamodel for EEG source analysis
  • Construct a sourcemodel for MEG or EEG source analysis
  • Localizing electrodes using a 3D-scanner
  • Reconstruct oscillatory sources in MEG data using a beamformer
  • Reconstruct oscillatory sources in combined MEG/EEG data using a beamformer
  • Reconstruct visual gamma and cortico-muscular coherence
  • Reconstruct event-related fields using minimum-norm estimation
  • Reconstruct event-related activity in combined MEG/EEG data with dipole fitting
  • Reconstruct epileptic spikes (activity?) in MEG data using a kurtosis beamformer
  • Computation of virtual MEG channels in source-space

If I understood correctly, changing the names of the sections above should be done with care because the same name is repeated in several places and there should be consistency.

@mcpiastra
Copy link
Contributor

  1. I will focus now on making the content of each of those subchapters mentioned above more consistent and similar to each other (e.g., same list of content, same figures)

@mcpiastra
Copy link
Contributor

  1. tags should be checked. Here:

https://github.com/fieldtrip/website/tree/master/_data/tag

I can see that there is "source", "sourceanalysis" and "sourcemodel"; "inverse"; "forward"; "headmodel". Are all needed? E.g., "forward" is used only once, "source" and "sourceanalysis" sound the same.

@mcpiastra
Copy link
Contributor

the figures:
img/shared/tutorial/sourcelocalization_background/source_analysis-03.png
https://www.fieldtriptoolbox.org/assets/img/tutorial/headmodel_meg/headmodel-01.png
are re-drawn in the google slide file. If they are good to go, I will replace them.

@robertoostenveld
Copy link
Member Author

@robertoostenveld
Copy link
Member Author

I would equate headmodel to forward and prefer the term headmodel, as that is how we call it in the code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request figure Improve the figures
Development

No branches or pull requests

2 participants