The "ambiguously referenced component" error + grating presentation problem

Support
1

[From Ha]

The “ambiguously referenced component” error has been solved — the reason of the error was that there was a duplicated name both in timer and variable.

The following code produces the error since it uses “ignore_timer” in timer name and variable name:

<action type="start_timer" tag="Start Timer" timer="ignore_timer" timebase="" duration="ignore_timer"></action>

If I change the upper code into the following one, the error disappears (woot! woot!):

<action type="start_timer" tag="Start Timer" timer="ignore_timer" timebase="" duration="ignore_time" duration_units="us"></action>

I, however, still have another issue in presenting gratings. The attached xml has a protocol “RF Mapping” which used to produce 4 differently oriented gratings in 5x5 different positions. If I run the protocol in the nightly build, I don’t see any gratings. (FYI, the two xml files are identical except RF_Mapping_02 uses ITC18 and RF_Mapping_02_FE-simple uses Fake Money.)

It would be great if you could figure out the grating problem.

Thanks a lot!

Ha

2

Attachments:

3

[From Ha]

And plus, the RF_Mapping_02.xml does crash MWServer when quitting and when closing the experiment xml file (through MWClient).

Thanks!

Ha

4

Hi Ha,

It would be great if you could figure out the grating problem.

The drifting grating is a dynamic stimulus. In order for it to display, it has to be playing. You start it playing with a play_dynamic_stimulus action and stop it with stop_dynamic_stimulus. I’ve attached a simple experiment that demonstrates how to display your grating.

In the past, if you queued the drifting grating without playing it, it would draw its first frame, which is presumably why your code used to work. This changed a while ago (over the summer, I think); now, if the grating isn’t playing, it doesn’t display at all.

And plus, the RF_Mapping_02.xml does crash MWServer when quitting and when closing the experiment xml file (through MWClient).

It crashes on my machine, too, presumably due to a bug in the ITC-18 plugin. I’ll investigate.

Thanks,
Chris

5

Attachment: grating_demo.xml (2.62 KB)

6

Thanks, Chris! play_dynamic_stimulus and stop_dynamic_stimulus solved the problem, and now the protocol runs well in the newest version. Thanks a lot!

7

Hi Ha,

I opened a ticket about making the “ambiguously referenced component” message more helpful.

Also, I found and fixed the ITC-18 plugin bug that caused MWServer to crash when closing your experiment. The fix will be in tonight’s nightly build.

Chris