MTDATA – Phase Diagram Software from the National Physical Laboratory







Training and Support 




Other Services 





Frequently asked questions

Please click on a question to reveal the accompanying help text. Please note that this page is Javascript-enabled, so you may need to allow Javascript in your browser to view this page correctly. If you are looking for a particular question by searching the page, it may help you to reveal all the questions, or all the answers, on the page first: please click the appropriate link at the bottom of the table of contents.

Table of Contents

Compatibility and Versions Queries

  • What is the current version of MTDATA?

    The current version of MTDATA is version 5.10. All versions of MTDATA show their version numbers in the Window Title Bar. You can also find extra information about the version of MTDATA by selecting "About" from the help menu in any of the GUIs.

  • What are the system requirements for using MTDATA?

    Any modern PC should be able to run MTDATA. There are natively-running versions available for Windows (GUI and command-line) and UNIX (command-line only at time of writing). MTDATA should be able to run on any machine that is capable of running Windows 95 or better - the only effect of lower specifications will be longer calculation times.

  • Does MTDATA work on Windows

    Yes! MTDATA has been tested on all recent versions of the Windows Operating System, and will work with older versions too. So whether you are still using a very old Windows 95, or a modern version such as Windows 7, MTDATA should still work well. At NPL we run MTDATA ourselves in Windows XP, so that is the system it is currently optimised for.

  • Does MTDATA work on Mac OS X?

    Yes, but not natively. For the typical user, one possibility to consider should be virtualisation - consider looking into VirtualBox, or VMWare Fusion - or else one of the wine ports for Mac - for example Crossover. If you are serious about wanting to get it running natively on a Mac, please get in touch.

  • Does MTDATA work on Mac OS classic (v9 and earlier)?

    Good question. We have not tested MTDATA on these systems, but we recommend that you consider (as above) your options for virtualising. You can always download the free MTDATA evaluation to take it for a spin - and if you get anywhere we would love to hear from you!

  • Does MTDATA work on Linux (Unix-based) systems?

    Yes! We have a native Unix version available - though as it stands there is no GUI, it is command-line only. We are looking into the possibility of developing a GUI for the UNIX version of MTDATA, so if this would be helpful to you, please do get in touch and let us know. If having a GUI is an immediate requirement, do consider using our Windows version under virtualisation, or under wine.

  • Is there a portable / web-accessible version of MTDATA?

    Not at this time, however if this would be something you find useful, do get in touch and let us know as we have been considering this.

  • Is there a high precision version of MTDATA?

    Yes, although it is not included as standard in the normal distribution of MTDATA, as calculation times are much larger due to the improved accuracy demanded of it. However, if using this product would be helpful to you or your company, please get in contact with us.

Running MTDATA

  • How do I download MTDATA?

    Please fill out our online form and you will be directed to the download page for the MTDATA evaluation copy. The form simply allows us to keep track of how many people are downloading MTDATA, where it is being used, and allows us to contact you about your download if necessary - all information provided is subject to NPL's Privacy Policy. The evaluation version does not expire, although it is limited in functionality, and has access to demonstration data only - please see the question below "What is the difference between the evaluation version of MTDATA and the full version?" for more details.

    If you are a licence-holder, you can download a copy of MTDATA from here.

  • How do I install MTDATA?

    Please ensure you have downloaded a copy of MTDATA from our site. Then simply proceed to run the installer from the location it was downloaded to.

    Please note that if MTDATA is to be used by users who do not have administrator privileges on the machine, then you may need to install MTDATA to a folder where they will have write-access, or, as an administrator, change the file permissions of the folder to give them write-access (do this by first right-clicking on the MTDATA folder, choose "Properties", then the "Security" tab. Then ensure that either the group "Users" or the relevant user from the top list is given "Full Control" by checking the relevant box and clicking "Apply").

    There may possibly be more up-to-date versions of databases supplied as part of an MTDATA setup installation package. You can check this by looking at the MTDATA download page from which you can also download and install more recent versions.

  • How do I activate MTDATA?

    The evaluation version of MTDATA no longer expires after 30 days, however its functionality is limited, and has access to trial databases only. To gain full access to MTDATA or to use any of the full databases you should obtain a full licence. Please contact us for more information. If you already have a licence to use MTDATA you will need to activate it for use on your computer by sending us your computer id in a file "mtinfo.txt" created by MTDATA (Tools menu, and select "Show Permit Information" in WinMT).

  • I receive a permit error code when attempting to run MTDATA. What does it mean?

    There are four common permit codes returned by MTDATA to indicate that the permit should be updated.


    indicates that the computer is not registered in the permit



    indicates that the version of MTDATA has not been authorised



    indicates that the permit has expired



    indicates that the user (i.e. login name) has not been registered

    If you feel that you have a valid permit it may be that you have stored it in the wrong folder and that MTDATA is picking up an old permit file: please check that your latest permit file is in the MTDATA licence sub-folder, and that all previous licences have been removed from the MTDATA file system altogether. Please contact us if you still have any problems and we will do our best to help.

  • Access to MTDATA seems to have expired. How do I update my permit?

    Please contact us. If you have a permanent licence to use MTDATA you will be sent be new permit by return. If your licence is annual you should already have been invoiced for the extra year's licence fee.

  • MTDATA no longer seems to work. Help?

    Firstly please check that another version of MTDATA is not already running. If it is please close this down either from within the program, or, if necessary, by using the Windows Task Manager. If there is still a problem check that other applications run as normal - if they do not then it is likely your problem lies elsewhere and we will be unable to help you directly. Next try restarting your computer, and closing all other applications that may be running when you try to run MTDATA. Also check whether anything you have changed recently on your system has affected any MTDATA files - if there is any chance something has, you can try reinstalling MTDATA to see if that fixes the problem. However if you do, please ensure you backup all your files before reinstalling - we cannot claim liability for loss of data brought on by reinstallation. If everything else works as expected and you still can't get MTDATA to work, or would just like to talk to a friendly helpful person, please contact Hugh Davies and provide details about any error message(s) that appear - hopefully he will be able to help you further.

  • I would like to / have moved MTDATA from my current computer. What do I need to do?

    Please contact us. If you have support in using MTDATA we will normally be happy to provide you with a new permit for using MTDATA on your new computer.

  • MTDATA is running slowly, is there any way to speed it up?

    If you are using WinMT, please consider using the command-line versions. Due to limitations in the application compilation process, WinMT seems to be limited in speed to around the level of a 1GHz processor, and is unable to make use of hardware beyond this. The command-line versions of MTDATA and MTDATA Studio and Lanchpad currently have no such limitations, and have been known to calculate as much as five times faster than the equivalent calculations performed in WinMT.

    If you are using the command-line interface within WinMT, please bear in mind that it is subject to the same limitations as the rest of WinMT, and that using a native command-line version will increase your calculation speeds significantly.

MTDATA First Steps

  • First time using MTDATA. Anything I should know?

    If this is your first time you are using MTDATA, you may find the built-in help menus helpful. There is a "Getting Started" article in the help files, with a direct link from the "Help" menu in WinMT. The standard keyboard shortcut of "F1" should bring up context sensitive help in many areas of the GUI applications, or you can browse the entire help file by choosing "Contents" from the "Help" menu in WinMT. Further information about using Graphucal User Interface of WinMT can be found on the appropriate part of the MTDATA website. Full information about the command line interface is also available. The installation and demonstration instructions (alternative link) also have a few example calculations you can perform in order to get you started with the application. Finally please also read the answer to the question "How do I use MTDATA?" below for links to further information.

  • What is the difference between the evaluation version of MTDATA and the full version?

    The MTDATA evaluation version no longer expires after 30 days, so the application is no longer time limited as it used to be.

    However, functionality in the MTDATA evaluation version is limited, for example it supports up to three components only in your system, with a total of 22 phases, containing up to 27 species in total. In contrast a standard licenced version of MTDATA has limits respectively set at 30, 500 and 1000. Specialised versions of MTDATA with larger limits may be available on request.

    As an evaluation user you have access to trial databases only, which are updated only infrequently, and have relatively limited ranges of systems. Licenced MTDATA users, however, can buy access to a wide range of databases, all maintained and updated regularly by us.

    Finally, as an evaluation user, you have no direct support from us. However we have attempted to make a certain level of help available even to evaluation users, including this FAQ, help documentation on our secondary site, and if you contact us we may be able to answer specific queries.

  • In my ternary system, where is the binary calculation option? / In my binary system, where is the ternary calculation option?

    The binary and ternary phase diagram calculation options in WinMT are system-specific. That is, in a system with three components the option for a ternary phase diagram calculation is available, and in a system with two components the option for a binary phase diagram calculation is available, but otherwise they are not available. However the multiphase calculations and plots are available for all systems.

  • I clicked "Plot" but there's nothing in the graph! What now?

    You may need to click within the graph to start the calculations - you may have left the option "Start point from graphics cursor" selected. This is because of how MTDATA is configured to search for relevant phases. If you do not want to have to do this every time, there is an option before choosing "Plot" to allow MTDATA to automatically choose the start point. In future versions of MTDATA this should become the default value, but for now you must ensure you specify it before plotting.

    If you have clicked on the diagram (with the left mouse button) and still see nothing, do not panic, some regions in graphs do not trigger full-diagram phase-calculations. In some single-phase regions it may appear that nothing has happened, but a black dot will still appear where you clicked. Try clicking elsewhere (with the left mouse button) in the diagram if you really prefer not to start calculations automatically, or try a new diagram to convince yourself it is working as expected before coming back to the original diagram. Alternatively you could try to click with the right mouse button which will display on the diagram the phase (or phases) calculated to be stable at that composition and temperature.

  • I cannot close the graph - help! / What does it mean that it cannot close the window while a calculation is in progress?

    To end the calculation and close the window, please hold the Control modifier key, and left click with the mouse anywhere in the plot's window.

    Before you end the 'calculation', clicking in the graph using the left mouse button will begin a new set of calculations. This can be useful in certain circumstances, however the downside of this is that you must currently tell MTDATA you want to stop calculating. Ending the calculation means you will be unable to add further labels, or use any other graphing functionality. Once the calculation has ended, you are free to close the window. It might be worth noting that a graph whose calculation has ended is equivalent to a displayed metafile. It may be printed or saved for subsequent use.

  • Why does an "Output" window come up when I attempt to perform a calculation using multiphase for a fixed temperature in WinMT?

    The answer is simply that since the temperature is fixed, there is nothing to plot, but simply sets of single data values. Hence while one could tabulate the output, it is perhaps cleaner to display it in the usual "Output" window

    Please do not worry if you attempt to close the "Output" window and nothing happens - this is expected! Please read the question "How do I close the 'Output' window in WinMT?" below for more information.

  • How do I close the "Output" window in WinMT?

    You cannot - this is by design. The "Output" window is used for all terminal output from calculations using MTDATA - remember that at its heart MTDATA uses many command-line commands to calculate, and so a certain amount of output will only ever be shown through this window.

    Note however that while you cannot close the window, you are able to minimize it again, and in case you had not noticed, that window was actually open the entire time you were using the application - it is just that it starts minimised by default!

'How-To's and Solutions to Common Problems

Please note that these answers get slightly more technically specific towards the end, however they are still some of the questions that we get asked more frequently.

  • General:

    • How do I use MTDATA?

      If your company has used MTDATA in the past, first check if there is anyone present who is able to get you started. If your company is new to MTDATA, please consider coming on one of our MTDATA training courses. There is also extensive help and documentation available on the technical MTDATA site that can be used alongside in-program documentation.

    • How do I define my system in terms of compounds (e.g. CaO) instead of elements?

      This can be done quite easily just by separating the components (compounds in this case) by commas. Further information on how to define a system is available here.

    • What happens in the case when MTDATA does not have interaction data? Can I perform calculations with such components?

      If MTDATA identifies missing interaction data in a phase, it automatically classifies that phase as absent - that is it removes it from calculations.

      To manually include such phases, it must be moved from the "absent" phase list to the "normal" phase list in the GUI, or by using the command


      before using compute in the command-line interface. MTDATA then assumes relevant interactions to be ideal. This is intended to be a fail-safe to stop people unknowingly doing calculations with incomplete datasets.

      As an example, data for the interaction between K2O and PbO are missing in the LIQUID_OXIDE phase from the "K2O-SiO2-PbO" system, so unless the phase is classified as 'normal', it will not be included in calculations, and therefore will not be included in any isopleths even at extremely high temperatures. If set as a normal phase, for example using the command


      then it will likely look like a simple eutectic system due to the ideal interaction assumed.

    • My MTDATA folder contains a huge number of files. How can I organise my MTDATA calculations better?

      It is true that if all your MTDATA results and output files are stored in the one folder eg Work, it can be quite difficult to find just those results pertaining to a particular project. There is no single solution to this but this is the approach we try to adopt at NPL:

      Create a new folder for your project. Then copy into that folder shortcuts to the executable MTDATA files eg winmt.exe, mtdata.exe, mtdata_cmd.exe. Change the properties of these shortcuts such that the "Start in" field is blank. That will ensure that all output from MTDATA initiated from these shortcuts will be stored in this folder. The "double click" on the shortcut to execute MTDATA.

    • Can I write my own software to interact with MTDATA?

      Yes. There are three ways you can develop software to control the inputs to and outputs from MTDATA in order to perform some complicated series of calculations. Each is quite complicated and requires an in depth understanding of how to use MTDATA via the command line interface.

      The first way is to make use of the internal MTDATA macro processing language. Everything that you type into MTDATA through the command line interface can be executed equally well via an MTDATA macro. Indeed most log files created by MTDATA contain a record of everything the user types in to MTDATA and can often be used without editing as a macro to redo the same calculation. MTDATA Macros can be executed by typing in ' at the command prompt. MTDATA also has an a way in which you can interact with the macro, providing, say, a temperature or a composition and is useful for repetitive task where successive calculations differ only very slightly. More information about macros can be found here. A more advanced feature is through use of "user variables". These allow specific results of a calculation to be stored away to be used later for setting conditions. Various arithmetic operations can be performed on user variables eg to convert temperatures from kelvin to celcius. By storing results in user variables, modifying the temperature, resetting the overall composition etc, it is possible to perform quite sophisticated sets of calculations.

      The second way to interact with MTDATA is to write your own software to create MTDATA macros, initiate the execution of MTDATA and process the output. The MTDATA executable "mtdata_cmd.exe" is particularly useful for this as it supports redirection of the output that would normally appear on the screen to a file eg "mtdata_cmd > mtdata_output.txt". Furthermore if the macro file created by your software is called "mtstart.txt" MTDATA will execute this macro automatically. This method is the basis behind MTDATA Launchpad.

      The final and ultimately the most powerful method is through use of the MTDATA API. This is a set of routines which contain the core of MTDATA, eg the ability to search MTDATA databases, read mpi files, set the temperature, pressure and composition and compute the phase equilibrium. Equivalent routines are available to inspect the results of calculations. Access to the api is through the mtdata.dll in a Windows operating system or through an object library under Unix.

    • When I run MTDATA it appear to start running and then stops. Why ?

      One reason why this might happen is that you have a file "mtstart.txt" in the folder where you are working. This is seen by MTDATA as a startup macro and executes automatically when MTDATA is run. This could have been created from previous use of MTDATA LaunchPad and lead to the re-execution of the macro. This can be checked fairly easily by looking at the contents of the folder. The MTDATA log file will also confirm this. The solution is simple - delete the mtstart.txt file.

    • I am using the command line interface. Is there any way that I can recall a previous command ?

      The executable "mtdata_cmd.exe" does have the facility for command line recall ie it will allow you using the up and down arrow keys to bring back a previous line that you typed into the program. It will also allow you to edit that line. That can be very useful if you need to type in the same command several times. "mtdata_cmd.exe" also allows you to scroll back over several pages of input and results from MTDATA.

    • Sometimes output from MTDATA covers more that one screen. Is there any way that I can scroll back over my session with MTDATA ?

      If you are using WinMT this is provided automatically on the output window. You can also do this with "mtdata_cmd.exe" although you may have to adjust the buffer size.

    • How can I get the diagrams calculated by MTDATA sent to my local printer ?

      If you are using WinMT or MTDATA Studio it should be easy to send your diagrams to you local printer using the File|Print command or the printer icon in WinMT. If your printer does not seem to be printing your diagrams please check the printer settings within your computer. If you are using a command line version of MTDATA it may still be possible to initiate a print out of a diagram by using the command "LASER". In this case, however, you will need to configure a file "lp.bat" to sit in your MTDATA program folder. This will generally contain lines such as

      copy "%1% <printer address>

    • I am not getting any on-line help within WinMT ?

      MicroSoft no longer includes within Vista the Windows Help (WinHlp32.exe) program used to display the help file used by WinMT. This program may however be downloaded from the Microsoft website.

  • Databases and MTDATA files:

    • I do not see all the databases I am expecting. Why not?

      The list of databases that you may search can be found in a file "mtconfig.txt". It is possible that your license allows you to use only some of these database as indicated in your permit file "mtpermit.txt". "mtconfig.txt" can be found in the main MTDATA folder while "mtpermit.txt" usually resides in the "Licence" subfolder.

    • How do I create a new database?

      You can create a database for use with MTDATA from the tools menu and selecting "Create new database". You will then need to load data into the database by selecting "Add new data to database", again from the tools menu. Further information is available here.

      If you are using the command line version of MTDATA you should use the utility module.

      Do bear in mind that to use this newly created database, the "mtconfig.txt" file will need to be updated. When created from the utility module, if "mtconfig.txt" is in the MTDATA "work" subfolder - which is not the default situation - this should be done automatically. To add manually (or to check if it has been done), simply add (or check for respectively) the line:


      to the "mtconfig.txt" file, where DBNAME is the name the database will appear under in MTDATA, DATABASENAME is the name of the ".inx" and ".dbs" files created, and "C:\mtdata\work\" is adjusted to point to the correct folder as appropriate. DBNAME and DATABASENAME can be the same. Note that if the databases are in the "databases" folder it is enough to add the line:


      to the file instead. Finally, it may be necessary to increase the database count at the top of the "mtconfig.txt" file by one so that MTDATA knows there is an extra database to load.

      Problems in loading can also occur if there are duplicate "mtconfig.txt" files in other folders, so please check for and remove duplicates if necessary - although creating a backup before deleting is always advisable.

    • Your database does not seem to be available / I get a "keyword not recognised" error on attempting to use a database. Help!

      Firstly, please ensure the "mtconfig.txt" file in your MTDATA folder is correct. For example, if DBNAME is the name of the database in question, (except in the case of databases you yourself have created: see the question above in this case) ensure that the line:


      is in the "mtconfig.txt" file, and not for example the line:


      The reason this can cause problems is that databases used to be stored in the main MTDATA folder, indicated by the presence of mt in the statement, whereas now they are normally kept in the "databases" subfolder, indicated by the presence of db.

      If for some reason you need to add the line to your file because it is not present, remember to increase the database count at the top of the "mtconfig.txt" file by one so that MTDATA knows there is an extra database to load.

      Problems in accessing databases may also occur if there are duplicate "mtconfig.txt" files in other folders, so please check for and remove duplicates if necessary - although creating a backup before deleting is always advisable.

    • I have searched through the databases and a number of important phases are missing from the calculations. Why are they missing, and what can I do about this?

      When MTDATA searches databases for a particular system it often comes across phases with missing interactions, for example if data for the fcc_a1 phase for part of a multicomponent system have not been assessed. MTDATA will then create an mpi file which contains data for this phase but it will also contain a flag which will classify this phase as absent once read into MULTIPHASE or one of the other MTDATA modules. The user may classify this phase as normal (which will assume that the mssing interaction is set to zero) but, because of the missing interations, the result must be checked carefully particularly if the missing phase is calculated to be stable. This is especially a problem if the user wishes to perform calculations for a complicated system where one or more of the component binary systems have not been assessed. The user will need to check the likely impact of the data for the missing systems on the final result, for example by looking at the overall composition of the material of interest.

    • I keep getting an error saying the format is not correct when I try to generate a .fap file for use with the 'Fit and Plot' module. Help?

      Make sure that the last entry in the file is duplicated, with the second value changed to 0. So for example if plotting Cp vs. T, and the last entry is:

      2800.0           120.00

      then simply add the following line at the end:

      2800.0           0.0
  • Plots:

    • Can I run a series of calculations sequentially, for example overnight or over the weekend?

      Yes, you can! Please consider writing a macro for the command-line version of MTDATA. Using the command [MODE=BATCH removes the pause between any diagrams and precisely allows a series to be run nonstop. The [metafile= command can be used to save diagrams in metafiles to be loaded later into MTDATA for use or for export into other formats.

    • How do I copy MTDATA diagrams into Word or PowerPoint?

      The best way to do this is to view the diagram using MTDATA studio. This should be included in all recent copies of MTDATA downloaded from our site. Then use the file menu to save the file as a .png file (portable network graphics file) which is then suitable for importing into any standard office package.

    • How do I make graphical changes to the liquidus-contour plot / other plot?

      There are two approaches that can be taken, each with advantages and disadvantages.

      The first, and perhaps more fiddly method, has the advantage that after making changes, your plot can still be loaded into MTDATA for further use. Export the plot you wish to edit as an MTDATA metafile, and open this exported file with a text editor. From here you have complete control over the plot and can change anything you like, as long as the syntax remains correct. For example, to change a label on the plot, look for a line similar to

      LABEL "|L0000" 79.1111 53.44444 0.2 0

      To then change the size, change the variable that above is valued at 0.2 to a larger value.

      The LABEL token has the syntax

      LABEL "label_text" x-coordinate y-coordinate size orientation

      with orientation in degrees, so you can change respectively what the label says, the location of the label, the size, or the orientation of the text.

      For more complex changes, more work is required. For example, to change the colour of a line, you must first identify the batch of POSITN and JOIN commands that make up the line in the metafile. This is the hard bit.

      When you have found that, you can add (as an example) the line

      HRDLIN 2

      at the start and

      HRDLIN 1

      at the end, to say respectively that the lines from that point on should be blue, and then black again.

      HRDLIN codes currently correspond to the following colours:

      Value Colour
          1   Black
          2   Blue
          3   Green
          4   Red
          5   Yellow

      and numbers above this cycle around these five in turn. Currently the colour palette is rather limited, but it is currently in our suggestions pool to add more colours, so please let us know if this is a feature that would be helpful to you. An option is available in Studio to use a "dot-dash" line style in place of colours.

      A second approach may be easier for those unwilling to fiddle with screens of code, however it has the drawback of breaking backward compatibility with MTDATA, ie. files edited in this manner will no longer be recognised by MTDATA.

      With the file open in MTDATA Studio, save the plot as an enhanced windows metafile. It will then be possible to use standard SVG editors to make changes to the metafile in a WYSIWYG GUI application - ie. changes are made live, and in a more natural way. There are some quirks that need to be worked around, but in general, this technique is more felxible and can often produce high quality results than just editing the metafile directly. One SVG editor that is known to produce positive results editing the exported .emf files is Inkscape, though some clipping may be necessary with some graphs. If you are keen to use this technique and still maintain MTDATA compatibility, please get in touch as if there is sufficient demand we may be able to extend the format compatibility.

    • I am trying to calculate liquidus contours for a system, but am getting different results from separate sets of calculations. Help?

      Please ensure that the temperature limits you give span all possible liquidus temperatures in your system.

      The reason this is necessary is that in calculating the liquidus contours, MTDATA finds the first phase boundary stepping down in temperature from the upper limit to the lower limit, and calls that the liquidus. For diagrams where the primary liquidus lies outside the given temperature limits, MTDATA may give a secondary (or other) phase boundary plotted as the liquidus, resulting in erroneous plots.

      As an example, a good temperature range to use for the MTOX database is 373K to 3373K, which should cover most phase boundaries of interest to users of that database.

    • How do I replot an isopleth that was created during a previous run of MTDATA?

      MTDATA keeps the results of the last isopleth calculated in a file "xxx.iso" where "xxx" is the root of the input file name. This will be overwritten each time an isopleth is calculated on that input file in that folder. To replot the isopleth enter the following:

      define data <input_file> !

      set u(application_code) 14 !

      plot go

    • How do I see / label the primary phase field names when using 'liqsect'?

      Liqsect currently labels the primary phase fields using numbers which correspond to the phase names on the phase list obtained by using the command:


      from the command-line version of MTDATA.

      There is currently no interactive facility to label the phase fields with the phase names - it is currently in our system as an enhancement request. However it is possible to add the labels manually by replacing in the MTDATA Metafile the numeric phase numbers by the phase names. To save the diagram as an MTDATA metafile in WinMT simply click "File", "Save As..." and choose the relevant option, or in Classic use the commands:


      plot diagram


      Once you have the metafile, open it in a text editor, and replace the numeric labels by the phase names. The labels in an MTDATA metafile use the syntax:

      LABEL "labelname" x-coordinate y-coordinate size orientation

      with orientation in degrees. For example:

      LABEL "REUTERITE" 25 65 0.4 0.0

      Please note however that at the moment the coordinate system is orthogonal (that is, cartesian x- and y-axes) and not the normal ternary coordinates, so some trial and error may be necessary if you wish to move the labels. We are working on changing this coordinate problem.

      As a final note, it is worth mentioning that if you choose to save as an enhanced windows metafile instead, it may be possible to edit this file in some SVG (support vector graphics) applications - for example Inkscape has good compatibility with MTDATA exports, though some clipping may be necessary. The advantage of this is that the editing can be done in a WYSIWYG GUI editor rather than from lines of code, however the disadvantage is that the result cannot then be imported back into MTDATA for later viewing.

  • Other Questions:

    • How do I...?

      If your question has not been answered above, then there are several things you can try. Firstly, please check the supplied documentation for help or the comprehensive help on the MTDATA web site - this documentation is there for a reason, and for many simple queries it may contain sufficient information to help you. Otherwise, if you currently have support in using MTDATA, please feel free to get in touch and we'll do our best to help. If you do not have support in using MTDATA, consider taking that offer up and we will be glad to offer any assistance we can - or you can simply beg assistance and we might consider granting you mercy and helping anyway. (Aren't we kind!)

Other Common Questions

Contact Us

Updated 13 September 2011