== **DMDX** == 

**Description:** 

DMDX is a free software for experimental control and timing of stimulus display. It is created in the Department of Psychology at the University of Arizona by Jonathan and Ken Forster. The first step about this software is made on May 5 1997. At the begin DMDX was separated in two parts DMTG and DM respectively DMDX is DMTG and DM successor. Also we can tell that DMDX has many updates. DMDX works on Windows operating systems expect Windows 8 and Windows 10, it is waiting for updates. DMDX needs to be set up properly, using associated program TIMEDX and each configuration will be specific to each computer. 
DMDX is a program that can be used to run psychological experiments, to presents lists of stimuli (pictures, text, sounds) that are prepared and specified by you, to collects responses, for example: "Which keys are pressed on the keyboard and how long did it take before they were pressed" and also DMDX saves the RT and correct/error responses in a data file for later analysis.


**URL:** ​

[1] http://www.u.arizona.edu/~kforster/dmdx/dmdx.htm 

[2] http://www.iub.edu/~psyling/resources/dmdx-tutorial_id_2010.pdf 


== **Project Anatomy**==


**Community**

DMDX is a member of the DMASTR family, and represents an extension of the original DOS programs (DM and DMTG) to a Windows 95/98 environment.

**Leadership**

Jonathan Forster 

**Forking**

You can create your own fork of the central repository. First go to github, create an account and make a fork of the DMDX repository. You can change your fork in any way you choose without it affecting the central project. You can also share your fork with others, including the central project.

**Communication**

All users of DMDX are encouraged to subscribe to the list.  If you have a problem, post it, and somebody will answer. First you must sing up. Send a message to list@list.arizona.edu from the address you want to subscribe to the list.Once your subscription is confirmed posts can be made to dmdx@list.arizona.edu. 

**Roadmaps**

N/A

**Releases**

TBD 

For more informations you can see on the folowing page: http://www.u.arizona.edu/~kforster/dmdx/overview.htm#Accuracy of Timing

**Repositories**

The use of git allows people to contribute changes that can easily be incorporated back into the project, while maintaining order and consistency in the code. All changes should be tracked and reversible.

**Packaging**

N/A

**Upstream/downstream**

Only a couple of people have direct write-access to the DMDX repository, but you can get your changes included in upstream by pushing your changes back to your github fork and then submitting a pull request.

**Version Control**

The last Update was on 21 May 2017.

**Trackers**

You can track the changes on the folowing link: http://www.u.arizona.edu/~jforster/dmdx.htm

**Project Evaluation**

The first step of founding DMDX was May 1997. After that DMDX is constantly developed.

== **Fieldtrips**== 


**Github:**

[1] https://github.com/txipi/VisualDMDX 

**Openhub:**

N/A

**Source Forge:**

N/A

== **Evaluation** ==

**Licensing** 

GNU General Public License v3.0

**Language**

!JavaScript

**Activity**

Active

**Number of contributors**

It has many contributors such as: John Allen, Jeff Bowers, Matthew Chung, Matt Davis, Zia Dikman, Mike Ford, Gareth Gaskell,  Michael Johnston, Ralph Mertens, Dennis Norris, Mary Peterson, David Schnyer etc.

**Size**

N/A

**Issue tracker**

It has forum on which you can ask your question.

**New contributor**

On the !GitHub provides a straightforward way for collaborating on a project. 

**Community norms**

You can create a fork of the central DMDX repository. You can also create a local clone of that fork: for small changes(make the changes directly in the master branch, push back to your fork, submit a pull request to the central repository) and for substantial changes (create a branch, when finished run unit tests, when the unit tests pass merge changes back into the master branch, submit a pull request to the central repository).

**User base**

It has its own strong user base.