question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Question: parametric design encoded with trial_type and amplitude in _events.tsv -- howto prescribe?

See original GitHub issue

We are digging but decided to ask just ask, if we have _events files with onset, duration, trial_type, and amplitude where trial_type is a categorical variable, how should 1st level design be prescribed?

background

Our main confusion is the early on separation of all those additional columns into separate variables which then share only the onset and duration. But in our case, we will have more than a single event for the same onset with different categorical label and having different amplitudes. So we wonder how they would get married again without being mixed up. Example (using spaces here instead of tabs):

onset duration trial_type amplitude
0        0.1         type1       0.2
1        0.1         type2       0.3
0        0.1         type3       0.4
...

so it is important to have later on trial_type.type1 event with amplitude 0.2 and trial_type.type3 event with amplitude 0.4 both happening at onset 0. With separation of the “variables” (now it would be trial_type and amplitude_ … yet to whine about that) it is not clear how to meld them back.

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:8 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
tyarkonicommented, Jan 24, 2019

You would do this via transformations. So, for example, if you want a separate regressor for each trial_type value, but with amplitude specified by amplitude, you can use the Split transformation (i.e., split amplitude by trial_type). There are various other transformations you can look at that collectively should allow you to do almost anything you need to (well, within reason—we’re still following the 80/20 rule).

0reactions
adswacommented, Feb 10, 2019

Thx, @adelavega, I’ll keep it in mind!

Read more comments on GitHub >

github_iconTop Results From Across the Web

Task events - Brain Imaging Data Structure v1.8.0
Task events. The purpose of this file is to describe timing and other properties of events recorded during a run. Events are, for...
Read more >
basic steps required: Topics by Science.gov
The sample identified for the survey shall have a probability-based design such that estimates... 23 Highways 1 2010-04-01 2010-04-01 false Basic design ......
Read more >
Generate an events.tsv file for the NeuroSpin localizer task
Create a BIDS-compatible events.tsv file from onset/trial-type information. The protocol described is the so-called “ARCHI Standard” functional localizer task.
Read more >
DISSERTATION - Refubium
hardware problem: The parallel port, the previous gold standard for sending event markers, is slowly disappearing from commercially available computers.
Read more >
wedge flange clamp: Topics by WorldWideScience.org
1 - Nature of the physical problem solved: Flange design for helium circuits. ... to maintain the clamp-pipe stiffness desired during a seismic...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found