fieldtrip / website

This contains the content hosted on the FieldTrip website
http://www.fieldtriptoolbox.org
Other
39 stars 104 forks source link

improve consistency of forward and inverse modeling documentation #571

Open robertoostenveld opened 2 years ago

robertoostenveld commented 2 years ago

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 commented 2 years ago

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.,

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 commented 2 years ago
  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 commented 2 years ago
  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 commented 2 years ago

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 commented 2 years ago

agreed that https://www.fieldtriptoolbox.org/tag/sourceanalysis/ should be merged with https://www.fieldtriptoolbox.org/tag/source/

robertoostenveld commented 2 years ago

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