You can specify a gamma scale factor for each bit run in Mezintel Gamma using a new built-in tool that helps you derive scale factors.
You can enter a scaling factor if you know it, otherwise, if you are unsure then you can calculate or find it from the Bit Runs window:
- In the Scale section under the bit run you want, double-click the value box for Gamma Scale Factor
→ The Get Scale Factor window opens
You may also click the … button to open up Get Scale Factor window.
Have you ever edited a log plot header to meet a requirement only to find yourself (or your colleagues) re-editing it several times to meet different requirements?
To make your work easier, you can now save multiple plot headers for the same job in Mezintel Gamma!
In Mezintel Gamma, samples points logged when the drill bit is ‘off-bottom’ are not shown on the plot. This is useful because it allows you to safely remove points from the plot by manually setting them to be off-bottom. This hides the points rather than delete them. The hidden points can be revealed again by reverting them back to be ‘on-bottom’.
Mezintel Gamma continuously sends out data to depth tracking EDR providers such as:
Pason and RigSense (NOV).
On a regular basis, about every 5 seconds, WITS data packets are sent out as several lines of plain text (ASCII) that are usually comprised of Toolface, Surveys, and Gamma data.
An example of a packet of lines of WITS data.
Notice that a packet of WITS data starts with the symbols && and ends with the symbol !!
As you know, sometimes sample data may go missing for an extended interval of time while drilling continues. In such cases, there is a gap in the sample plot for the depth interval where data went missing.
Up until now Mezintel Gamma used to fill-in (or close) the gap with a straight line. However, some users wanted to control whether or not to show such gaps, so we have provided you with a new option to do just that.
Slow Performance Due to Accumulation of Jobs (more than 5 jobs)
Depending on your computer’s specs, Mezintel Gamma can start to run slow if you have accumulated about 5 or more jobs in addition to the default job templates. Some processes may even fail to complete when you have too many jobs. For example:
- Adding a new job may fail to complete
- Saving tie-in for the Survey Table may return an error
- Adding a new bit run may fail to complete