FAQ

Modifying The Blast Record

When trying to add, delete or change blasts in mXrap, best practice is to use the ‘Blasts Editor’ found under the ‘General Set-Up Windows’ tab: If you need to make bulk changes however, it may be tempting to directly alter the input file in the root folder. Problem: When you open the ‘Blasts.csv’ in MS Excel, it automatically changes the date format and mXrap is no longer able to read the blast information. Solution: Prior to saving the new file, format the Date column to match the input required for your root: yyyy-mm-dd hh:mm:ss.0   This is the typical input format, but you may have to modify slightly in order to match the format for your specific root. This can be done by selecting the Date column, right clicking, and opening ‘Format Cells’. Choose the ‘Custom’ category, and manually enter the input format for your root: To see your changes, save the file and ‘Reload Data’ in mXrap.

Modifying The Blast Record Read More »

What are Bundles?

Bundles are a form of protection which we use to limit access to specific parts of mXrap applications. One of the primary incentives behind the use of Bundles is to reduce the amount of the root folder which is exposed to users for editing. While we encourage users to modify the root folder to suit their specific needs, modifications to core parts of the app can hamper our ability to maintain and upgrade root folders efficiently. Bundles provide us with the flexibility to prevent users from editing important parts of the app while leaving other parts accessible for customisation. This helps us to deliver and upgrade bundled apps much more reliably. Bundles can also be used to provide protection of mXrap’s and other developers’ intellectual property (IP). By being able to lock down important parts of the code using Bundles, it allows us to distribute mXrap to a wider audience without worrying about sensitive IP being exposed. In addition, access to Bundles in mXrap is tied to a user’s license key by a Bundle License ID. This feature allows us to ensure apps are only accessed by the permitted users and cannot be freely distributed. We have begun to roll out the Bundles in two stages. Stage one is to lock everything down and see what no longer works. Stage two involves opening back up again as required. If you encounter limited access to a tool which you believe would be beneficial to either use, view or customise please email us at using the support email. Developer notes – how it works: Bundle settings are defined by a permission file called _mxbundle.mxperms which is stored in each folder. The permission file also affects each subfolder. If there is a new permission file it will override its parent’s settings.The format for a permission file is:      LicenceId, Access, Export     NUM, ACCESS, EXPORT     NUM, ACCESS, EXPORT Where NUM is the Bundle License ID that should be allowed access.ACCESS is either: none, secret, hidden, visible, editable or overridable.EXPORT is either: internal or exported.Different Bundle Licence IDs can be assigned different permissions by adding multiple lines.The behaviour of the different combinations is summarised below. If you are an mXrap app developer and are interested in bundling your own application please contact us at the support email address.

What are Bundles? Read More »

Survey decimation

Are your surveys really slow to load? Are you having difficulty rotating your 3D view? The problem might be the level of detail in your survey files. If the level of detail of survey files is unnecessarily high, it will slow down the 3D view for no reason. This is often the case with stope CMS files. To reduce the level of unnecessary detail in your survey files: Open the survey setup window (can be found in the General Analysis app) and select the surveys you’re interested in (on the left). Click on decimation, then turn on the decimation override using the tick box. Set the Target Reduction. This number is how much mXrap will try to reduce the size of your surveys (i.e. with a Target Reduction of 90%, mXrap will try to reduce the number of points to 10% of the original size). You should set this to as high a number as possible, while still being able to see the level of detail in your surveys that you need (somewhere between 60 and 90% often improves the speed of the 3D view dramatically, without making the surveys look awful). Don’t forget to rebuild the cache and hit save before looking at your 3D view! If you need a refresher on updating surveys, watch the Survey Setup training video.

Survey decimation Read More »

Survey input configuration

Are you unable to see your surveys, but can’t work out why? Are some of your surveys located a long way away from the rest of your mine when they shouldn’t be? This could be due to the input configuration of your survey files. The order of the co-ordinate components (Easting, Northing, RL) are sometimes different for some survey formats, so we have to ‘flip’ the X and Y co-ordinates. This is often the case for DTM files. To fix this: Open the survey setup window (can be found in the General Analysis app) and find the surveys with an issue. Click on input config, then turn on the override using the tick box. Click the swap button between X and Y to change whether X and Y are the first or second column. Don’t forget to rebuild the cache and hit save! If you need a refresher on updating surveys, watch the Survey Setup training video.

Survey input configuration Read More »

What do the hazard iso’s mean?

The Iso View in the Hazard Assessment application expresses the seismic hazard in two ways. The current yearly hazard within the chosen grid volume. This is shown in the footer of the 3D view, as the probability of an event exceeding the design magnitude. The spatial distribution of the hazard. This is highlighted by the hazard isosurfaces. In the case below, the design magnitude is set as ML2. The corresponding hazard isosurfaces for ML2 can be interpreted as the most likely location for that event to occur. The ML rating essentially delineates the areas of the mine from lowest to highest hazard. The volume bounded by the ML2 isosurface indicates the ML rating is above ML2. Note that the colours in the legend are slightly different than the isosurfaces’ apparent colour in the 3D view. This is due to transparency effects and viewing multiple transparent surfaces on top of one another. It is important to note that while the data period can change (6 months in the example above), the hazard calculations are all referring to the yearly hazard. This is a simple matter of normalisation. E.g. if you record 100 events in an area in six months, this area is assigned an activity rate of 200 events per year. The use of yearly hazard is to help interpretation. Reducing the time period used in the definition reduces the probabilistic hazard and this can be misleading. For example, let’s say you give your mine manager a report every day and it says that based on recent data, the probability that we will experience an event in the next 24 hours over ML2 is 0.77%. You do this every day for a year and each day, the mine manager looks at the number and thinks, “Hmm, 0.77%, that’s pretty small, risk is pretty low”. A daily hazard of 0.77% is the same as the yearly hazard in the example above. 1 – (1 – 0.0077)365 = 94% The mine manager may interpret the risk more accurately when presented with the same hazard but expressed for a hazard period that is more intuitive. The current yearly hazard displayed in the footer of the 3D view applies to the entire volume of the chosen grid. We also compute the yearly hazard in the VTM table in General Analysis. So, you might reasonably assume that if you specify a volume in General Analysis the same as the grid volume in the Hazard app, the two numbers should match. In fact, while the probability of exceeding ML2 is 94% in the example above, the same volume and time period in the VTM table gives 86%. This is because the two calculation methods are quite different. To compute hazard, the main inputs are the seismic activity rate, and the b-value (Mmin and MUL are also required). In the VTM table, a single b-value and activity rate is computed for events within the volume, and the seismic hazard is computed directly. In cases where the b-value does not vary significantly within the volume, this is a reasonable approach. However, in most cases, the b-value varies in space, and this approach tends to underestimate the seismic hazard. This is illustrated in the figure below. You can represent the full volume with its activity rate and b-value to compute the probabilistic hazard, like in the VTM table. In the Hazard app, the variations in activity rate and b-values are calculated on a regular grid through space (in sub-volumes). While the event search radius for each grid point may exceed the grid cell spacing, the activity rate is normalised and the b-value is assigned to represent the seismicity for the specific grid cell volume. The probability of exceeding the design magnitude within each sub-volume can then be calculated. Then the probabilistic hazard for the full volume can be calculated by integrating together all of the sub-probabilities. ML Rating – Technical Meaning As mentioned already, the yearly seismic hazard is expressed as the probability of exceeding the design magnitude. An alternate definition of hazard, is to use a design reliability rather than a design magnitude. I.e. the hazard can be expressed as the magnitude that, to the design reliability, will not be exceeded. We use a reliability of 85%. The ML rating is the design magnitude that would have a probability of exceedance of 15%. An ML rating is assigned to each grid point to compute the isosurfaces. On the surface of the ML2 iso for example, the ML rating refers to the magnitude that, to a reliability of 85%, would not be exceeded within the standard volume given one year’s seismicity. The standard volume we use is that of a sphere of 50m radius.

What do the hazard iso’s mean? Read More »

What are minodes?

Minodes are what we use in multiple places in mXrap if we want to assign information to development. They are just point locations, dotted along your development, in roughly 5m intervals. Things like ground support and PPV hazard are really only relevant for development locations, so minodes are our way of denoting these places. Minodes are also used to calculate the span of the excavation at that point. The tunnel length is also used in the Hazard Assessment app. Minodes are not generated automatically for new development. The minode calculations use an older generation of code that can’t be used in the current mXrap. So, we need to generate the minodes for you periodically as you add more development. Minodes can be created from floor strings but 3D development surveys work best, the same formats you use for mXrap.   Minode Update Procedure  Add your most recent 3D development surveys to the #Data folder in your root. Include all surveys where you want to show minodes, even if minodes are already there. Run a default backup of your root folder in mXsync. If you are unsure how to do that, review the “Intro and Default Backup” video on the mXsync page.  Send an email to our support email address and ask us to update your minodes. Please confirm that you have updated your surveys, run a backup in mXsync, and indicate which surveys are for minode generation. It can take some time depending on other work, so please indicate if it is especially urgent. We will generate your new minodes and merge all previous information from the old minodes. We will let you know when it’s done via email. Your new minodes will be sent as a patch in mXsync back to you. All you need to do is apply the update. See the “Apply patch” video on the mXsync page. Review your new minodes (in the Hazard Assessment app for example) and confirm they are as expected. Then run another default backup in mXsync if you are happy. Contact support if there are any problems.

What are minodes? Read More »

What on Earth is MUL?

Yes, this is a frequently asked question…. MUL or MUpper-Limit refers to the truncating magnitude of the Gutenberg-Richter distribution. We used to refer to this as Mmax in the Hazard Assessment app and on the frequency-magnitude chart but we found there was confusion caused by Mmax being used to describe multiple things. Hopefully if we refer to MUL or the upper-limit magnitude, this will clear up the terminology a little. A quick review on the terminology that concerns the frequency-magnitude chart and the Gutenberg-Richter distribution: Mmin – The magnitude of completeness, the dataset is considered complete above this magnitude (property of the data). b-value – The slope of the Gutenberg-Richter distribution, describes how the frequency of events scales with magnitude (property of the statistical model). Xmax – The largest magnitude event in the dataset (property of the data). a/b – The magnitude at N = 1 of the Gutenberg-Richter distribution (property of the model, maximum likelihood, see previous blog post). max(m,n) – This is the probability density function, given n events, of the largest event in that n events. This is a property of the Gutenberg-Richter statistical model. In other words, given a certain Gutenberg-Richter model, if you record N events, what is the largest event? This is not a single number but a likelihood distribution. The maximum likelihood of the largest event is the a/b value. MUL – The upper-limit magnitude of the max(m,n) distribution. It is an estimate only and a property of the statistical model. The truncating magnitude has slightly different meanings in mining seismology and crustal seismology. MUL is usually referred to as Mmax in crustal seismology literature and is generally considered constant for a particular area. In mining seismology MUL generally increases over time given the gradual increase in mining dimensions and loading of the rock mass. For this reason the definition is slightly modified in mining seismology to be the upper limit of the next largest event. Why do we need an upper-limit or truncating magnitude? The truncated Gutenberg-Richter distribution, rather than the open-ended distribution, is the most common frequency-magnitude relationship used in mine seismology. If there is no upper limit given to the Gutenberg-Richter distribution, then to evaluate the total energy of events in the relevant time period, the energy tends to infinity as the relationship is integrated above Mmin. This is clearly unrealistic. We know there is a physical limit to possible magnitudes since the size of large earthquakes is related to the slip area of the fault and the physical size of faults is limited. Earthquakes on Earth above magnitude 10 (Richter) are essentially impossible given the size of known faults and a magnitude above 12 represents a fault area larger than the Earth itself! So it is safe to say that MUL for a particular mine is going to be less than Richter Magnitude 10. The question is how much less is reasonable given the significantly reduced physical dimensions in mining. How do we estimate MUL? An empirical method of estimating MUL can be taken using a dataset compiled by McGarr et al. (2002) of large events and the largest dimension of the human activity associated with them. The figure on the right comes from Wesseloo (2018) who added a few extra points to the dataset from Australian and Canadian mines. The range applicable to mining indicates rough dimensions between 500 and 5,000m. Aside from the empirical approach, there are also statistical approaches to estimating MUL. These generally take the form: MUL ≈ Xmax + Δ There are a number of different methods for calculating the Δ value. Many of these methods are described by Kijko and Singh (2011). Most of these have been implemented in the Hazard Assessment app along with the associated uncertainty of each method as described by Lasocki and Urban (2011). It is better to over-estimate MUL than to under-estimate it. In terms of probabilistic seismic hazard calculations, the truncated Gutenberg-Richter model will always give a lower hazard result than the original Gutenberg-Richter, for magnitudes approaching MUL. For magnitudes well below MUL, the seismic hazard calculations are the same. In the Hazard Assessment app, we take the maximum of each MUL + σ estimate from multiple methods. These statistical approaches assume the recorded magnitudes of large events are reliable. Moment is under-recorded for large events if there are no low-frequency sensors installed. The figure to the left comes from Morkel and Wesseloo (2017) showing the effect on the frequency-magnitude relationship, given certain sensor bandwidth limitations. In cases like this it is best to override the MUL as it is likely to be under-estimated with statistical methods. Conclusion While it is important to understand what MUL is and how it effects seismic hazard calculations, it is not something to use for design purposes or to communicate seismic hazard. It is just one part of how seismic hazard is defined. By definition, the probability of an event exceeding MUL is zero, so it isn’t a great measure of seismic hazard. If you have any questions regarding this topic, or something to add, feel free to leave a comment or send an email to support.

What on Earth is MUL? Read More »

What survey formats can be imported into mXrap?

mXrap supports the following survey formats to be used in 3D views: DXF (AutoCAD .dxf) DTM / STR (Surpac .dtm/.str) PNT (.pnt) INP (Map3D Geometry .inp files) Regarding DXF files, this is a complicated format that AutoCAD often updates with new specifications. Our importer will always be behind the latest updates and therefore incompatible with loading in the very newest DXF formats. When exporting your survey files, you should have compatibility options for older formats. Look for ASCII DXF options R14 or 2000; these will work in mXrap. Otherwise it needs a bit of trial and error initially. Binary DXF files are not supported. The other option is to use the ODA File Converter. It is free to download and use to convert DWG and DXF files into other formats.

What survey formats can be imported into mXrap? Read More »

What’s the difference between updating the mXrap software and updating the root folder?

Some things you see in mXrap are properties of the software, while other things are properties of the root folder. We often use the software Excel as an analogy. Excel has many built-in capabilities with endless possibilities for creating specific calculations.  The software has powerful capabilities, but without a user constructing the spreadsheet, the power and value are not fully utilised. An Excel user can set up a spreadsheet which, with the required inputs, will provide you with results.  This user can then provide you with that spreadsheet, which you can then use to perform the same calculations with other inputs. mXrap is like the software Excel that provides the basic tools and the applications are like spreadsheets that can be used to perform specific tasks.  Anybody with enough understanding of the software can build their own app which can be shared with others. For example, when you make a chart in Excel, the ‘add chart function’ is a property of Excel. What’s in the chart, what’s on each axis, what colour are the lines, etc are properties of the spreadsheet. mXrap is the same; there is an ‘Add Chart’ function. Every chart in mXrap uses the same tool, but the application configures what’s actually displayed in the chart. mXrap software level changes are things that affect the ‘Add Chart’ function itself. For example, the current mXrap charts only plot data on four axes; top, bottom, left and right. If we were to add more possible axes, like a secondary left axis, this would require a change to the software. It isn’t related to the root folder. Another example is the image capturing tool. This is a feature of every chart, 3D view and table at the software level. If you want an updated Hazard Assessment application, this is like getting an updated spreadsheet. The root folder is essentially a library of data and applications, like a folder full of different spreadsheets and their associated data. To summarise, if it seems like its a common feature across many areas in mXrap, its probably a property of the mXrap software. If it seems to be something related to a specific app or chart, etc, it’s probably a setting in the root folder. Updating the mXrap software is easy, just download the installer from the website. Updating the root folder is what we use mXsync for and it’s actually more complicated to manage the root folder than the software; a bit like trying to manage a lot of interconnected spreadsheets. We normally rely on sites to request root updates. If you read about a feature on the blog or watch a training video that seems different to your current version. You probably need a root update. It’s a fairly quick process, we just need a brief connection with TeamViewer/Webex or GoTo Meeting to perform the update. Contact us at our support email address.

What’s the difference between updating the mXrap software and updating the root folder? Read More »

Why aren’t my events updating?

If you notice that you are not getting updated events in mXrap, there are a few possible explanations. In order to troubleshoot the problem, it is good to know exactly how your events are transferred from your seismic database, into mXrap. The first thing to check is if the events are just being filtered out. In the events table, there is a ‘Show All Rows’ option that will disable all filters and show you every event in the database. Sort by descending time and ‘Reload Data’ and check the latest event time. Cross-check with your seismic processing software to confirm you are definitely missing events. Remember there is a short delay (~5 mins) from events being recorded to appearing in mXrap. If showing all rows unveils your missing events, it’s a filtering issue. Look through the event filters to make sure everything is turned off. It might also be the quality filter. To see what quality settings are applied at your site, refer to the ‘Event Quality Settings’ video. If you have confirmed the events are not updating, go to your root folder and open the #Events Import folder. Inside there will be an all_events and a recent_events evp file (exact folder, name, extension varies slightly between sites). These are the event files that are read by mXrap. Check the timestamp of the recent_events file; it normally updates within five minutes of the latest event recorded. Try opening the file using Notepad. It will be sorted by time so check what the latest event is. If the evp files in the root folder have the updated events, mXrap is not reading the files correctly. Contact our support email address for assistance. evp files are generated by querying the seismic event database. The recent_events evp is normally updated every five minutes and contains the events from the start of the previous month, up to the present. The all_events evp is normally updated every 24 hours and contains all events up until the start of the current month. So there is always up to one month of overlapping events between the all_events and recent_events evp’s. The evp file only changes if there is something to change, i.e. the all_events evp may be checked for updates every 24 hours, but the file may not have any changes for several days or weeks if none of the processing has changed. If the evp files in the root folder have not been updated, the problem lies in how these files are copied into the root folder from your seismic database. This process varies by site, depending on whether you use IMS or ESG as your seismic service provider. IMS sites IMS generate the all_events and recent_events evp files and normally store them on the seismic server share drive (often a Linux samba drive). Hitting ;Reload Data’ in mXrap will copy those evp files (if they’ve changed) into the #Events Import folder in the root. You need to specify the location of the evp files on the network. This setting is in the ‘Config Events Import’ app, usually at the top of the app list (log in as Admin or Super User). In this app you should see the file paths to the all_events and recent_events files. Make sure these file paths are correct and try navigating to the files in Windows Explorer. If you can’t access the files through Windows Explorer, you will need to ask your IT department for help to get access to the network location. There might also be a password required. If there is no password required, but your local machine is not able to access the files (particularly if you have recently updated Windows 10 or are using a new PC), then you may be experiencing this issue relating to accessing unauthenticated shared folders from Windows 10 (or invalid protocol). If you are able to access the evp files on the seismic server, again, check the timestamps and open the recent_events file to see what the latest event is. If these files are up-to-date, it is a problem with the copy-action from the seismic server to the root. Double check the file path in mXrap is correct and try to ‘Reload Data’ again. Contact our support email address for assistance if mXrap events are still not updated. If the evp files on the seismic server are not updated, it is a problem with the IMS query and you will need to contact IMS for assistance. ESG sites We have a purpose built program for querying the ESG seismic database and dumping the evp files into the root folder. The mXrap Export ESG program normally runs on the ESG computer. Check that this is still running. There should be an icon in the system tray. The ESG Exporter needs to know the location of the seismic database mdb file and the location of the #Events Import folder in the root. Try manually running the query from the Exporter window and look for error messages and report to our support email address. Common problems are not being able to write files in the root folder (user permissions), ESG Exporter is out-of-date, or the seismic database mdb has moved or changed format. The flowchart below summarises the troubleshooting process when your events are not updating in mXrap (PDF version).

Why aren’t my events updating? Read More »