DMDX Help.


Files Generated.

    There are several files that DMDX generates (besides regular output files with the extensions .DTP .AZK and .ZIL), they are located either in the directory the item files are in or in /Program Files/DMDX or as a last resort as of version 4.2.1.0 of DMDX in the system or user's temporary directory (the %temp% directory in a batch file) if the item file directory is read only (or otherwise incapable of being written to):

rtfparsed.itm
   
This file is generated as the .RTF item file is parsed, it is the actual item file that the scramble routines read.   If an .RTF file wasn't used for input (a feature that I don't think currently works) and instead a pure ascii file was then this file would not be generated and scramble would use the pure ascii file instead.

scrambled.itm
    This file is generated as the item file is scrambled, it is the actual item file that the display routines read.   If an scrambling was not used then this file would not be generated and the display routines would use whatever came from the .RTF parser instead.

job1.zil
    The temporary output file for .AZK and .ZIL output types -- used by the user only in the case of a failure or an accidental abort.  If you wanted to try and recreate or save a subject's data from one these because you either didn't save it or it was otherwise aborted then you'd have to paste in the right sort of headers into each file before any of the usual filters will read them (they're all text files so use whatever you like to edit text files, NotePad and so on all work, just preserve the right file extensions). So say you've got this for a job1.zil:
 
!  DMDX is running in auto mode (automatically determined raster sync)
!  D3D Video Mode 1920,1080,24,59
!  Item File <D:\dx5\test\ken\WSE1.rtf>
    99     99.00
    99     99.00
    99     99.00
    99     99.00
    21     21.00
    22     22.00
**********************************************************************
ABORTED
**********************************************************************
 
You'd want to cut the aborted message out and paste headers into it so it becomes something like the following (note that it begins with a blank line, some of the filters DMDX has can get pretty persnickety about exact formatting):
 

Subjects incorporated to date: 001
Data file started on machine WIN7LAPTOP

**********************************************************************
Subject 1, 02/10/2016 09:29:28 on WIN7LAPTOP, refresh 16.95ms
  Item       RT
!  DMDX is running in auto mode (automatically determined raster sync)
!  D3D Video Mode 1920,1080,24,59
!  Item File <D:\dx5\test\ken\WSE1.rtf>
    99     99.00
    99     99.00
    99     99.00
    99     99.00
    21     21.00
    22     22.00

And of course you'd want to rename the result to experiment.azk instead of job1.zil...
 
diagnostics.txt

    The contents of the DMDX run dialog.   This is generated as DMDX runs so if there is a catastrophic crash you have some track record of what caused it.   Also, if the .DTP output file type is used this is your only track record of frames displayed late (other AZK and ZIL ASCII output files have the errors written to them).   If the TimeDX / Advanced / Task Priorities / Cumulative Diagnotics.txt check box has been checked this file will not be overwritten with each new run of DMDX and will need to be pruned manually.  As of version 6.1.2.13 the diagnostics can actually be a UTF-8 text file if the Unicode option is in effect.  While the file doesn't start with a UTF-8 BOM most editors these days detect and display UTF-8 automatically, if yours does not you may have to specify the file's format as being UTF-8 or try using the main run dialog's copy button as that pastes UTF-16 (what Windows considers to be Unicode) onto the clip board so your editor may do better with that.

    diagnostics.txt used to be created in the folder that DMDX.EXE lives in, however on a lot of systems these days that's not writeable unless you're running as an administrator so DMDX will ask Windows for the temporary files directory.  In days gone by this might have been C:\windows\temp or any one of a wide range of other possible locations, under Windows 10 every user has their own temporary directory C:\Users\UserName\AppData\Local\Temp.  These days it's easier to use the Copy button on the DMDX run dialog to copy the diagnostics onto the clipboard, of course if you have more than 8000 or so lines of diagnostics you will need the diagnostics.txt file as the run doalog list box only contains the last 8000 or so lines of it.

dmdxpass.txt
    Only generated by PASSPOINT versions of DMDX.   This file contains any amount of diagnostic information generated as DMDX runs depending on how many types of passpoints have been enabled (currently there are 20 categories of passpoints).  



DMDX Index.