DataWarrior User Manual

Using Macros for Workflow Automation

Workflow based cheminformatics tools like Pipeline Pilot or Knime gained quite some popularity, because they allow defining complicated or long task sequences, which can be executed at a later time multiple times by different people on different or frequently updated data.
In DataWarrior a defined sequence of tasks is called macro. In DataWarrior new macros can be created by creating and defining macro tasks one-by-one interactively, by duplicating and customizing an existing macro, or simply by recording normal user interactions. These include creating or changing views, filtering data, calculating properties, retrieving data from databases, opening and saving files, and much more. Basically, any action that can be done interactively can also be defined as macro task. In addition there exist some special macro tasks that cannot be performed interactively.
Most macro related functionality are accessible through the Macro menu, which allows recording, playing, exporting and importing macros. A dedicated macro editor view lets you create new or customize existing macros. Finally, macro files can be opened from the file menu or by double-clicking their icons to immediately run them.

Macro Concepts

In order to efficiently work with macros, one needs to understand a few general concepts:

  • Typically a macro is owned by a DataWarrior document. When this document is saved, the macro is saved as part of the document's .dwar file.
  • When a new macro is created, either manually within the macro editor or by recording a macro, then the macro belongs to that document, whose window was in front during the macro's creation.
  • When a longer macro is recorded it may happen that the window, which owns the macro, is pushed to the background, e.g. when a task creates a new window. In that case user interactions happen in the new front window, but are still added to original macro, which belongs to the background window.
  • If a macro is executed, then every one of its tasks is executed in the front window, even if the macro is owned by another window that is in the background.
  • Macros may be exported into a dedicated .dwam file. Usually, this is done to share the macro with other users or to store it independent of a data file for future use.
  • When a .dwam file icon is double-clicked or the file is opened from DataWarrior's File menu, then the contained macro is executed on the front window's dataset.
  • Macro files, which are located in certain predefined directories, are listed in the Macro menu for direct execution.
  • Macros can call other macros recursively.

  • Recording and Running Macros

    The easy way to create a macro is recording one. To do so, activate that window, which shall host the new macro and select Start Recording... from the Macro menu. A dialog opens to ask for a macro name. After closing that dialog a red message in the bottom right corner of every window indicates that all interactions with DataWarrior are currently recorded as tasks of a new macro until you select Stop Recording from the Macro menu. Once a macro was recorded its name appears in the Run Macro and Export Macro items of the Macro menu.

    A macro is currently being recorded or executed.

    In order to execute a macro select its name from the Macro -> Run Macro menu. Then, the macro's tasks will be sequentially executed in the front-most window, which may change during the execution of the macro, if a task brings another window to the front or if a new window is created. During the execution of the macro a message and a progress bar in the bottom right corner of every window report on the progress of individual tasks. An X button can be pressed anytime to stop a macro's execution immediately (see image above).

    The Macro Editor

    While it is convenient to just record a new macro by naturally interacting with DataWarrior, sometimes it is necessary to slightly adapt a recorded macro or even useful to create a new macro from scratch. Moreover, there are tasks, which cannot be recorded, e.g. for showing a message or waiting for a few seconds. To change an existing macro or to construct a new one from scratch DataWarrior has built-in macro editor view, which can be opened with a right mouse click on any view's title area and selecting New Macro Editor from the popup menu.

    Macro Editor

    The left part of the editor shows all task categories and tasks that are available in DataWarrior. At the top of the right part one may create macros, rename of delete existing macros from the current data file. If the active DataWarrior window contains macros, one may select one for editing. All tasks of the selected macro are then shown below in the order they will be executed. Available tasks can be dragged and dropped from the left into a macro's task list, which causes a new task of this kind to be added or inserted into the currently macro. If the task needs further specification, which most tasks do, then a dialog opens to define the task's details. Any time later one may double click any task of a macro to open the detail dialog again. A right mouse click of a macro task opens a popup menu allowing to rename or remove the task. The task order can be changed by dragging tasks to a different position.

    Note that the dialog for editing a macro task may look and behave slightly different from the dialog to configure the same task for immediate execution on the current window's dataset. When you edit a macro task, DataWarrior cannot know the structure of the data, which the macro will run on. Nor does it know, which views or filters will be available. Therefore, a higher flexibility is needed for specifying a particular data column, a view or a filter. To allow for this higher flexibility dialog items often permit typing in a column name in addition to selecting one from a list of compatible columns.

    Exporting and Importing Macros

    When a new macro is born by either creating it in the macro editor or by recording user interactions, the macro belongs to the DataWarrior document that was in front, when the macro was created. Whenever this document's window is active, its Run Macro menu contains an item for every contained macro, which triggers its execution. This way the initial scope of any new macro is more or less limited to the data file it belongs to. In order to share a macro with a colleague or to make it available to all data files, it needs to be detached, i.e. exported from its original data file. When selecting the macro's name from the Export Macro menu, the macro is written into a dedicated file that can be sent to a colleague, or converted into a global macro by putting into a directory, which is scanned by DataWarrior during launch.
    Likewise, macro files can be imported into any DataWarrior document to quasi marry them with it. This is done by selecting Import Macro... from the Macro menu. Whenever a document with embedded macros is opened, the names of its macros appear in the Run Macro submenu for immediate execution.

    Global and User Macros

    When DataWarrior is launched, it searches some predefined directory paths for macro files, i.e. for files with the extention .dwam. From any found macro file it reads the contained macro's name and adds it to the Run Macro submenu of the Macro menu. Note that a macro name may be different from the name of the file that contains the macro. When any of the Run Macro submenu's items is selected, then the corresponding macro is executed on the active window's dataset. When assembling the macro list DataWarrior searches these paths:

  • The macro folder directly in the DataWarrior installation directory. This is /opt/datawarrior/macro, /Applications/, or C:\Program Files\DataWarrior\macro for Linux, Macintosh or Windows (64-bit), respectively. Any macro files in these directories are visible to all users.
  • A macro folder in a datawarrior folder in the user's home folder. This is /home/<username>/datawarrior/macro and /Users/<username>/datawarrior/macro for Linux and Macintosh, respectively. On Windows the home folder location depends on the version of Windows, the version of Java and other settings. Often it is the user's Desktop folder. Therefore, DataWarrior supports an additional path on Windows: C:\\Users\<username>\AppData\Roaming\DataWarrior\Macro. Any macro files in these directories are visible to one user only.
  • Another option is to define one or more custom macro folders by setting the Java system property macropath when launching DataWarrior as e.g.: -Dmacropath=/home/thomas/datawarrior/macros:/home/thomas/datawarrior/test/macros (on Windows use ';' instead of ':' as separator). On Linux this can be done by updating the launch script /opt/datawarrior/datawarrior. On OSX one needs to change Info.plist in the folder. On Windows this is again less straight forward: One needs to pass the -D option to the executable when that is launched. One option is to create a shortcut and add the option to it. However, this approach only works, if DataWarrior is launched from the shortcut. If you know what you are doing, you may also edit the registry's shell/open/commands for the file extentions "dwar", "dwam", "sdf".

  • Running Macros from the Command Line

    One way of using macros is to launch DataWarrior from the command line or from within a shell script and passing a macro file name as the only parameter. This causes DataWarrior to execute the macro. If the macro's last task is Exit Program, then DataWarrior would close after the work is done letting the shell script continue with whatever is supposed to follow.
    If configured from the macro editor, the Exit Program task allows to select, how open files with unsaved content shall be treated when the program closes. The options are not to save anything, to ask, which windows to save, or to save all Windows with unsaved changes automatically without asking interactive questions. In the latter case DataWarrior handles Windows differently depending on whether they already have an existing file association. If a Window was earlier opened by reading a DataWarrior file or if the Window's content was saved earlier into a DataWarrior file, then changes would be written into that file effectively overwriting the previous content. If, however, there is no file association, because the Window's data was retrieved from a database or e.g. created as a combinatorial library, then DataWarrior would save a new file under a unique name in the user's home directory making sure that no existing file is overwritten.