Bug reports

Your feedback is important to make XMapTools and Bingo-Antidote better. You can submit bug reports or feature requests to the XMapTools developer repository on Github.

For the sake of transparency, all known and past issues are and will be listed below. Before reporting a new bug, please check if it is known. Thank you for your participation.

Known problems (XMapTools 4.3)

    Fixed problems

    • 031 – July 31st, 2023 – Error in the external function for rutile thermometry (see source code here). The pressure variable for the thermometers of Kohn (2020) should be expressed in bar and not in kbar. Workaround: enter the pressure value in bar to obtain the correct temperature. This bug will be fixed in XMapTools 4.3. Thanks to Mona Lueder for discovering and reporting this problem.

     

      Archives

      • 030 – March 26, 2020 – XMapTools 3.3.1 is not fully compatible with MATLAB R2020a and several buttons/options are not available in the interface. Fixed in XMapTools 3.4.1 Thanks to Daniel Peters for discovering and reporting this issue
      • 029 – December 16, 2019 – Update is not possible with MATLAB 2014b whereas XMapTools updates should be compatible with this version of MATLAB. A patch for users of MATLAB 2014b is available. Fixed in XMapTools 3.4.1
      • 028 – July 11, 2019 – Warning message in the Command Window while saving large XMapTools projects for one or more of the variables. Saving projects involving high–resolution maps (> 1000*1000 pixels) and many maps in Quanti can result in a warning message indicating that the variable Quanti was not saved. In this case, (1) the data in the workspace Quanti are lost and (2) the project file is corrupted – it cannot be opened by XMapTools. Fixed in XMapTools 3.1.2  Thanks to Thereza Yogi for discovering and reporting this issue
      • 026 – May 10, 2019 – The function Transfer to Results did not work at all preventing the data to be displayed in the Spider module. Fixed in XMapTools 3.1.2
      • 025 – Feb. 24, 2018 – The merge function introduced in XMapTools 2.6.4 caused several unexpected issues, especially in the structure of the data saved in project files. A project file might be corrupted if this function was used before Saving the project. Fixed in XMapTools 3.1.1.
      • 024 – Dec. 04, 2018 – The file standard.txt is not properly read by XMapTools if a line of the third block of data has a tabulation and an empty space at the end.  Fixed in XMapTools 2.6.1 on Dec. 18, 2018. Thanks to Laure Laffont for discovering and reporting this error.
      • 023 – Jul 24, 2018 – The function to delete maps in the workspace “Quanti” is not working correctly if the quanti file to be deleted located  between the second and the n–1 quanti file (with n the number of quanti files). Fixed in XMapTools 2.5.2 on Aug. 8, 2018
      • 022 – Jan 08, 2018 – There was an error in the dead time correction function of the import tool (probably since 2.4.1). It is strongly recommended to all users to re–import the X–ray maps with XMapTools 2.4.3 Fixed in XMapTools 2.4.3 on Jan. 10, 2018
      • 021 – Sep 19, 2017 – Several functions such as sampling line or export oxide compositions are not working for the users having MATLAB 2013b and previous versions. Fixed in XMapTools 2.4.2 released on Sep. 20, 2017. Thanks to Francesco Giuntoli for reporting this error.
      • 020 – May 14, 2017 – The function “transfer to quanti” cannot be used to transfer only part of the maps. If only n maps are selected, the first n maps in the list will be transferred instead with the wrong names.  Select all the maps and the function will work ok with the correct names. Fixed in XMapTools 2.4.1. Thanks to Laura Airaghi for reporting this error.
      • 019 – Nov. 11, 2016 – The external function ThermoFctChlBourdelle.m has an error. Fixed in XMapTools 2.4.1.  Thanks to Janet Muhling for reporting this error.
      • 018 – July 11, 2016 – The external function StructFctGarnetFe3.m has an error line 149. Fixed in XMapTools 2.3.1. Thanks to Marco Burn for reporting this error.
      • 017 – April 4, 2016 – The function sampling area calculates the median (not the mean) of the selected pixels. Fixed in XMapTools 2.3.1
      • 016 – March 4, 2016 – The function generate a density map (from selected mask file) requires the use of the file Classification.txt (see user guide page 56). If the button “no” or “cancel” is pressed XMapTools stops working and generates an error message. Fixed in XMapTools 2.3.1. Thanks to Gaétan Link for reporting this error.
      • 015 – August 17, 2015 – The diary functionality does not work with XMapTools 2.1.7. Fixed in XMapTools 2.2.1. Thanks to Nils Bigge for reporting this error.
      • 014 – August 14, 2015 – Chem2D module is not working with MALTAB 2015a. An error occurs after pressing the button Chem2D and the GUI does not start. Fixed in XMapTools 2.2.1 Thanks to Nils Bigge for reporting this error.
      • 013 – August 10, 2015 – If the computer is connected to a wifi network but not logged in to have access to Internet, the following error occurs when launching XMapTools: Index exceeds matrix dimensions. Error in (path) Line 180. Fixed in XMapTools 2.2.1. Thanks to Marco Burn for reporting this error.
      • 012 – February 10, 2014 – The new function to import pixel coordinates during the classification doesn’t work if the map has been rotated. If you don’t use the rotate function, the coordinates are the right. This error will be fixed in XMapTools 1.6.6. Solution: Do not use the rotate function before and during the classification step. You can alternatively use the user–selection mode. Fixed in XMapTools 2.1.2
      • 013 – November 03, 2014 – XMapTools fails to open some projects if the function filter (in quanti) has been used. This error will be fixed in the next release. Solution: Download the new XMapTools.p file here and replace the old one in your XMapTools directory. Fixed in XMapTools 2.1.2
      • 011 – November 18, 2013 – The download of the XMapTools package using the launcher doesn’t work properly from some universities using a proxy. In this special case the connection to our ftp server seems to be not allowed. We know this problem since many month and the only way to solve it is to provide an alternative way for downloading the package. Fixed in XMapTools 1.6.5.
      • 010 – August 02, 2013 – All the ‘bulk compositions’ exported are calculated using the average composition of all the pixel from the bulk map including pixels that show null compositions (rim, not standardized phase…). Fixed in XMapTools 1.6.4
        009 – August 02, 2013 – Standardization function can fail if the intensities of an element for all the pixels corresponding to the spot analyses are null. Fixed in XMapTools 1.6.4
      • 008 – July 26, 2013 – Backup saved using the button save is always save in the current directory of MATLAB©. Fixed in XMapTools 1.6.4
      • 007 – April 28, 2013 – If you save an existing and loaded project using the function ‘save as’, the project will be saved using the old name. Fixed in XMapTools 1.6.2
      • 006 – April 24, 2013 – The fonction ‘poly2mask’ used by user to select an area (Export_area, Chem2D and TriPlot3D: zoom, selections) requires the MATLAB© Statistic Toolbox to work. Fixed in XMapTools 1.6.2
      • 005 – April 23, 2013 – Button median filter (Medfilter) requires the MATLAB© Image Processing Toolbox to work. Fixed in XMapTools 1.6.2
      • 004 – March 8, 2013 – Button transfert to quanti (TTQuanti) can not be used with a mineral selected. In this case the first mineral is always sent. Fixed in XMapTools 1.6.2
      • 003 – December 13, 2012 – If you save as the project as a new project, the new name is not updated in the project window. Fixed in XMapTools 1.6.1
        002 – November 6, 2012 – Error “” : ??? Error using ==> load Unable to read file NAMEFILE.txt: No such file or directory. Error in ==> C:\XMapTools\XMapTools.p>MButton1_Callback at 2868 Error in ==> gui_mainfcn at 96 feval(varargin{:}); Error in ==> C:\XMapTools\XMapTools.p>XMapTools at 45 Error in ==> @(hObject,eventdata)XMapTools(‘MButton1_Callback’,hObject,eventdata,guidata(hObject)) ??? Error while evaluating uicontrol Callback.XMapTools v1.5.3 : Problem with the current folder. If the XMapTools setup is completed (see the notice), you can run and use XMapTools from any folder, but you need to change the “current folder” (before running XMapTools) to the folder in which the X–ray maps are stored. This error will be fixed in the next version, but it’s strongly recommended to change the “current folder” before running XMapTools also because the diary files, the backups and the exported files will be saved in this folder. Fixed in XMapTools 1.6.1
      • 001 – September 25, 2012 – Error “Compute Masks” : Error using XkmeansX (line 240) Empty cluster created at iteration 1. XMapTools v1.5.3 : Problem with the “Select Map” window. You must select at least 2 maps (i.e. two elements). A problem with the auto–select–all can occur. This error will be fixed in the next release. Fixed in XMapTools 1.6.1