Meyer 2012 Meyer 2010 Meyer 2009 Meyer 2008 Meyer 2006 Meyer 2005 Meyer 2003 SE Meyer 2003 Meyer 2001

From:	Bruce R. Meyer, Meyer & Associates, Inc.
To:	Meyer Hydraulic Fracturing Software Users
Subject:	Meyer 2012 Software Suite version 5.70
Date:	December 2011

Dear Users:

We are pleased to announce the Meyer 2012 suite of software version 5.70 dated December 2011.

Meyer 2012 is compatible with 64-bit and 32-bit versions of Windows 7 and Windows Vista, and with 32-bit versions of Windows XP SP3 and Windows Server 2003. The minimum system requirements are listed in Section 1.2 of the User’s Guide. See the Meyer Fracturing Software User’s Guide Section 1.3 for additional instructions on installing the Meyer Software.

To run the software, current users must upgrade their license key by running MKey and opening their company-specific key file (sent separately via email). New users must attach the enclosed hardware license key to their computer.

Meyer 2012 represents over a year’s worth of development, and has a number of exciting new features. Here are some of the highlights. (For details, see the section “Meyer 2012 RELEASE1” below.)

MShale & MFrac

• Midfield Fracture Complexity. In Meyer 2012, MShale has gained the capability to model time dependent midfield fracture pressure decline for the fracture network.

  It has been observed (e.g., Weijers et al. (2002), Weng (1993), and Jacot et al. (2010)) that complex fracture behavior may occur when fracturing highly deviated and/or horizontal wellbores. MShale’s new Midfield Fracture Complexity option enables users to model this behavior using the methodology set forth in Meyer et al. (SPE 140514).

• 3D Wellbore Model. The Meyer 2012 wellbore model has been greatly enhanced to account for wellbores deviating in 3D space. The new wellbore model allows the user to enter 3D deviation data (inclination, azimuth, northing, easting) to accurately describe wells drilled with modern directional drilling techniques.

All Apps

• Native 64-bit Support. The Meyer Software is now available in two builds: a traditional 32-bit build, and a new 64-bit build that runs as native 64-bit executables on operating systems supporting this capability. The 64-bit version of the software is faster than the 32-bit version, and it is capable of handling a much larger amount of data in MView.

  Both versions of the Meyer Software are built from a single code base, so their file formats, preferences, and databases are compatible, and there should be little to no difference in their simulation results. (We have done extensive testing to verify that this is true; see the detailed changelog.)

  Both versions of the Meyer Software are included on the Meyer CD. The Meyer Setup program will automatically install the 64-bit version, rather than the 32-bit version, if it detects that it is running on a 64-bit operating system. (This behavior can be customized by each individual user’s system administrator or IT department.)

• Plot Print Preview. All Meyer plots have been enhanced to support a Print Preview command. This should greatly simplify the task of fine-tuning the layout of a printed set of plots (e.g., it will make it much easier to put text blocks and legends in the exact right spot).

  Additionally, the plots now allow the user to select a printer at Print time using the standard Windows printing workflow, rather than requiring a visit to Page Setup.

• Translated Installer. The Meyer Setup program is now translated (localized) into the same language as the apps on its CD. (For example, the installer for Russian Meyer 2012 will now appear with a Russian user interface.) This corrects a long-standing gap in our support for running the Meyer Software in users’ native languages.

Meyer Data Acquisition

• TCP/IP Data Acquisition. The Meyer Data Acquisition program has been enhanced to allow data acquisition via a direct TCP/IP link (i.e., a link running no particular application protocol but rather simply dumping raw data). This feature should be especially useful when working in newer data vans without a reliable serial port connection.

It is important to emphasize that these are just the highlights, and that Meyer 2012 features many other enhancements, not listed here, that are called out in the detailed changelog. (For example, many input screens have been enhanced with spreadsheets for easier data entry, replacing the old-style individual form controls.) The Meyer 2012 release includes over 135 enhancements and bug fixes. We have put a lot of effort into ensuring its quality and stability, and we hope that you will find it our best release yet.

Please do not hesitate to contact me with any questions.

Sincerely,

Bruce R. Meyer, Ph.D., P.E.
President
+1 (724) 224-1440
meyer@mfrac.com

Meyer 2012 RELEASE1 (Build 5.70.2427)

We are pleased to announce that Meyer 2012 is now available in two builds: a traditional 32-bit build, and a new native 64-bit build. This 64-bit build runs the Meyer Software as native 64-bit executables on x64 versions of Windows 7 and Windows Vista. (#2243)

Both versions of the Meyer Software are built from a single code base, so their file formats, preferences, and databases are compatible. The 64-bit version’s simulation results have been extensively cross-checked against the existing 32-bit (x86) version, and any discrepancies have been noted and corrected during development (e.g., #2592).

The 64-bit version of the Meyer Software is marginally faster than the 32-bit version. Much more importantly, it is capable of handling a much larger amount of data in MView. We are looking forward to the new features we expect to be able to add to future Meyer Software releases now that we have 64-bit support.

Sysadmin’s Corner: Both builds of the Meyer Software are included on the Meyer CD. The Meyer Setup program will automatically install the 64-bit version, rather than the 32-bit version, if it detects that it is running on a 64-bit operating system. To prevent installing the 64-bit version, create a new CD image containing only the 32-bit version (or at least, with the file mfs_amd64.msi removed). Contact Meyer Technical Support if you have any questions.

All Apps

• [Enhancement] Added more settings to the Window | Restore Default Layout command. In particular, this command now resets spreadsheet column positions, splitter positions, and last selected tabs (for input screens with multiple tabs) to their default values, in addition to any settings affected in prior versions. (#2550)

• [Enhancement] All apps with simulators now show the date of the last run output data on the Run menu. (#2562)

• [Enhancement] All Meyer apps now support data entry and text file import using Unicode fullwidth and national digit shapes. This is especially important for users running Chinese and East Asian versions of Windows. (#2569)

• [Enhancement] Many input screens across the apps have been modernized and made easier to use by converting them to use spreadsheets. This especially eases copying, pasting, sorting, and transformation of data in the case of screens with many inputs. (#1961)

• [Enhancement] Meyer Setup is now translated (localized) into the same language as the apps on its CD. (For example, the installer for Russian Meyer 2012 will now appear with a Russian user interface.) This corrects a long-standing gap in our support for running the Meyer Software in users’ native languages. (#2540)

• [Enhancement] Progress bar windows (e.g., for importing a text file) now open on the same monitor as their parent window on multi-monitor configurations. Previously, these windows would open on an arbitrary monitor. (Similar symptoms to #2518, but with disjoint code.) (#2486)

• [Enhancement] The Recent Files list now offers the user a choice about whether to remove an unreachable file from the list, rather than simply removing it. This will help users who try to open Recent Files on flash drives or disconnected network drives (e.g., offline laptop). (#2529)

• [Enhancement] The Units screen now remembers the user’s last selected sort order and scroll position. (#1779)

• [Change] Starting in early 2010, a number of commercial virus scanners began flagging bits and pieces of Meyer Setup (typically the README) as a “generic virus/trojan.” Meyer 2012 Setup has a number of non-functional changes intended to ameliorate this. (#2503)

  It is important to note that none of the affected Meyer-supplied setup discs or packages actually contained a virus; this was purely a false positive caused by automatic virus scanner updates (after our releases) and/or virus scanner heuristics.

  Please report any future virus scanner warnings involving Meyer Setup directly to Meyer Technical Support.

• [Fix] Fixed About box and File menu sidebar text appearance on Windows Vista and Windows 7. By default, this text was black with a black drop shadow, which made it difficult to read. (#2480)

• [Fix] The Simulation Data Windows lost their settings (e.g., column order and column hidden/shown preferences) whenever the user changed the computer’s screen resolution. (#2509)

• [Fix] When error checking screens with multiple tabs (panels), not all tabs were error checked when simply opening and closing the screen. The user had to manually visit each tab in turn to find any errors in the data. This could be very frustrating when trying to track down errors reported by the Run command. (#2542)

Databases

• [Enhancement] New Proppant Database vendor: CRS Proppants. (#2597)

  The databases provided with the software are based on sound engineering practices, but because of variable well conditions and other information which must be relied upon, Meyer & Associates, Inc. and its database suppliers make, no warranty, express or implied, as to the accuracy of their data or of any calculations or opinions expressed therein or derived therefrom. You agree that Meyer & Associates, Inc. and its database suppliers shall not be liable for any loss or damage whether do to negligence or otherwise arising out of or concerning such data, calculations or opinions.

• [Fix] The system database entries for proppants 0000 (100 Mesh Sand for Fluid Loss) and 0001 (20/40 Jordan Sand) contained data that triggered validation errors upon editing these entries in the user database. (#2590)

Plots

• [Enhancement] All Meyer plots have been enhanced to support a Print Preview command. This should greatly simplify the task of fine-tuning the layout of a printed set of plots (e.g., it will make it much easier to put text blocks and legends in the exact right spot). (#2523)

• [Enhancement] Pressing Escape while adding a text block now cancels adding the text block. Previously, there was no way to cancel adding a text block. This fix also applies to most movable objects on the plots, including objects that become movable in Graphical Arrange mode (titles, legends, plot area, etc). (#2465, #2508)

• [Enhancement] The Default Plot Attributes screen now features a “Reset default configuration” button to restore user settings to the program’s initial defaults. Previously, restoring these settings required manually editing the Windows® Registry. (#2497)

• [Enhancement] The plots now allow the user to select a printer at Print time using the standard Windows printing workflow, rather than requiring a visit to Page Setup. (#2448)

• [Fix] Clarified error message when opening files with an invalid plot configuration. (Such files did not normally appear “in the wild,” but they could be generated by users testing pre-release development builds of the Meyer Software.) Previously, trying to open a file with an invalid configuration would fail with the cryptic error message “Unspecified error encountered while reading temporary file.” (#2488)

• [Fix] Fixed access violation crash when deleting an app’s default plot configuration (.plt file, e.g., mfrac.plt) with the app open. This also occurred if the .plt file was locked (e.g., by a virus scanner) while the app was starting up. (#2491)

• [Fix] Fixed confusing user interface: bar charts allowed the user to configure the plot to show Stage Number, Percentage, or Unit Values on the legend, but this option had no effect. This “Chart Legend” option is now disabled for 2D and 3D bar charts. (#2547)

• [Fix] Fixed the occasional appearance of double gridlines (caused by floating point roundoff error) in plots with both left and right Y scales. (#1670)

• [Fix] For plots with hidden information display boxes, clicking and dragging in the upper left corner of the plot’s data area would allow the user to manipulate a phantom drag rectangle. (“Information display boxes” are programmatic readouts of simulator results, e.g., the ISIP readout in MinFrac.) (#2195)

• [Fix] Mouse coordinates on bar charts were displayed using the curve colors, when they should have been using the filled area colors. (#2472).

• [Fix] Mouse coordinates: The text “У(сл)” and “У(сп)” was displayed in the wrong colors for the Russian build. The code to draw the coordinates was assuming that the Russian translations of “YL” and “YR” had the same number of characters as their English originals. (#2470)

• [Fix] Plots containing more than one sub-plot (e.g., MFrac Stress, Width Profile, Width Contours) allowed the user to specify a setting for the Plot Layout option, but then ignored it. The radio buttons for this setting are now disabled. (#2463)

• [Fix] Toggling the Mouse Coordinates in plots containing more than one sub-plot (e.g., MFrac Stress, Width Profile, Width Contours) now keeps the mouse coordinates setting in sync between all the sub-plots. Previously, these plots would show the mouse coordinates on all sub-plots if any sub-plot had them set to “On,” so removing them required manually setting them to “Off” for each sub-plot. (#2608)

Spreadsheets

• [Enhancement] All spreadsheets now have a default (non-blank) value for Alternate background color and Frozen rows background color (under Tools | Options). These options have existed for several releases but the old default values were blank, so most users did not benefit from them. (#2519)

• [Fix] Changing spreadsheet preferences (e.g., row colors) in one app now applies changes immediately across all apps. (#2520)

• [Fix] Copy To Clipboard did not function properly in spreadsheets that were set to Row Select mode (e.g., the new Tubing and Casing Database spreadsheets in MFrac’s Wellbore Hydraulics screen). Instead of copying the whole row, this command would only copy one cell of the row. (#2527)

• [Fix] The Fill Down (Ctrl+D) command would overwrite the data in any selected cells, even those that were supposed to be non-editable (grayed). (#2563)

• [Fix] The Linear Transformation screen now shows only the editable rows from the spreadsheet selection. Previously, this screen would show all selected rows—including non-editable rows—even though its changes only applied to the editable rows. (#2484)

• [Fix] Select All was missing from the spreadsheets’ right-click context menus. (#2521)

• [Fix] Spreadsheets now give the user feedback (e.g., adding or removing rows from the spreadsheet; changing a background color) immediately upon making a change in a drop-down list. Previously, spreadsheets would not react to the user’s input until the user pressed Enter or OK, or moved the selection to another cell. (#2506)

MFast

• [Enhancement] The Base Data screen has been completely rewritten to clarify the operation of this screen and to make the error checking work more clearly and consistently. (#671)

MFrac

Many of the fixes in this section also apply to MShale, MPwri, and MWell.

• [Enhancement] Added buttons to the Casing, Tubing, and Coiled Tubing tabs in Wellbore Hydraulics to access the respective databases. (#2479)

• [Enhancement] The Meyer 2012 wellbore model has been greatly enhanced to account for wellbores deviating in 3D space. The new wellbore model allows the user to enter 3D deviation data (inclination, azimuth, northing, easting) to accurately describe wells drilled with modern directional drilling techniques. (#1724)

  The new code supports the five standard methods for wellbore surveying calculations:

  1. Average Angle Method

     This method models the well path between two stations as being along a straight line whose length is the measured depth difference between the two stations and whose inclination and azimuth angles are the average of the stations’ values.

  2. Balanced Tangential Method

     This method models the well path between two stations as two line segments, each having a length that is half the measured depth difference between the stations. The first segment has the inclination and azimuth angles of the first station, while the second segment has those of the second station.

  3. Minimum Curvature Method

     This method is a refinement of the Balanced Tangential Method where the two line segments are replaced by a circular arc lying in the same plane as the line segments, but where the arc length is equal to the difference in measured depths of the stations. The Meyer implementation is based on the formulation of Sawaryn et al. (See SPE 84246.)

  4. Radius of Curvature Method

     This method models the well path between two stations as a circular arc lying on a vertical plane which is then curved along a horizontal circular arc.

  5. Tangential Method

     This method, like the Average Angle method, models the well path between two stations as being along a straight line whose length is the measured depth difference between the two stations. In the Tangential Method, this line’s inclination and azimuth are those of the second station only.

• [Fix] Fixed an off-by-one error in the simulator where the stage properties from the n+1th stage could be used to compute bottomhole data. (#2558)

• [Fix] Fixed excessive padding inside the legend border when printing plots when the plot windows were set to a very small size on the screen. (Example: Reduce MFrac to 200×200 pixels; Tile Horizontally; print all plots.) (#2603)

  The fix for this bug should also make it easier to position legends precisely when printing. The buggy code had a side-effect of guaranteeing that legends would appear in a different place on the printer than they did on the screen, which made the printed copy’s appearance difficult to predict.

• [Fix] Fixed erroneous Tab key behavior on the Heat Transfer screen with Fluid Inlet set to Surface. (#2462)

• [Fix] Fixed excessively large propped width at closure due to improper extrapolation. (#2591)

• [Fix] Fixed infinite loop (and resulting 100% CPU crash) when printing contour plots with the plot large (e.g., maximized) on the screen and small (e.g., all plots on one page) on the printer. (#2605)

• [Fix] Fixed non-increasing time step and/or time going backwards in the fluid loss layers simulation. (#2557, #2560)

• [Fix] Fixed printing when multiple plots were open and the Graphical Treatment Schedule was in the foreground. (#2525)

  Depending on the exact version in question, this bug typically caused one of the following:

  1. Access violation crash;
  2. Unable to print anything except a single window at a time (like MView #2483, which was fixed in a Meyer 2010 service release);
  3. The options to “print all plots” produce blank pages.

• [Fix] Fixed radio button keyboard navigation on the Auto Design Treatment Schedule. (#2507)

• [Fix] Fixed scaling and other user interface glitches while dragging the Restart Time line in the Graphical Treatment Schedule. (These were more noticeable in Real-Time mode as opposed to Replay mode.) (#2514)

• [Fix] Fixed simulator coding errors which allowed the pay zone location to influence the proppant transport solution. This was mainly noticeable when the pay zones and perf zones were not overlapping. (#2575)

• [Fix] Fixed simulator coding errors which could result in a negative average fracture permeability (and negative fracture conductivity/negative dimensionless conductivity). (#2581)

• [Fix] Fixed spurious concentration spikes in stages with no proppant (caused by floating point roundoff error in stage boundary detection). (#2572)

• [Fix] Fixed total leakoff coefficient (simulator output value) for ellipsoidal fluid loss. Also affects MPwri. (#2593)

• [Fix] Inactive perf zones could influence the Wellbore Hydraulics simulation output. In particular, an inactive perf zone with an invalid center-of-perfs measured depth (that would not pass error checking if the zone were active) could cause incorrect output. (#2526)

• [Fix] In Wellbore Hydraulics, error checking did not always display the appropriate tab (i.e., the tab with erroneous data) when the user selected the Change button. Thus the user could get an error message, select Change, and then be left in an unrelated part of the Wellbore Hydraulics screen with no hint from the program about how to find the erroneous data.

  (Also fixed a similar bug in the Fluid Loss screen.)

  (#2541, #2559)

• [Fix] New MFrac files now default to Empirical proppant settling. The default had inadvertently been switched to Convective Transport since Meyer 2008. (#2604)

• [Fix] Perf zone and pay zone lines did not appear in the plots the first time the simulator was run after an upgrade. Also, if you edited the zone depths, the lines would appear in their old locations (which could be outside of the bounds generated by auto-scaling) the next time the simulator was run. After running, the lines would move to the correct locations. (#2602)

• [Fix] Perfs in horizontal wells are now visible on the Wellbore Staging profile plot. (#2546)

• [Fix] On the Heat Transfer screen, the defaults for Base Fluid, Reservoir Lithology, and In-Situ Fluid had inadvertently changed for new files starting in Meyer 2008. The correct defaults are Water, Sandstone, and Light Oil, but in Meyer 2008 through Meyer 2010 these were changed to Binary Foam, Anhydrite, and Medium Oil.

  The same bug also occurred in MPwri’s Thermal Front screen, except that the default In-Situ fluid was supposed to be Water, and had changed to Gas.

  This bug only affected new files. A simple workaround was to check and adjust the settings in the Heat Transfer and Thermal Front screens before running the simulator. (#2606)

• [Fix] The Graphical Treatment Schedule now longer draws grid lines and incoming real-time points underneath the legend, not over it. (#1448, #1450)

• [Fix] The Graphical Treatment Schedule would not show data from MView’s “Additional Parameters” under the following circumstances: (#2545)

  1. Opening an MFrac file before opening the corresponding MView file;
  2. Opening an MView file, opening the corresponding MFrac file, then returning to MView and selecting different Additional Parameters;
  3. Opening MFrac and using the default Most Recently Used file opened by MFrac at startup (i.e., never performing File | Open after MFrac connects with MView).

• [Fix] The Treatment Schedule error checking was broken for negative rate stages when Flowback was enabled. (The error checks were improperly rejecting these stages.) (#2531)

• [Fix] The Wellbore Hydraulics wellbore schematic plot now updates after deleting rows from the Casing, Tubing, and Restrictions tables using the Delete key. (#2230)

• [Fix] Upon opening the Treatment Schedule, the schedule would delete any proppant codes that didn’t have a corresponding entry in the user database. When this happened, it was impossible to tell what proppants had been used in the file before the Treatment Schedule deleted them, creating a chicken-and-egg problem for anybody trying to recover the file to its original state. (#2517)

  Normally this bug had little impact because .mfrac files carry copies of any proppant database entries used in their Treatment Schedule, and these entries are automatically imported into the user database upon opening the file. However, the bug could cause trouble in two common scenarios:

  1. The relevant database entries were deleted with the file open, and the file was subsequently saved;
  2. User running with a read-only proppant user database.

• [Fix] Wellbore Hydraulics did not recalculate the Wellbore Reference Depth and BHP Reference Depths if the user changed the data in the Deviation table, then immediately closed the Wellbore Hydraulics screen without looking to see if the depths had been properly recalculated. (#2589)

• [Fix] When the Wellbore Hydraulics injection method was set to Annulus, the simulator was not error checking the Tubing table. This caused an access violation crash if the Tubing table happened to be empty in a case with injection down the annulus. (#2539)

MinFrac

• [Enhancement] Overhauled the user interface layout for the Step Rate “Enter ΔP Fric and ΔP Frac” screen. (#1660)

• [Enhancement] Removed pressure curve data based minimum and maximum value constraints from items in Edit Selections (especially the Slope Lines points) where basing the minimum and maximum values on the pressure curve data was not helpful. (#2614)

• [Enhancement] The Simulation using History Match Data screen now highlights any cells with different values compared to Simulation using Base Data. (#2516)

• [Fix] After importing a file in Data | Options, the History Match Data toolbar icon remained disabled until the user closed and reopened the Options screen. (#2600)

• [Fix] Attempting to pick up a point with the mouse set to Zoom mode, then trying to switch out of Zoom mode using the F4 key (while still holding the mouse button) caused a malfunction. (#2471)

• [Fix] Derivative curves on regression plots could trigger plot scale corruption and/or random memory corruption if there was no data in the curve (i.e., if the curve became empty—for example, by clearing Real-Time data in memory). (#2513)

• [Fix] Fixed an access violation crash when using the “print all plots in all screen windows” command from the Wizard. (This crash was present in all previous versions of the software; however, Meyer 2010 introduced a secondary bug which made the crash impossible to reproduce. The relevant code was corrected in Meyer 2012.) (#2524)

• [Fix] Opening Edit Imported Data would (unintentionally) close the report, but only if one or more plots were also open. (#2515)

• [Fix] Select and Zoom mouse modes were improperly disabled (grayed) in the right-click context menu for the Step Down Diagnostic plot. (#2598)

• [Fix] Switching tabs in the Wizard made the Regression History Match tab forget the user’s settings for the GDK, PKN, and Ellipsoidal drop-down lists. (#2543)

• [Fix] The calculations for the Regression History Match curve were wrong when the input units for Time were set to something other than minutes. (#2582)

• [Fix] The Linear Transformation command was disabled in Edit Imported Data. This command is now enabled. (#2485)

• [Fix] When the user changed the Base Data, the diagnostic plots would not update their information on the plot using the mouse. (#2325)

MProd

• [Fix] Certain spreadsheet columns could interfere with each other in the Design Optimization Data and Multi-Case (NPV) Fracture Characteristics screens. Resizing or moving one such column would cause the other column to be resized or moved upon reopening the screen. (#2556)

• [Fix] Fixed drawing glitch in the “Optimum Fracture Performance Curves” plot legend when unchecking the “Optimum Fracture Performance Curves” option in the Design Optimization simulator. (#2588)

• [Fix] Fixed incorrect simulator error messages for “C_fD number of sub-divisions” and “proppant number of sub-divisions.” (#2494)

• [Fix] The Design Optimization simulator produced incorrect dimensionless fracture conductivity (C_fD) output when the number of sub-divisions exceeded 994. (#2587)

• [Fix] The History Match simulation was not implemented for an unfractured, horizontally oriented well. (#2498)

• [Fix] The Multi-Case (NPV) Fracture Characteristics screen did not recalculate its C_fD values properly on Fill Down, Linear Transformation, Cut, and Paste. The code would only recalculate the value for the first selected row, not any subsequent rows. (#2586)

• [Fix] The Proppant Calculator’s spreadsheet column widths were shared across all apps, but the Calculator screen’s overall size was stored separately per app. Thus the following sequence of steps caused an absurd result:

  1. Make the Proppant Calculator very small in MProd.
  2. Close MProd.
  3. Open MFrac. Make the Proppant Calculator and its spreadsheet columns very wide.
  4. Open the Proppant Calculator again in MProd.

  (#2490)

• [Fix] The simulator did not compute the Reservoir Pore Volume and Initial Gas in Place if the user stopped a History Match, Closed System simulation early. These values could be blank or out-of-date at the bottom of the report. (#2617)

• [Fix] The Well Data “Horizontal—No Fracture” tab could improperly allow the user to edit the data when using the History Match simulator with a fractured, single-case, horizontally oriented well. (#2473)

  This bug affected cases that had been using the Production simulator with either Base or Stimulated Case set to “Horizontal—No Fracture.” If such a case were then changed to use the History Match simulator, the Well Data screen would continue to interpret the Base and Stimulated Case options, even though these options are disabled in History Match.

• [Fix] The Well Data “Horizontal—No Fracture” tab was visible when using the Design Optimization simulator, even though Design Optimization does not use any of the data on this tab. (#2473)

• [Fix] When importing multi-zone Proppant Transport data from MFrac (using the Import button on the Variable Fracture Conductivity Data screen), MProd allowed the user to select more than one zone for import, but only the lowest numbered zone would actually be imported. MProd now limits the user to a single selected zone. (#2499)

• When the “McGuire and Sikora Type Curves” and “Optimum Fracture Performance Curves” options were unchecked in the Design Optimization simulator, the McGuire & Sikora: Productivity Index (PI) vs Penetration (Ix) and Optimum Fracture Performance Simulation Data Windows were missing from the menu. These windows were supposed to be disabled (grayed), not hidden. (#2537)

MPwri

• [Enhancement] Improved support for very low injection rates. (r40463)

• [Fix] Fixed bounds checking error on Run (“Fluid Loss Data: Hydro-Carbon Saturation is not within bounds”) when Hydro-Carbon Saturation (fraction) was between 0.9 and 1.0. (#2568)

• [Fix] Fixed incorrect BHTP and flow rate distribution as efficiency approaches zero in limited entry mode for multilayer fracs. (#2567)

• [Fix] For 2D fracture geometry, the Fracture Fluid Gradient option is now disabled upon entering the Options screen. (#2577)

• [Fix] Saving a file with an Injectivity Index plot open, then reopening the same file, would show the plot with the wrong options.

  Specifically, any Injectivity Index plot versus Time would be converted to a plot versus Volume (but with the wrong X axis caption), and any plot with the Leakoff Rate or Fracture Length options selected would have these options disabled. (#2552)

• [Fix] Some of the Diagnostic plots were missing titles (i.e., there were no words on the plot). This also applied to the Vertical Stress Profile plot under Fracture Characteristics. (#2573, #2607)

• [Fix] The Porosity plot on the Fluid Loss input screen was blank and/or showed the wrong data. (#2534)

• [Fix] The Real-Time injection rate staging was calculated incorrectly for cases with stages smaller than the real-time data steps. (#2530)

  This could cause a variety of problems, including preventing the simulation from ever initiating a fracture.

• [Fix] The simulator did not properly store its output for particulates volume per unit area. The symptom was that the “Vol. Loss/Area” plot (number 9 under Plot | Waterflooding) was always blank. (#2564)

MShale

• [Enhancement] Meyer 2012, MShale has gained the capability to model time dependent midfield fracture pressure decline for the fracture network.

  It has been observed (e.g., Weijers et al. (2002), Weng (1993), and Jacot et al. (2010)) that complex fracture behavior may occur when fracturing highly deviated and/or horizontal wellbores. MShale’s new Midfield Fracture Complexity option enables users to model this behavior using the methodology set forth in Meyer et al. (SPE 140514).

  The basis of MShale’s Midfield Fracture Complexity simulation, as explained in the Meyer User’s Guide appendix M.8, is the idea that complex fractures in the midfield region turn and twist, then re-orient in the direction perpendicular to the principal stress planes. This creates a high fracture pressure that does not diminish instantly when the fracture is shut-in. The fracture gradient during pumping can be much greater than the overburden stress gradient without creating horizontal fractures in the far-field.

  Weijers et al. state that “Mid-field tortuosity is recognized by a high apparent ISIP and rapidly declining pressures during the first few minutes of shut-in.” If you are seeing such effects in your work on unconventional resources, you may benefit from trying out this new MShale feature.

  The Midfield Fracture Complexity feature is configured using the MShale Zones screen. (#2378)

• [Fix] The Fracture Network (Width) plot and the 3D Plot with the DFN option enabled were incorrectly showing the secondary fractures when the number of fractures was set to zero. (#2595)

  This affected cases using the “Cluster or Complex Fractures” option and zero in any of the “Number of ... Fractures” inputs on the Characteristics page.

MView

• [Enhancement] Massive speedup of the Edit Data screen. This screen should now appear almost instantly for any size data set. Also greatly reduced MView’s memory consumption with this screen open. (#2438)

• [Enhancement] The Data Sets | Setup screen now has a horizontal splitter bar so the user can adjust the relative sizes of the data preview and column setup spreadsheets. (#2464)

• [Fix] Changing a data set from Real-Time to Replay when the “Data File” checkbox was unchecked had no effect. (#2553)

• [Fix] Data set names containing an “&” (ampersand) character now display properly in Build Plots, Merge Data Sets, the Data menu, and the Data Sets screen. (#1595)

• [Fix] Disabling a data set, then changing the parameters, could cause MView files to become unreadable with a message about an “unexpected unit type.” (#2551)

  (The version of MView with this bug fix can recover any files that may have become corrupt due to the bug.)

• [Fix] Fixed an unhandled exception crash when using Meyer 2010 to upgrade an MView file created with the following procedure: (#2561)

  1. Create the file using Meyer 2003 or earlier;
  2. Upgrade the file using any of Meyer 2003 SE through Meyer 2009 (inclusive);
  3. Never edit the Parameters screen data (i.e., never open the Parameters screen) in the intermediate version.

• [Fix] Graphical Edit drop-down lists were interfering with menu access keys (Alt+R, Alt+P, Alt+S, etc). (#2489)

• [Fix] MView was unable to open data sets where parameter #1 had no data, but the other parameters did have data. This made certain .mview files unusable. (The symptom was a long message about an “inconsistent number of data points.”) (#2487)

• [Fix] Pressing F4 now correctly cycles through all available mouse modes in Graphically Edit Data mode. (#2461)

• [Fix] Renaming a data set in Data | Data Sets, but not making any other changes (i.e., not entering Setup), would not mark the MView file as needing to be saved. (In other words, File | Exit would not prompt the user to save their changes to the data set.) (#2554)

• [Fix] The “Clear All” button in Build Plots is now disabled if the Parameters spreadsheet is blank. (#2505)

• [Fix] The Data | Data Sets Browse (...) button once again defaults to the folder containing the currently selected data file. (#2493)

• [Fix] The Simulation Setup for Concentration TSS and Concentration OIW was not properly stored in the .mview file. MView could be configured to send these parameters to MPwri, but File | Save followed by File | Open (e.g., by closing and reopening MView) would reset them to “Not Available.” (#2528)

• [Fix] The View Plots menu could open the wrong plot, or nothing at all, if the data for one of the plots in Build Plots becomes unavailable. (#2613)

Meyer Data Acquisition

• [Enhancement] Meyer 2012 introduces the ability to perform data acquisition via a direct TCP/IP link (i.e., a link running no particular application protocol but rather simply dumping raw data). This feature should be especially useful when working in newer data vans without a reliable serial port connection.

  Data acquisition interfaces in frac vans are not standardized, so we have chosen to implement the simplest possible “protocol” (acquiring or sending raw data over a TCP/IP socket) first. We are open to supporting more structured or more capable protocols in the future; however, we need details about the protocols that are in use before we can support them. Please contact Meyer Technical Support if your data van is running a TCP/IP-based acquisition protocol that is not compatible with this new version of Meyer Data Acquisition.

  Information Security: The data transmission in this new protocol is not secure: not encrypted, not authenticated. If you are using Meyer Data Acquisition to send your frac data across the Internet, anyone along the way could eavesdrop on your data or alter data being sent to you. Please consider using add-on encryption such as a VPN, an SSL/TLS tunnel, or an SSH tunnel if you are performing data acquisition across the Internet or any other insecure network.

  These issues are much less of a concern when the data is staying within the job site and only incidentally traveling via LAN or local radio link (WiFi).

• [Enhancement] Meyer Data Acquisition now auto-detects COM port names and descriptions (for serial and modem ports) and displays them in a drop-down list, rather than requiring the user to iteratively guess the port number. (#625)

• [Enhancement] This release features a complete rewrite of the Meyer Data Acquisition input and output port configuration screens. This makes the screens much better organized, and should make them much easier to understand. (#625)

• [Enhancement] Timed popups (alert windows that appear, then disappear after a set amount of time if the user ignores them—useful for non-critical alerts, e.g., “reached the end of the input file”) now support the Ctrl+C keyboard shortcut for Copy To Clipboard, to make it easier to search for the popup contents online and/or mail it to tech support. (#2599)

• [Fix] Fixed an integer overflow in the “Specify how often to check for data”/“Specify how often to send a line of data” text file polling options. Previous versions of Meyer Data Acquisition could not use any polling interval longer than ~33 seconds. Meyer 2012 allows polling intervals up to 1 week, which matches the original design. (#2583)

• [Fix] Long pathnames could be truncated on the Append/Overwrite screen. This screen now dynamically adjusts its size to accommodate the current output pathname. (#2518)

• [Fix] Overwriting a large output file (e.g., several hundred thousand lines) could cause Meyer Data Acquisition to appear to stop responding while it counted the exact number of lines in the file so it could show an exact line count in the Append/Overwrite screen. This line counting process now runs in the background after the Append/Overwrite screen is already open. (#2555)

• [Fix] The horizontal scroll bar was missing from the Meyer Data Acquisition data preview panel. (#2500)

• [Fix] The Meyer Data Acquisition Phone Book now allows commas in the “Name” field. (#2580)

• [Fix] Timed popups (see #2599) could appear on the wrong monitor in multi-monitor setups. Specifically, if the user had ever moved one of these popups to a secondary monitor, all future popups would appear on that monitor regardless of the placement of Meyer Data Acquisition. (#2518)

• [Fix] When saving to an output file on a network drive across a wide-area network link, if the WAN connection dropped then Meyer Data Acquisition would stop saving to the output file due to an I/O error. However, the visual cues indicating that this had happened were very subtle and easy to miss, so it was possible to lose data in this situation. (#2481, #2518)

  Meyer Data Acquisition now halts and clearly signals an error in this case.

  (Meyer & Associates, Inc. does not recommend saving the Meyer Data Acquisition output file to a network drive located across a WAN link.)

  The same conditions could technically have occurred while saving the output file to a LAN network drive, but this was much less likely due to the more reliable nature of local area networks.

MKey

• [Enhancement] MKey is now much faster at processing key files for companies with a large number of keys. (Updates that took five minutes with the old code take under a second with the new code.) (#2576)