rTMS
Communication Code for the rhythmic/repetitive TMS protocol
This protocol allows you to trigger trains of TMS pulses, adding the option to choose the distance in ms between the two pulses and the number of pulses within each train. If you’ve read the previous section (dcTMS) most of this information will be redundant, aside from the “SET,nPULS” parameter.
Lines 5-8 initialize the serial communication. Python can use:
As the same as:
It is important to change the USB port (“COM”) name according to your case as explained above.
Then, copy-paste the mandatory signature. Without this the following lines won’t work.
After these mandatory steps, you can declare optional stimulation parameters (e.g., IPI, number of pulses, markers) in any order. In this case, since we’re going to use a spTMS protocol, the only parameter we may be interested in is the voluntary marker duration. This option allows you to place digital markers of a chosen duration (max 9 different lengths) at any moment. This may be useful in case you need to discriminate between different stimuli’s onset (e.g., neural, joy, or fearful faces). Remember that voluntary markers always get delivered through BNC3. Its syntax is:
In this case N is the preset number (between 1 and 9), and X is the marker length. Recalling the three stimuli example, we may want three voluntary markers of different duration (e.g., 3, 5, and 7 ms) ease our analysis, later. We will write then:
For rTMS paradigms it is important to declare the number of pulses constituting each train, triggered simultaneously from BNC1 and BNC2. Its syntax is:
In this case N is the preset number (between 1 and 9), and X is the number of pulses within the train. For example, we may want to test the difference in delivering trains of 4, 5, or 6 pulses prior to the stimulus occurrence. We will write then:
Additionally, in rTMS paradigms it is also important to declare the distance in ms between the two pulses (IPI), delivered from BNC1 and then BNC2. Its syntax is:
In this case N is the preset number (between 1 and 9), and X is the distance between pulses in ms. For example, we may want an 80 ms interval in the first preset (4 pulses), a 100 ms interval for the second one (5 pulses), and a 120 ms interval for the third one (6 pulses). We will write then:
Our last step before calling the pulse command is declaring which TMS protocol we are going to use. We can choose between spTMS, dcTMS, or rTMS. Since we’re using the double pulse one, we will write:
Now that we have declared all of the necessary stimulation parameters, we can finally trigger the TMS device. You can independently trigger each of the declared protocols. These lines must be copy-pasted within your code according to your stimulation and task requirements (es. prior to a certain stimulus onset).
We can also individually call for voluntary markers at any time using letters. Preset 1 (MRK1) is paired with letter “A” – Consequently, preset 2 with “B”, 3 with “C”, 4 with “D”, 5 with “E”, 6 with “F”, 7 with “G”, 8 with “H”, and 9 with “I”. Since we declared three different markers (“MRK1,3”, “MRK2,5”, “MRK3,7”) we can trigger them using the letters “A”, “B”, and “C”.
The command code also includes a line to run in case you may reset any setting and return to the mandatory signature. You can then declare once again the parameter settings. The command is:
Once the task is completed you can definitely close the serial communication between the Silicon Spike device and the experimental computer, thus avoiding any potential bug.
Last updated