NIH MEG Short Course 2018: Difference between revisions
Jump to navigation
Jump to search
Content added Content deleted
Line 37: | Line 37: | ||
=====Course Material===== |
=====Course Material===== |
||
; Singularity container running CentOS 6.9 with the CTF DataEditor tool and SAMsrc MEG tools |
|||
: [https://megcore.nih.gov/MEG/megcore.img Singularity container megcore.img download] |
|||
: {| width=70% style="border: 1px solid black;" |
|||
|<u>Usage</u>: singularity shell --bind /data:/mnt/data megcore.img |
|||
|- |
|||
| where the ''/data'' file system holds your CTF data set and mounts under /mnt/data inside the container |
|||
|- |
|||
| (your /home directory and the /tmp file systems are automatically visible inside the container) |
|||
|} |
|||
---- |
Revision as of 06:53, 20 July 2018
MEG Short Course Agenda:
Monday, August 6th
Building 10 FAES Classroom 3: B1C207
12:30 – 1:10 pm | MEG: The Basics Fred Carver |
1:10 – 1:50 pm | Introduction to Source Localization Tom Holroyd |
1:50 – 2:00 pm | Break |
2:00 – 2:40 pm | Instrumentation and Hardware Stephen Robinson |
2:40 – 3:20 pm | Applications: What can I do with MEG? Allison Nugent |
3:20 – 3:30 pm | Final Questions |
Tuesday, August 7th
Building 10 FAES Classroom 3: B1C207
12:30 – 12:50 pm | Data Editor and command line Preprocessing Allison Nugent |
12:50 – 1:30 pm | Placing fiducials, headmodel creation Allison Nugent |
1:30 – 1:50 pm | The building blocks of SAM: SAMcov and SAMwts Tom Holroyd |
1:50 – 2:00 pm | Break |
2:00 – 2:30 pm | Voxel-wise evoked fields: SAMersc Tom Holroyd |
2:30 – 3:00 pm | Induced power: SAM_3dc Fred Carver |
3:00 – 3:30 pm | Advanced (and potentially dangerous) topics Allison Nugent |
Course Material
- Singularity container running CentOS 6.9 with the CTF DataEditor tool and SAMsrc MEG tools
- Singularity container megcore.img download
Usage: singularity shell --bind /data:/mnt/data megcore.img where the /data file system holds your CTF data set and mounts under /mnt/data inside the container (your /home directory and the /tmp file systems are automatically visible inside the container)