-
Notifications
You must be signed in to change notification settings - Fork 0
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(create) M/EEG landing page on Wiki #12
Comments
We could have separate SOP links for EEG-MEG. Post Maxfilter the artRej pipelines can be similar right? Sure referencing issues in EEG. But other than that can't we have similar pipeline-samples for both? Forward models can be very similar until we move into the forward solution. So we can create forks at those and redirect? |
I think we should make a flowchart similar to mne workflow so it easy to visualise which steps are similar, how one step might depend on a previous, and which steps do not depend on a previous. |
+1 for workflow, but only insofar as it's somehow idiosyncratic to CFIN-ways (like our particular flavour of the cluster). When it comes to the SW we rely on, links can be used to the relevant www-pages. The more I think about this, the more I like it. We could in fact make a little effort to write our pipeline-documentation as graphs using either |
👍 for python graphs :) @cjayb agree. By making our own graph it will be easy to show which processes could be submitted and which is better handled on a local machine. |
New "design", perhaps more EEG-friendly i.e. more general to both M and EEG? What should be on the page? Current version is here.
The text was updated successfully, but these errors were encountered: