{ "version": "https://jsonfeed.org/version/1", "title": "mXrap Blog", "home_page_url": "https://es.mxrap.workers.dev/updates", "description": "mXrap Blog", "items": [ { "id": "https://es.mxrap.workers.dev/updates/changelogs/mxrap-6-1-4", "content_html": "

6.1.4 introduces a few bug fixes, and a new feature: the ability to download files from HTTP and SFTP hosts (SFTP is for transferring files via SSH - used for downloading event files from IMS servers).

\n

You will be prompted to upgrade by a yellow banner at the top of the Apps window. Follow the link to download and install.

\n\n

What's New for Users - mXrap 6.1.4​

\n

Release Date: 30 September 2025

\n

mXrap Changes​

\n\n

mXsync Changes​

\n\n

What's New for Developers - mXrap 6.1.4​

\n

Release Date: 30 September 2025

\n", "url": "https://es.mxrap.workers.dev/updates/changelogs/mxrap-6-1-4", "title": "mXrap 6.1.4 - Release notes and Changelogs", "summary": "6.1.4 introduces a few bug fixes, and a new feature: the ability to download files from HTTP and SFTP hosts (SFTP is for transferring files via SSH - used for downloading event files from IMS servers).", "date_modified": "2025-09-30T00:00:00.000Z", "author": { "name": "mXrap Team", "url": "https://mxrap.com/team" }, "tags": [ "Changelogs", "Developers", "Updates", "mXsync" ] }, { "id": "https://es.mxrap.workers.dev/updates/changelogs/mxrap-6-1-3", "content_html": "

This version brings a large number of bugfixes and user experience improvements.

\n

You will be prompted to upgrade by a yellow banner at the top of the Apps window. Follow the link to download and install.

\n\n

What's New for Users - mXrap 6.1.3​

\n

Release Date: 23 July 2025

\n

Overview​

\n

6.1.3 is a large maintenance release, with over 100 changes that will directly improve the user experience, and many more lower-level improvements not listed here.

\n

Changes and Bugfixes​

\n\n
Important

In the past, files could potentially be partially written to disk, resulting in corrupted data files.

\n\n
\n
\n

Date Variables now has a \"Start of Year\" and \"Today\" button

\n
\n


\nLoading a Workspace via the workspace button is more logical.

\n

Double-clicking on another workspace will reload the app to behave as if it had been loaded from scratch.

\n\n
\n
\n

The Webforms GUI now helps you to choose the stable URLs to use.

\n

In general, you should not use URLs based on Dynamic IP addresses, as any pending reports will become stuck in the web browser when that IP address changes.

\n
\n
\n

mXsync's file list interface has been much improved - you can now sort by file sizes and search for filenames.

\n

What's New for Developers - mXrap 6.1.3​

\n

Release Date: 23 July 2025

\n", "url": "https://es.mxrap.workers.dev/updates/changelogs/mxrap-6-1-3", "title": "mXrap 6.1.3 - Release notes and Changelogs", "summary": "This version brings a large number of bugfixes and user experience improvements.", "date_modified": "2025-07-23T00:00:00.000Z", "author": { "name": "mXrap Team", "url": "https://mxrap.com/team" }, "tags": [ "Changelogs", "Developers", "Updates" ] }, { "id": "https://es.mxrap.workers.dev/updates/changelogs/mxrap-6-1-2", "content_html": "

This version brings several new features to mXrap 6, as well as a host of bugfixes and performance improvements.

\n

You will be prompted to upgrade by a yellow banner at the top of the Apps window. Follow the link to download and install.

\n\n
nota

The first time you run mXrap following this update it may take a minute to list the root folders, and it will need to read the root folder files from the disk again.

\n

mXrap 6.1.2 - What's new for Users​

\n

Release Date: 13 March 2025

\n

Webforms Server​

\n

The server requires an upgrade before the end of March in order to continue working properly, due to an expiring SSL certificate.

\n\n

Survey File Improvements​

\n\n

User Interface Improvements​

\n\n

Root Folder Maintenance​

\n\n

Other Bugfixes​

\n\n

mXrap 6.1.2 - What's new for Developers​

\n

Release Date: 13 March 2025

\n

(Human Language) Translations​

\n\n

App Developer Experience​

\n\n

3D Views​

\n\n

Actions​

\n\n

HTML View (and HTML in Panels)​

\n\n

HTML in Panels​

\n\n

HTML in Other Places​

\n\n

Javascript (Tablecalcs, Rowcalcs)​

\n\n

Other Bugfixes​

\n", "url": "https://es.mxrap.workers.dev/updates/changelogs/mxrap-6-1-2", "title": "mXrap 6.1.2 - Release notes and Changelogs", "summary": "This version brings several new features to mXrap 6, as well as a host of bugfixes and performance improvements.", "date_modified": "2025-03-13T00:00:00.000Z", "author": { "name": "mXrap Team", "url": "https://mxrap.com/team" }, "tags": [ "Changelogs", "Developers", "Updates" ] }, { "id": "https://es.mxrap.workers.dev/updates/moment-tensor-colour-update", "content_html": "

For users that look at moment tensors, please be aware that we are changing the arrow colours and improving the legend.

\n\n

The colours of the moment tensor T and P axes have been updated to align with the colours used in ESG and IMS system:

\n\n

The legend for the moment tensors now has nice labels to allow you to identify the axes, planes and motions.

\n

You can see this change in the comparison below.

\n
\n

Old Moment Tensor Colours

\n
\n

Updated Moment Tensor Colours

", "url": "https://es.mxrap.workers.dev/updates/moment-tensor-colour-update", "title": "Moment Tensor Axis Colour Update", "summary": "For users that look at moment tensors, please be aware that we are changing the arrow colours and improving the legend.", "date_modified": "2025-02-19T00:00:00.000Z", "author": { "name": "Paulus Angkodjojo", "url": "https://www.linkedin.com/in/paulus-angkodjojo/" }, "tags": [] }, { "id": "https://es.mxrap.workers.dev/updates/developers/developer-updates-january-2025", "content_html": "

Recent updates which may be of interest to developers

\n\n

Caving is now bundled​

\n

The Caving module is now bundled. If you have custom tools that connect to tools in Caving, please check for any broken links or redirections required. If you need assistance with this or if the tools that you were using are no longer accessible, please contact us

\n

Survey surfaces has moved to !/Base​

\n

The survey surfaces utilities, used when painting on surveys, have been moved from ! to !/Base so that they can be used in apps that do not require the seismic module. If you have custom apps that are linked to the survey surfaces tools, please check them and redirect any broken links to the new location.

\n

Library for mapping data from lines to points​

\n

A new JavaScript library was added to simplify the task of mapping data from a collection of line segments to the points that are within a certain distance of those line segments. For example, this can be used to colour surveys based on borehole data by mapping from line segments along the borehole onto the vertices of survey surfaces. You can find this library at mxjs/base/algorithms/map_lines_to_points.js

\n

Supporting extended clipping options in 3D Views​

\n

mXrap 6.1 has extended the 3D clipping feature to support more general clipping volumes. Previously clipping volumes were restricted to axis-aligned bounding boxes, specified using a minimum and maximum XYZ. The more general clipping volumes support shapes that can be created using the 3D View's selection box system, as shown below.

\n
\n

To support these more general shapes, a new column needs to be linked in the clipping volumes setup of your 3D Views, as shown below.

\n
\n

Note that after saving these updated 3D Views, they will only be usable with mXrap 6.1 or higher. To help you identify 3D Views which need to be updated, when you have a settings window open, any 3D Views that are missing the link will show a red error message at the top of their window.

\n

Chart interaction​

\n

mXrap 6.1 brought several improvements to charts, including support for user interaction with charts.

\n

You can now control whether a chart series is able to be displayed as points, lines, or both. Previously a user would always be able to turn on the points or lines options, even if the series was not intended to display that way. In the image below, you can see these options at the top of the Data panel, 'Enable plotting as points' and 'Enable plotting as lines'. All series in existing charts will default to having both of these options enabled.

\n

For lines-only series, there is also a special option which creates lines that fill either the horizontal or vertical range of the chart window. In these cases you only need to specify one coordinate, e.g. the image below shows the creation of a magnitude threshold line which crosses the chart horizontally, and is specified by a magnitude number on the left axis only.

\n

The ability to specify a single value rather than a column is also a new feature. If both the X and Y are specified as single values, or if one is a single value and the other is not specified (as with the magnitude threshold below), then no input table is needed at all. This simplifies many cases where developers previously had to create new tables in order to plot single values, indicator lines, thresholds, etc. In order to change between single values and columns, simply click on the type button for that axis (e.g. Date for X and Number for Y in the below image) and choose either the column or single value types.

\n
\n

Lines series now have the option to start and/or end each line at a particular point. This is particularly useful for histograms, for example in the below image all lines in the series will start from Y=0. Because the starting X value is unspecified, the lines will start from the X value of the first point in the line. This ensures that all lines in the histogram correctly start from the bottom of the axis, without requiring us to create a new table with extra points at the zero coordinate.

\n
\n

The Markers, Hover tab contains the familiar marker menu configuration options, and new options for enabling hover information and for optional behaviour when double-clicking on points.

\n
\n

When hover information is enabled for a series, hovering the mouse cursor over a point in that series will display a tooltip containing information about the point. At the moment the tooltip shows the exact values for the point's X and Y coordinates, in this case an event's date and ML. If the series is using a marker with a range of colours, then the input value used for the marker colour is also displayed, in this case the event's seismic moment.

\n
\n

The bottom of the \"Markers, Hover\" tab is where you can configure what happens when the user double-clicks on a point in that series.
\nIt can write the ID of that point to a Value (e.g. Variable), and then trigger an Action. From there, there are many possibilities for extending your chart's abilities. For example, the user could double-click on a seismic event, which would adjust a filter to show other events within a range of time and space around that event.

\n

Finally, the Editing tab is used to configure the new chart editing features. Editing can be enabled for each axis of a series independently. With editing enabled the user can hold the shift key, then click and drag a point to interactively move it to a new location in the chart. If only one axis has editing enabled, they will only be able to move the point along that axis.

\n

For the simplest case, if you are displaying a series and the axis column is editable (it is defined in a variables tool, or it comes from an import CSV tool that is write-enabled), then moving a point will cause the value to be updated in place, the same as if you had edited that value in an existing table view.

\n
\n

More complicated situations might require us to do some calculation on the original value. For example, the image below shows someone moving a bolt in the ground support standard designer (the yellow line shows where the point will be moved to). Althought the point is displayed using X and Y coordinates, these are calculated values and the underlying data stores the bolt position as a distance along the tunnel profile, ensuring that the bolt is fixed to the profile and making it easy to calculate the spacing between bolts.

\n

To support this case we can use the optional tools shown in the Editing tab above. When the user moves the point, the ID of the point as well as the new X and Y location are written into variables that we choose. We can then make a calculation which reads those values and uses them to calculate the correct distance along the tunnel profile. Finally, we set up an action to trigger which will copy our calculated value into the correct place for the moved point.

\n

This option can also be used for validating changes caused by the user. In this case we validate the new location by ensuring it is on the tunnel profile, but event simple values may benefit from validation, e.g. ensuring that a user can't move a percentage value below zero or above one hundred.

\n
", "url": "https://es.mxrap.workers.dev/updates/developers/developer-updates-january-2025", "title": "Developer Updates - January 2025", "summary": "Recent updates which may be of interest to developers", "date_modified": "2025-02-10T00:00:00.000Z", "author": { "name": "Matthew Heinsen Egan", "url": "https://www.linkedin.com/in/matthew-heinsen-egan/" }, "tags": [] }, { "id": "https://es.mxrap.workers.dev/updates/esep-ratio-charts-have-moved", "content_html": "

The Es:Ep ratio chart previously found under Charts has been incorporated into the Parameter Distributions chart.

\n\n
\n

Select the Es:Ep option using the chart controls to replicate the previous Es:Ep ratio chart.

\n

\n

Similar to above, the Es:Ep ratio chart for VSAs (previously found under VSA > Charts) is now found in the VSA Parameter Distributions.

\n

\n
nota

You will need to recreate any workspaces that include the old Es:Ep ratio charts. Simply replace the old chart with the new parameter distribution chart set to the Es:Ep option.

", "url": "https://es.mxrap.workers.dev/updates/esep-ratio-charts-have-moved", "title": "Es:Ep Ratio Charts Have Moved", "summary": "The Es:Ep ratio chart previously found under Charts has been incorporated into the Parameter Distributions chart.", "date_modified": "2024-12-05T00:00:00.000Z", "author": { "name": "Laura Camball", "url": "https://www.linkedin.com/in/laura-camball/" }, "tags": [ "General Analysis", "Seismicity", "Charts" ] }, { "id": "https://es.mxrap.workers.dev/updates/changelogs/mxrap-6-1-0", "content_html": "

Highlights​

\n

This version brings several new features to mXrap 6, as well as a host of bugfixes and performance improvements.

\n\n

3D Interactive Slicing​

\n

Slice through a 3D View to get a better view of data deep inside of a mine.

\n
\n

Chart Interactions​

\n

Manipulate elements on a chart using the mouse, or hover to see the data represented by that specific point.

\n
\n

You will be prompted to upgrade by a yellow banner at the top of the Apps window. Follow the link to download and install.

\n

What's New for Users - mXrap 6.1.0​

\n

Release Date: 4 December 2024

\n

New Feature: 3D Interactive Slicing​

\n

Users can now interactively slice through a 3D display of data.
\nUse the dot, line or triangle buttons to create the initial slicing tool.

\n
\n

Then manipulate the slicing tool with the CTRL key and the mouse.
\nAdjust the exact settings with the \"Slicing\" tab on the far right of the window.

\n
\n

New Feature: Extended clipping options in 3D Views​

\n

mXrap 6.1 has extended the 3D clipping feature to support more general clipping volumes.
\nPreviously clipping volumes were restricted to axis-aligned bounding boxes, specified using a minimum and maximum XYZ.
\nThe more general clipping volumes support shapes that can be created using the 3D View's selection box system, as shown below.

\n
\n

New Feature: Chart Interactions​

\n

Users can now manipulate elements in a chart with the mouse.
\nIn this example, the mouse is used to directly edit the positions of rock bolts in a Ground Support Design.

\n
\n

New Feature: Chart Mouse-Hover Information​

\n

Charts now show the location of the mouse cursor on the visible axes,
\nand will also show information about the point under the mouse.

\n
\n

Bug fixes and Improvements​

\n

User Interface​

\n\n

Survey Import​

\n\n

CodeMeter / Dongle​

\n\n

mXsync​

\n\n

What's New for Developers - mXrap 6.1.0​

\n

Release Date: 4 December 2024

\n

Supporting extended clipping options in 3D Views​

\n

mXrap 6.1 has extended the 3D clipping feature to support more general clipping volumes. Previously clipping volumes were restricted to axis-aligned bounding boxes, specified using a minimum and maximum XYZ. The more general clipping volumes support shapes that can be created using the 3D View's selection box system, as shown below.

\n
\n

To support these more general shapes, a new column needs to be linked in the clipping volumes setup of your 3D Views, as shown below.

\n
\n

Note that after saving these updated 3D Views, they will only be usable with mXrap 6.1 or higher. To help you identify 3D Views which need to be updated, when you have a settings window open, any 3D Views that are missing the link will show a red error message at the top of their window.

\n

Chart interaction​

\n

mXrap 6.1 brought several improvements to charts, including support for user interaction with charts.

\n

You can now control whether a chart series is able to be displayed as points, lines, or both. Previously a user would always be able to turn on the points or lines options, even if the series was not intended to display that way. In the image below, you can see these options at the top of the Data panel, 'Enable plotting as points' and 'Enable plotting as lines'. All series in existing charts will default to having both of these options enabled.

\n

For lines-only series, there is also a special option which creates lines that fill either the horizontal or vertical range of the chart window. In these cases you only need to specify one coordinate, e.g. the image below shows the creation of a magnitude threshold line which crosses the chart horizontally, and is specified by a magnitude number on the left axis only.

\n

The ability to specify a single value rather than a column is also a new feature. If both the X and Y are specified as single values, or if one is a single value and the other is not specified (as with the magnitude threshold below), then no input table is needed at all. This simplifies many cases where developers previously had to create new tables in order to plot single values, indicator lines, thresholds, etc. In order to change between single values and columns, simply click on the type button for that axis (e.g. Date for X and Number for Y in the below image) and choose either the column or single value types.

\n
\n

Lines series now have the option to start and/or end each line at a particular point. This is particularly useful for histograms, for example in the below image all lines in the series will start from Y=0. Because the starting X value is unspecified, the lines will start from the X value of the first point in the line. This ensures that all lines in the histogram correctly start from the bottom of the axis, without requiring us to create a new table with extra points at the zero coordinate.

\n
\n

The Markers, Hover tab contains the familiar marker menu configuration options, and new options for enabling hover information and for optional behaviour when double-clicking on points.

\n
\n

When hover information is enabled for a series, hovering the mouse cursor over a point in that series will display a tooltip containing information about the point. At the moment the tooltip shows the exact values for the point's X and Y coordinates, in this case an event's date and ML. If the series is using a marker with a range of colours, then the input value used for the marker colour is also displayed, in this case the event's seismic moment.

\n
\n

The bottom of the \"Markers, Hover\" tab is where you can configure what happens when the user double-clicks on a point in that series.
\nIt can write the ID of that point to a Value (e.g. Variable), and then trigger an Action. From there, there are many possibilities for extending your chart's abilities. For example, the user could double-click on a seismic event, which would adjust a filter to show other events within a range of time and space around that event.

\n

Finally, the Editing tab is used to configure the new chart editing features. Editing can be enabled for each axis of a series independently. With editing enabled the user can hold the shift key, then click and drag a point to interactively move it to a new location in the chart. If only one axis has editing enabled, they will only be able to move the point along that axis.

\n

For the simplest case, if you are displaying a series and the axis column is editable (it is defined in a variables tool, or it comes from an import CSV tool that is write-enabled), then moving a point will cause the value to be updated in place, the same as if you had edited that value in an existing table view.

\n
\n

More complicated situations might require us to do some calculation on the original value. For example, the image below shows someone moving a bolt in the ground support standard designer (the yellow line shows where the point will be moved to). Although the point is displayed using X and Y coordinates, these are calculated values and the underlying data stores the bolt position as a distance along the tunnel profile, ensuring that the bolt is fixed to the profile and making it easy to calculate the spacing between bolts.

\n

To support this case we can use the optional tools shown in the Editing tab above. When the user moves the point, the ID of the point as well as the new X and Y location are written into variables that we choose. We can then make a calculation which reads those values and uses them to calculate the correct distance along the tunnel profile. Finally, we set up an action to trigger which will copy our calculated value into the correct place for the moved point.

\n

This option can also be used for validating changes caused by the user. In this case we validate the new location by ensuring it is on the tunnel profile, but event simple values may benefit from validation, e.g. ensuring that a user can't move a percentage value below zero or above one hundred.

\n
\n

Tablecalc and Row Calc JS Engine Update​

\n

mXrap version 6 supported ECMAScript 5.

\n

mXrap version 6.0 supported up to ECMAScript 2022 (partially)

\n

Version 6.1 now supports:

\n", "url": "https://es.mxrap.workers.dev/updates/changelogs/mxrap-6-1-0", "title": "mXrap 6.1.0 - Release notes and Changelogs", "summary": "Highlights", "date_modified": "2024-12-04T00:00:00.000Z", "author": { "name": "mXrap Team", "url": "https://mxrap.com/team" }, "tags": [ "Changelogs", "Developers", "Updates" ] }, { "id": "https://es.mxrap.workers.dev/updates/changelogs/mxrap-6-0-6", "content_html": "

mXrap version 6.0.6 is now available to all users. This release is focused on bugfixes and performance improvements and will be the final release for version 6.0. Follow one of the links in the banner at the top of the Apps window to upgrade.

\n\n

What's new for Users - mXrap 6.0.6​

\n

Release Date: 26 September 2024

\n

User Interface​

\n\n

Survey Import​

\n\n

CodeMeter / Dongle​

\n\n

mXsync​

\n\n

What's new for Developers - mXrap 6.0.6​

\n

Developers​

\n

Release Date: 26 September 2024

\n

Tableview / Action​

\n\n

Tablecalc​

\n\n

Tablecalc FileIO​

\n\n

HTML View​

\n\n

System Information​

\n\n

Bug Fixes​

\n\n

Other recent changes of note:​

\n", "url": "https://es.mxrap.workers.dev/updates/changelogs/mxrap-6-0-6", "title": "mXrap 6.0.6 - Release notes and Changelogs", "summary": "mXrap version 6.0.6 is now available to all users. This release is focused on bugfixes and performance improvements and will be the final release for version 6.0. Follow one of the links in the banner at the top of the Apps window to upgrade.", "date_modified": "2024-09-26T00:00:00.000Z", "author": { "name": "mXrap Team", "url": "https://mxrap.com/team" }, "tags": [ "Changelogs", "Developers" ] }, { "id": "https://es.mxrap.workers.dev/updates/structure-rmd", "content_html": "

There have been lots of recent changes to the Rock Mass Data Analyser. Some of these changes just add features, but as part of these changes we have had to re-organise how the data is structured in the app. This means that the individual databases for all of the data now come in as aliases in the root folder under Settings/#Site Setup/RMDA/Inputs folder (instead of places such as Rock Mass Characterisation/RMDA/Datalearn/base/2 Rock Mass Quality).

\n\n

This means that if you have any custom apps that link to the RMDA data (or have made any site specific changes to the app), then your work may break. It's probably best to contact us if this is the case - we can help you to fix your work.

\n

There is also an additional column added to the back of the database (Imported Geotechnical Domain). This is unlikely to affect anything unless you had additional extra columns added to the back of your database.

\n

We will give more details on the new features in a later general post (as changes are still being made and new features added), but those completed so far include

\n\n
", "url": "https://es.mxrap.workers.dev/updates/structure-rmd", "title": "Updates to Rock Mass Data Analyser structure", "summary": "There have been lots of recent changes to the Rock Mass Data Analyser. Some of these changes just add features, but as part of these changes we have had to re-organise how the data is structured in the app. This means that the individual databases for all of the data now come in as aliases in the root folder under Settings/#Site Setup/RMDA/Inputs folder (instead of places such as Rock Mass Characterisation/RMDA/Datalearn/base/2 Rock Mass Quality).", "date_modified": "2024-07-12T00:00:00.000Z", "author": { "name": "Daniel Cumming-Potvin", "url": "https://www.linkedin.com/in/daniel-cumming-potvin-13a581121/" }, "tags": [] }, { "id": "https://es.mxrap.workers.dev/updates/filter-volumes-library-changes", "content_html": "

We have recently updated the JavaScript library mxjs/base/algorithms/filter_volumeset.js to be more efficient. If you are using this library and call the flag_members() method of volume sets directly, then you will need to update your code slightly. If you don't call flag_members() directly then you'll automatically get the efficiency updates when you upgrade without needing to do anything, and you can stop reading now :)

\n\n

Previously code would create a finder object from the mxjs/base/algorithms/find_neighbours_3d.js library like so:

\n
const VolumeSets = require.mx(\"mxjs/base/algorithms/filter_volumeset.js\");
const Finder = require.mx(\"mxjs/base/algorithms/find_neighbours_3d.js\");
const finder = new Finder(Blasts.size(), Blasts.read_Location);
\n

And then pass it to the flag_members() method:

\n
volume_set.flag_members(flags, is_ticked, Blasts.read_Location, finder, null);
\n

With the updated library you should remove find_neighbours_3d.js and instead create a finder object like so:

\n
const VolumeSets = require.mx(\"mxjs/base/algorithms/filter_volumeset.js\");
const finder = VolumeSets.create_finder(Blasts.read_Location, 0, Blasts.size());
\n

And then pass this finder object to flag_members() in the same way as above. For the moment the old style is deprecated but will continue to work, so your code will not break, but in the future we will remove support for the old style.

", "url": "https://es.mxrap.workers.dev/updates/filter-volumes-library-changes", "title": "Filter volumes library changes", "summary": "We have recently updated the JavaScript library mxjs/base/algorithms/filtervolumeset.js to be more efficient. If you are using this library and call the flagmembers() method of volume sets directly, then you will need to update your code slightly. If you don't call flag_members() directly then you'll automatically get the efficiency updates when you upgrade without needing to do anything, and you can stop reading now :)", "date_modified": "2024-05-03T00:00:00.000Z", "author": { "name": "Matthew Heinsen Egan", "url": "https://www.linkedin.com/in/matthew-heinsen-egan/" }, "tags": [] }, { "id": "https://es.mxrap.workers.dev/updates/changes-to-root-structure", "content_html": "

There has been some rearrangement to the ! folder within the root folder, which may affect some of your apps. This was primarily a move of tools which are not seismic specific from the ! folder to !/Base (so that mines without the seismic module can use these tools). The most commonly used parts of this migration are anything that uses Filter Volumes, Grid definitions or Plane definitions.

\n\n

Apps that you created that are being used on site will break as a result of these broken connection in upgraded root folders. As we transition to v6 of mXrap, root upgrades will be required, and any of your custom apps will require fixing. To rectify missing sources, you can either manually change links (on an updated root folder) from the old to the new location, or use mXrap's redirect source/table/column feature in the menu bar of the Settings window:

\n
\n

The moves are as follows:
\n!/Filter Volumes -> !/Base/Filter Volumes
\n! Standard Data/File Locations -> !/Base/Standard Data/File Locations

\n

Some of ! Standard Data/Parameters -> !/Base/Standard Data/Parameters , including:
\nFilter Volumes
\nGrid Definitions
\nPlane Definitions
\nImport/Filer Volumes Auto-ID
\nImport/Filer Volumes CSV
\nImport/Filer Volumes Staging
\nImport/Grid Definitions Auto-ID
\nImport/Grid Definitions CSV
\nImport/Grid Definitions Staging
\nImport/Plane Definitions Auto-ID
\nImport/Plane Definitions CSV

\n

A summary of the new locations are shown below

\n
", "url": "https://es.mxrap.workers.dev/updates/changes-to-root-structure", "title": "Changes to root structure", "summary": "There has been some rearrangement to the ! folder within the root folder, which may affect some of your apps. This was primarily a move of tools which are not seismic specific from the ! folder to !/Base (so that mines without the seismic module can use these tools). The most commonly used parts of this migration are anything that uses Filter Volumes, Grid definitions or Plane definitions.", "date_modified": "2024-02-01T00:00:00.000Z", "author": { "name": "Daniel Cumming-Potvin", "url": "https://www.linkedin.com/in/daniel-cumming-potvin-13a581121/" }, "tags": [] }, { "id": "https://es.mxrap.workers.dev/updates/changelogs/mxrap-6-0-0", "content_html": "

Highlights​

\n

We're pleased to announce the release of mXrap version 6, bringing with it a range of enhancements to elevate your mXrap experience. This major update includes improvements to the user interface, as well as enhancements to speed when loading the root folder and applications. Additionally, we've upgraded the 3D rendering and navigation capabilities in the 3D Views.

\n\n
\n

New: Tilt View and automatic grid

\n

However, it's important to note that older root folders may not function properly in version 6 due to incompatibilities. Therefore, it's crucial that all root folders and apps are upgraded and checked to ensure they work correctly before transitioning. If you haven't received communication about this upgrade yet, expect an email in the coming weeks with instructions on how to complete the process.

\n
precaución

Please be aware that mXrap version 5 is scheduled to cease functioning in May 2024. Your cooperation during this transition period is greatly appreciated and will help facilitate a smooth migration to the new version.

\n

The notable changes that would effect development includes the change in scope for Table Calcs and data structure changes (octal literals, null locations, etc.). These changes mean that some Table Calcs or Row Calcs may break. Please read the change logs on how to address this.

\n

What's new for Users - mXrap 6.0.0​

\n

Last update: 14 November 2023

\n

Introduction​

\n

Short story: Ask the mXrap team to upgrade your root folder, and then you can install and use Version 6. Be sure to check any site-specific Apps that you have in your root.

\n

Version 6 is intended to be backwards and forward compatible with Version 5. This means you can switch between Version 6.0 and Version 5 without compatibility issues.

\n

Version 6.1 will bring changes that are incompatible with Version 5, so please help us upgrade you to Version 6.0 soon so we can ensure any problems are fixed before we move onwards into the future.

\n

Contact support if you require a root folder upgrade, or help upgrading your own Apps.

\n

Operating System Support​

\n

Full support for Windows Server 2022+ and Windows 10+

\n

We are unable to fully support old operating systems such as Windows Server 19, Windows Server 16 and Windows 7. Many IT departments will be running Windows Server 16 on their Virtual Machines, so this could be an issue at some sites.

\n

The simplest way to check if your computers are supported, is to run mXrap v6 and try it out. If mXrap detects problems, it will tell you.

\n\n

CodeMeter Update - 7.60d​

\n

WIBU recently announced a software update to address a CVE security issue (Common Vulnerability and Exposure) that relates to an exploit available from the SOCKS5 proxy. You may not have such a proxy configured, but in theory, Malware could use this issue as part of a combined attack.

\n

https://cdn.wibu.com/fileadmin/wibu_downloads/security_advisories/AdvisoryWIBU-231017-01.pdf

\n

The solution is to upgrade the CodeMeter Runtime to the latest version. A link to the latest version of the CodeMeter Runtime can be found here:

\n

https://downloads.mxrap.com/Dongles/CodeMeterRuntime.exe

\n

or here: https://www.wibu.com/support/user/user-software.html

\n

mXrap Optimisations​

\n

We've made many improvements to the way we load the Root folder and files from disk. Our developers have been using Version 6 Beta for months, and the speed difference alone is such that we don't like switching back to Version 5. We hope you will also find Version 6 faster in your environment.

\n

Improved Display​

\n

mXrap now works properly on higher resolution monitors. Version 5 relied on automatic scaling, so it could appear fuzzy and out of focus. Version 6 is now crisp and sharp.

\n

We have also changed the GUI styling of mXrap (e.g. the buttons and spacing look different). We aren't happy with the current state and hope to make some more changes in this area.

\n

Note that the fixed-width font (used for numbers) has changed to the newest Microsoft font: \"Cascadia Mono\". As a result, the width of columns and text might be different to before, and column widths may need to be adjusted. Depending on your operating system, you may have been using Courier New or (more likely) Consolas in the past.

\n
\n

mXrap Tips​

\n

We have now added some helpful tips in mXrap. Try clicking the ? buttons to view the tips.

\n
TipsLocation
3D Tips
Chart Tips
Tableview Tips
\n

3D Navigation​

\n

Version 5's 3D View could be confusing when looking at a plan view of your mine. Dragging the left mouse button up and down would rotate the view in such a way that your mine would end up sideways.

\n

Starting from Version 6, dragging the view up and down will always rotate the mine vertically between a plan view and a section view.

\n

Dragging the mouse side to side will always rotate the mine around the vertical axis.

\n

To make navigation easier, you can:

\n\n
NavigationDemonstration
Rotate the View:
Mouse side-to-side

Force Rotation:
Shift + Drag
Tilt the View:
Mouse up-and-down

Force Tilt:
Shift + Alt + Drag
Gridlines rotate with the View
\n

Improved 3D View​

\n

We've made an update to mXrap that improves several aspects regarding its display. A short list of the changes can be seen below.

\n\n
Select and Highlight Vertices in a Surface or Line Series in 3D
\n\n
Control
Depth Peeling Controls in the 3D Panel
Global controls that affect all 3D Views
Depth Peeling Off
Depth Peeling On
\n

Improved Marker Symbol Dialog Box​

\n

While choosing a Marker Style symbol, you can preview all symbols in a chosen colour.

\n
Style
Choose a Symbol
Preview in different colours
\n

Local Cache Changes​

\n

mXrap keeps a copy of a lot of data in your \"User Profile\" folders on the C: system disk. This can be problematic if your C: is running low on disk space.

\n

You have always been able to choose another location to store this cache (e.g. on a larger data disk), however, Version 5 still stored quite a lot of stuff on the C:

\n

Version 6 will now store all of its Cache where you choose, and, it will also detect and clean up unused cache files left behind in your User Profile.

\n
Cache
Access the Settings
Change the Location of the Cache

You will need to choose your root folder again
Old cache auto-detected
Clearing old Cache files
\n

File Path Update​

\n

mXrap now supports more special characters, white spaces in file paths and deeper folder paths. Stricter file naming is also enforced.

\n

If you have any issues regarding any special characters, please try to use plain ascii instead and let us know via support.

\n

Credentials Pop-Up​

\n

mXrap may read files from network drives, such as seismic event files. The username/password credentials for these network shares are sometimes forgotten by Windows, and mXrap Version 5 would fail to access the file and not tell you that there was a problem.

\n

As of Version 6, mXrap will ask the user for the username and password if the Network share needs the credentials.

\n

App Translations​

\n

We've implemented a language translation system for translating Apps into different languages.

\n

You can choose the language mXrap uses via the About dialog.

\n
Translations
Click \"About mXrap\"
Choose a Language
\n

The current languages available for mXrap include English, Spanish, French, Portuguese and Swedish.

\n

We have only just started translating some Apps. If you are interested in contributing to the translations, please let us know.

\n
Examples
English: General Analysis
Français: Analyse Générale
\n

What's new for Developers - mXrap 6.0.0​

\n

Last update: 14 November 2023

\n

Introduction​

\n

We are pleased to announce the first release of version 6 of mXrap!

\n

Version 6 is intended to be backwards and forwards compatible with Version 5. This means you can switch between Version 6 and Version 5 without compatibility issues. You can develop Apps in Version 6, and deploy to a Version 5 site, and everything will work. Almost.

\n

You do need to upgrade the root before using Version 6 (see the \"Migration Guide\" for more information) and you need to avoid some new features while it can be used with Version 5.

\n

The mXrap team's standard code in your root folders has been upgraded, so ensure we have upgraded your root folder BEFORE you start using Version 6. Contact support if you require a root upgrade, or help upgrading your own Apps.

\n

Hotkey to Save​

\n

You can now save tools with Ctrl + S.

\n
\n
\n

Tab Icons​

\n

You can now add icons to tool tabs.

\n
\n

Inline CSS for Panels, Headers and Footers​

\n

You can now use inline CSS to style your text as HTML using CSS selectors.

\n

You can use this technique in places such as:

\n\n

Note for Panel Views: Some CSS techniques cannot be done via the \"Stylesheet (CSS)\" tab, and must be done using inline-CSS.

\n
Examples
HTML + Inline-CSS
HTML + Inline-CSS in a Header/Footer
HTML + Inline-CSS in a Panel
\n

Example HTML with Inline CSS​

\n
<html>
  <style>
    .title {
      font-weight: bold;

      text-decoration: underline;

      font-size: 20px;
    }

    .sub.title {
      font-size: 14px;
    }

    #keynote {
      color: #006400;

      font-style: italic;
    }

    .keyWord {
      font-weight: bold;

      text-decoration: underline;

      font-size: 13px;
    }
  </style>

  <div class=\"title\">Example Title</div>

  <div class=\"sub title\">Example Sub Title</div>

  <div id=\"keynote\">This is just an <span class=\"keyWord\">example</span>!</div>

  <div>
    This is an <span class=\"keyWord\">example</span> on how you can use
    <span class=\"keyWord\">inline CSS</span> to style

    <span class=\"keyWord\">HTML items</span> using
    <span class=\"keyWord\">CSS selectors</span>.

    <div id=\"keynote\">
      Note: This is <span class=\"keyWord\">not</span> the full extent of its
      capabilities.
    </div>
  </div>
</html>
\n

Table Calc and Row Calc Update​

\n

Table and Row Calcs have been treated to a very large upgrade.

\n

New Javascript Language Support​

\n

New Engine: We've upgraded our Javascript engine to support the latest version of (JS 2021/2022), allowing for further flexibility in table calcs and row calcs. Please note that these new features will not be compatible with mXrap v5, so only use them once the users of your apps have been upgraded to v6.

\n

mXrap supported ECMAScript 5. Version 6 brings support for the following language changes:

\n\n

Access more RAM in your Calculations​

\n

mXrap is now able to support bigger memory allocations. You create a shortcut to the mxrap.exe and add these to the command line parameters.

\n\n

Where N is the size you want to specify for memory allocation, in Gigabytes.

\n

Example - add the following to the back of a shortcut in the target section:\n--js_max_all_buffers_gb=8 --js_max_per_buffer_gb=4 --js_max_native_gb=4

\n
\n

Storing Data files and CSVs in Bundles​

\n

The \"Bundle\" feature allows developers to put their Apps in a protected and controlled package that is ideal for deployment.

\n

One problem in the past was distributing and reading fixed data files - e.g. tables of mathematical constants for computation.

\n

The solution was to store the CSV files outside the bundle, but that was annoying to deploy.

\n

Version 6 adds the ability to store CSVs inside bundles like any other tool. You can import that CSV with an ImportCSV tool from within the same bundle, or, mark that file for \"Export\" to read that file from outside the bundle.

\n

Please note, you will need to manually set the Input File path to the CSV, as the \"Browse\" button does not list files within Bundles.

\n

mXrap Developer Migration Guide: Version 5 to 6.0.0​

\n

Last update: 13 November 2023

\n

Introduction​

\n

Short story: Ask the mXrap team to upgrade the root folder, and check your own Apps for the problems described below.

\n

Version 6 is intended to be backwards and forward compatible with Version 5. This means you can switch between Version 6 and Version 5 without compatibility issues. You can develop Apps in Version 6, and deploy to a Version 5 site, and everything will work.

\n

We almost achieved that goal.

\n

The new Javascript engine in Version 6 delivers \"ECMAScript 6\" support, which brings changes to the way the JS language works. Your Javascript code MAY require changes to work in Version 6.

\n

The mXrap team's standard code in your root folders has been upgraded, so ensure we have upgraded your root folder BEFORE you start using Version 6. Contact support if you require a root upgrade, or help upgrading your own Apps.

\n

Returning Points in a Row Calculation​

\n
Guide
Screenshot
Codereturn [1,2,3];
Warning MessageWARNING: use the provided 'result' variable to return array results for efficiency.
SolutionA \"result\" variable is automatically provided. Fill it with the results and return it, like so:
result[0] = 1;<br/>result[1] = 2;
result[2] = 3;
return result;
Reasonreturn [1,2,3]; creates an unnecessary Array - this is slower and consumes more memory.We want to encourage good consistent coding practices and use the same code pattern everywhere.
Before
After
\n

Returning Null Points​

\n
Guide
Screenshot
Codereturn [null,null,null];
Warning MessageWARNING: do not return [null,null,null], instead return null
Solutionuse instead: return null;
ReasonNull coordinates are now specified as null instead of [null,null,null]. This is more efficient and simpler to code, as there is no Array involved.
Before
After
\n

Checking Null Points in a Row Calculation​

\n
Guide
Screenshot
Codeif(override[0] == null || override[1] == null || override[2] == null)
Warning MessageTypeError: Cannot read properties of null (reading '0')
Solution for Version 6 only. This is the future: use this if you don't need to support users on Version 5.Use instead: if(override === null)

Note the use of 3 = signs, not 2.
=== compares both type and value: you want this!
== will do conversions and may not do what you expect.
Backwards Compatible Solution for both Version 5 and 6use instead: if(override === null || override[0] == null || override[1] == null || override[2] == null)

Tip: add override === null to the front of the if statement.
ReasonNull coordinates are now specified as null instead of [null,null,null]. Thus the check should be much simpler, as there is no Array involved anymore.
Before
After
\n

Octal Literals​

\n
Guide
Screenshot
Codenew Date(2023,10,01);
Warning MessageWARNING: Program failed to compile

SyntaxError: Octal literals are not allowed in strict mode.
Solutionuse instead: new Date(2023,10,1);
ReasonThe new Javascript does not accept numbers written with a leading zero, eg 01 or 02. These are known as Octals, and were a common source of confusion i.e. 08 and 09 are invalid, and 010 translates to 8 in decimal. This was a source of bugs, so Octals are disallowed as a blanket policy.
Before
After
\n

Problems with Omori Library​

\n

Similar errors are seen as ReferenceError: something is not defined

\n
Guide
Screenshot
Error MessageReferenceError: results_best is not defined
SolutionThis requires a root upgrade for a newer version of this library. Contact support to arrange a full root upgrade.
ReasonWe have tightened up \"global scoping\" rules for better coding practices. In Version 5, scripts imported via require.mx() could access global variables defined in the main calculation code. This is bad practice and is no longer allowed.
\n

Table Column Widths​

\n

Note that the fixed-width font (used for numbers) has changed to the newest Microsoft font: \"Cascadia Mono\". As a result, the width of columns and text might be different to before, and column widths may need to be adjusted. Depending on your operating system, you may have been using Courier New or (more likely) Consolas in the past.

\n
", "url": "https://es.mxrap.workers.dev/updates/changelogs/mxrap-6-0-0", "title": "mXrap 6.0.0 - Release notes and Changelogs", "summary": "Highlights", "date_modified": "2023-11-14T00:00:00.000Z", "author": { "name": "mXrap Team", "url": "https://mxrap.com/team" }, "tags": [ "Changelogs", "Developers", "Updates" ] }, { "id": "https://es.mxrap.workers.dev/updates/developers/developer-updates-august-2023", "content_html": "

Recent updates which may be of interest to developers

\n\n

Inspection Reports (July 3, 2023)​

\n

mXrap's Inspection Reports now support multiple report types, allowing tailored reports for various needs.

\n

Improved DXF Export (July 31, 2023)​

\n

We've improved the DXF export libraries, ensuring better compatibility with AutoCAD and Gem4D.

\n

Transparency in Bundles (August 21, 2023)​

\n

Most tools in the Seismic module bundles are now visible and can be temporarily edited, which offers increased transparency for developers and power users. Please note that the tools which allow connections from external apps is still limited to a specific subset.

", "url": "https://es.mxrap.workers.dev/updates/developers/developer-updates-august-2023", "title": "Developer Updates - August 2023", "summary": "Recent updates which may be of interest to developers", "date_modified": "2023-08-30T00:00:00.000Z", "author": { "name": "Liam Niedzielski", "url": "https://www.linkedin.com/in/liamniedzielski/" }, "tags": [] }, { "id": "https://es.mxrap.workers.dev/updates/some-mxmas-fun", "content_html": "

With the holidays approaching we thought we would send everyone some mXmas presents! And obviously what everyone wants for mXmas are mXrap videos ?. These videos are not geotech related but come from various games, generative art, or physics simulations that we have made for fun.

\n\n

The mXrap team wishes everyone well for the holidays and a happy new year. Please be aware that the mXrap offices will be closed between December 23 and January 9. We will still be able to provide limited support during this period but there may be some longer than normal delays.

\n

Now, onto the videos…

\n

Rock Paper Scissors​

\n

This is a Rock - Paper - Scissors simulation where players randomly walk through the space and do battle when they come within a certain distance of one another. The losing player becomes a new member of the winners' team. There are several ups and downs with the numbers in each team over time. There are some interesting dynamics since as one team gets low in number, it affects the encounter probability to the other teams. But anyway, place your bet and play the video to see if you've won!

\n
\n

As a fun bonus, here is another version with a more geotech flavour. Welcome to Ground Support - Rock Fall - Bogger. In this version, Ground Support stops Rock Fall, Rock Fall buries Bogger, and of course the pesky Bogger destroys Ground Support. Place your bets and don't let your geotech feelings bias you ?.

\n
\n

3D Cellular Automata​

\n
\n

Cellular Automata are processes that can generative highly complex patterns from simple cell-based rules. In a 3D grid, cells are born and survive based on the status of their neighbouring cells. Different cell rules can have very different results, generating rapid expansion, slow decay, or steady-state behaviours. Cellular Automata can be used to simulate various real-world biological processes.

\n

This next video has some Sierpinski triangle vibes. It uses cell rules based only on neighbours that share a face (up to 6). The rules for the first video were based on all neighbours in the surrounding 3x3 box (up to 26).

\n
\n

Chladni Patterns​

\n
\n

Chladni Patterns are formed by sand or metal filings on a plate vibrating at various frequencies. A 2D standing wave pattern is formed and the particles settle in areas where the vibration is cancelled out. This video simulates several Chladni patterns increasing in vibration frequency. Particles randomly move a distance relative to the amplitude of the vibration at that location. If a particle falls off the plate it is replaced at a random location.

\n

Diffusion-Limited Aggregation​

\n
\n

Diffusion-limited aggregation can be used to model various fractal growth processes. There are several real-world examples such as crystal growth, lightning paths, coalescing dust and snowflakes, plant branching, and even mineral deposits. New particles are added to the space and randomly walk until they come within a certain distance and stick to the existing structure. Different patterns can be made based on the starting structure and where new particles are added in the space. In the video above, a circular ring is added as the starting structure and new particles are added at a random place in the circle (although not too close to the existing points).

\n

The same process can be extended to 3D space. The video below starts with points at the bottom of the cube and new particles are added from the top. The pattern formed is a lot like the growth of a forest. As some structures grow higher they start to block other structures below (like blocking sunlight) and grow even faster.

\n
\n

Slime Mould Simulation​

\n
\n

Slime mould (Physarum polycephalum) is widely studied as it has no brain and yet can grow and make decisions to find food and even solve mazes. The growth behaviour can be simulated with an agent and trail system. Agents (particles) deposit chemicals as they move across the trail. An agent may continue straight or rotate left or right depending on the concentrations of chemicals it senses ahead. The chemical concentration on the trail diffuses and decays over time. Different transport networks develop over time as the agents paths interact.

\n

Ant colonies can be modelled in a similar way. Ants don't have the memory to know where home or food sources are, but they follow different pheromones left by other ants. Ant colony simulation will be a nice future project ?.

\n

Epicycles​

\n
\n

Epicycles are radially connected circles that rotate at different frequencies. The radius and frequency of each circle comes from a Fourier transform of the input line. Any continuous line can be represented with epicycles, even an mXmas message…

\n
", "url": "https://es.mxrap.workers.dev/updates/some-mxmas-fun", "title": "Some mXmas fun", "summary": "With the holidays approaching we thought we would send everyone some mXmas presents! And obviously what everyone wants for mXmas are mXrap videos ?. These videos are not geotech related but come from various games, generative art, or physics simulations that we have made for fun.", "date_modified": "2022-12-19T00:00:00.000Z", "author": { "name": "Stuart Tierney", "url": "https://www.linkedin.com/in/stuart-tierney-2275a563/" }, "tags": [] }, { "id": "https://es.mxrap.workers.dev/updates/fun-and-games-with-mxrap", "content_html": "

If you were wondering what a bored Xman does in their free time, this might give you an indication.....

\n

You should know by now that mXrap is very flexible and apps can be developed to perform a very wide range of functions. If you were doubting that, this might change your mind :)

\n\n

Ever played the puzzle game known as 2048? Well now there is an mXrap version!

\n

The mXrap version has buttons for each of the four moves (up, down, left, right) which controls the game board in the 3D View.

\n
\"2048\"
2048
\n

If 2048 is not your cup of tea, how about a spot of backgammon? This is two player and each player rolls the dice and selects where to go from the list of possible moves.

\n
\n
\"Backgammon\"
Backgammon
\n

Both of these games were built using the beta version of mXrap so we can't send them to you just yet. Once the Beta version is stable we'll upload the games to mXsync for you to play around with. It will be good motivation for you to learn mXsync :).

", "url": "https://es.mxrap.workers.dev/updates/fun-and-games-with-mxrap", "title": "Fun and games with mXrap", "summary": "If you were wondering what a bored Xman does in their free time, this might give you an indication.....", "date_modified": "2018-04-16T00:00:00.000Z", "author": { "name": "Stuart Tierney", "url": "https://www.linkedin.com/in/stuart-tierney-2275a563/" }, "tags": [] } ] }