DMDX Help.


Record Clock On Time Keyword

<RecordClockOnTime [N[,eventname]]>
<rcot [N[,eventname]]>


    MDSP bit 400000 modifier. Reset if N = 0, otherwise set. All MDSP modifiers are both parameters and switches. If N is missing the bit is set and the mode is active. Setting this MDSP bit records the time that the clockon in each item occurred at across items after the subjects RT in the .AZK output. First clockon is deemed time zero all others are from that time.

    This is provided for use with other packages that record data for the entire item file, ERP and FMRI machines in particular.

    The option eventname (case sensitive) is for inter-process synchronization of DMDX with other custom software.  If another process creates an event that matches the eventname then every time DMDX turns the clock on it will signal that event.  The following code snippet demonstrates this by waiting 5 seconds or printing * when signaled by DMDX:

	HANDLE	ev;
	if((ev = CreateEvent(NULL, FALSE, FALSE, "DMDXevent")) == NULL) {
		printf("failed to CreateEvent");
		exit(1);
	}
	while(running) {
		if(WaitForSingleObject(ev, 5000) == WAIT_TIMEOUT)
			printf("-");
		else
			printf("*");
	}
    Note that N must be specified when using eventname, as in <rcot 1,DMDXevent>.

    Note that using <rcot> with <ContinueClockOn> will not store the time the clock is continued from, it will store the time the frame with <cco> in it is presented.

    If you needed access to the item number for a code to send to another machine say that DMDX was executing you could piggy back on the network monitor capabilities and use a local TCP socket to recieve DMDX's runtime diagnostics.  Packets beginning with ESC can be ignored as they are control packets (unless you turned on naming task negation of course then you'd have to respond appropriately to "\33<ntn>text" packets with either "\33<ntnaff>" or "\33<ntnneg>") but the rest are going to be plain text that you can parse the item number out of.

 


DMDX Index.