Announcing the new Datavyu v1.3.6 with enhanced features and transcription support!

Hello!

We're working on a script, where if the argument in one variable (e.g. numvocs) is equal to 1, it generates a cell in another variable matrix with the onsets and offsets generated for free. We are able to make that script.

However, there are instances in the study, where the variable 'numvocs' can equal anywhere from 2 to 15. We want the script to generate cells that match the number 'numvocs', but we are unsure how to intentionally loop the script.

Does anyone have any pointers for how to accomplish this?

Thanks!

asked 11 Jun '13, 15:05

jducz's gravatar image

jducz
81558
accept rate: 0%


I'm not sure if I'm quite following exactly what you're asking, but are wondering how to generate a cell in another column when <numvocs> is 1 or higher? Or do you want to do something different in the new column depending on what the value of <numvocs> is?

Maybe you could rephrase the question?

permanent link

answered 11 Jun '13, 16:58

KCSoska's gravatar image

KCSoska ♦
2363
accept rate: 17%

Hey Kasey,

Sorry about that. Basically, the individual is coding in one column the number of vocalizations that occur during the trial with a number (1 - infinity). For every time there's a vocalization, they want a cell created in a different column that corresponds with the number of voce (e.g. if there's one voc, generate one cell. If there are 2 vocs, generate 2 cells and so on).

Does that help? Let me know.

permanent link

answered 13 Jun '13, 16:15

jducz's gravatar image

jducz
81558
accept rate: 0%

It is theoretically possible to do something like what you're asking. However, in doing so, I'm not sure where the onset and offset of the 2nd, 3rd, 4th, etc vocs would be. I suppose they could all be set to one time and then the coder could manually adjust those times. But this would be a lot of extra work for the coder.

My suggestion for the best way to handle this is to actually change how the coding is being done. If the coder is watching/listening through and counting the number of vocalizations during some part of the video anyway, they could just as easily be tagging the onsets (and offsets) as well. Rather than first counting up the vocs and then later going back and finding the onsets (and coding something about the vocs), all of that could be done in one pass.

If the coder is coding something else entirely (manual activity or facial expression) and is being asked to count vocs at the same time, that entire coding pass is slowed down. From my experience coding vocalizations, they are coded most accurately and efficiently if they are the sole focus of the coder's attention. You could build off of a previous code (trials or epochs of another behavior) to guide the voc coder; but I definitely just suggest sticking to one pass for vocs (unless you want to have someone go back to each voc and code whether something else was happening during that voc time).

permanent link

answered 14 Jun '13, 10:07

KCSoska's gravatar image

KCSoska ♦
2363
accept rate: 17%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×7
×1

question asked: 11 Jun '13, 15:05

question was seen: 3,172 times

last updated: 14 Jun '13, 10:07

powered by OSQA