Standard analysis design steps: Difference between revisions

From MEG Core
Jump to navigation Jump to search
Content added Content deleted
(Created page with "UNDER CONSTRUCTION =Create a github page of the project= github.com ==Describe the data acquisition task by task== Auditory M100 task: Tone burst auditory stimuli were delivered bilaterally to the subject using the .... Somatosensory task: Pneumatic stimulation was performed on the index finger at a rate of approximately 2 times per second with a jitter of 20 ms ... ==For each task describe the auxilliary channels:== UADC001 was used for left hand patient response...")
 
No edit summary
 
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
UNDER CONSTRUCTION
UNDER CONSTRUCTION <br>

Below are some general guidelines that help you analyze your data<br>
Thinking about this early on, is extremely helpful as it can prevent you from acquired a lot of data without the required inputs. Some things can not be corrected after the fact<br>



=Create a github page of the project=
=Create a github page of the project=
github.com
Sign up for a github account: github.com <br>
Create a github page of the project - this page can initially be a private repository if you prefer. Try to give it a reasonably focused name and NOT just Data_Analysis. This type of setup is often required for publication and can be very helpful in the understanding of the study for reproducibility. This excercise is very important in thinking about your end goal - otherwise your data analysis can become a wandering mess. Below are some things that are very helpful to put on a data analysis repository.
==Describe the data acquisition task by task==
==Describe the data acquisition task by task==
Auditory M100 task:
Auditory M100 task:
Line 11: Line 16:


==For each task describe the auxilliary channels:==
==For each task describe the auxilliary channels:==
UADC001 was used for left hand patient responses
UADC001 was used for left hand patient responses
UADC002 was used for right hand patient responses
UADC002 was used for right hand patient responses
UADC016 was used for the projector channel to correct for timing delays
UADC016 was used for the projector channel to correct for timing delays
UPPT001 codes the stimuli values

===Describe what each PPT value codes===
2: congruent word stimuli
4: incongruent word stimuli
6: distractor words
8: high noise condition
....


==If your logfile incorporates special data that is not in your meg dataset - list these entries==
==If your logfile incorporates special data that is not in your meg dataset - list these entries==
The logfile codes out ...


==If there is external data that is collected - describe how this will be incorporated with the data==
==If there is external data that is collected - describe how this will be incorporated with the data==
External camera data was used to judge facial expressions. Timing triggers were sent to the
External camera data was used to judge facial expressions. Timing triggers were sent to the


==Describe Your Hypothesis About The Results==
We expect to see activation in the left dorsolateral prefrontal area <br>
Timing - Prior literature has shown that <br>

=Develop code to write the triggers to your MEG dataset=
Python Dataframe Based:
examples: https://github.com/nih-megcore/hv_proc/tree/main/hv_proc/Process_scripts
requires nih2mne: https://github.com/nih-megcore/nih_to_mne.git
Commandline Based:
requires pyctf: https://github.com/nih-megcore/pyctf OR https://github.com/nih-megcore/pyctf-lite)



==Run the

Latest revision as of 10:05, 12 December 2024

UNDER CONSTRUCTION

Below are some general guidelines that help you analyze your data
Thinking about this early on, is extremely helpful as it can prevent you from acquired a lot of data without the required inputs. Some things can not be corrected after the fact


Create a github page of the project

Sign up for a github account: github.com
Create a github page of the project - this page can initially be a private repository if you prefer. Try to give it a reasonably focused name and NOT just Data_Analysis. This type of setup is often required for publication and can be very helpful in the understanding of the study for reproducibility. This excercise is very important in thinking about your end goal - otherwise your data analysis can become a wandering mess. Below are some things that are very helpful to put on a data analysis repository.

Describe the data acquisition task by task

Auditory M100 task:

 Tone burst auditory stimuli were delivered bilaterally to the subject using the ....

Somatosensory task:

 Pneumatic stimulation was performed on the index finger at a rate of approximately 2 times per second with a jitter of 20 ms ...

For each task describe the auxilliary channels:

UADC001 was used for left hand patient responses
UADC002 was used for right hand patient responses
UADC016 was used for the projector channel to correct for timing delays
UPPT001 codes the stimuli values

Describe what each PPT value codes

2: congruent word stimuli
4: incongruent word stimuli
6: distractor words
8: high noise condition
....

If your logfile incorporates special data that is not in your meg dataset - list these entries

The logfile codes out ...

If there is external data that is collected - describe how this will be incorporated with the data

External camera data was used to judge facial expressions. Timing triggers were sent to the


Describe Your Hypothesis About The Results

We expect to see activation in the left dorsolateral prefrontal area
Timing - Prior literature has shown that

Develop code to write the triggers to your MEG dataset

Python Dataframe Based:

examples: https://github.com/nih-megcore/hv_proc/tree/main/hv_proc/Process_scripts 
requires nih2mne: https://github.com/nih-megcore/nih_to_mne.git 

Commandline Based:

requires pyctf: https://github.com/nih-megcore/pyctf OR https://github.com/nih-megcore/pyctf-lite)


==Run the