Meyer 2001 is a major upgrade to the Meyer 2000 Hydraulic Fracturing Software. Meyer 2001 includes numerous technical enhancements, improved filename handling (long filenames and paths), a new installer, bug fixes, and more.

One very noticeable enhancement to Meyer 2001 is the 32-bit long filename and path extension. Prior versions of the software could not handle long filenames or paths.

This release is a major step toward full 32-bit capability, and includes the latest third party software and operating system upgrades. Code consistency, optimization, error checking and file handling have all been enhanced.

Meyer 2001 Changes (Build 4.00.0423)

Meyer 2001—New Features

Following is a partial list of the enhancements and improvements since the release of Meyer 2000 on December 1, 1999.

Installation & Operating Systems

New Installer

A new installer based on the Microsoft Windows Installer technology was implemented to make the installation process more reliable.

Application Directories

The applications now store the user databases, *.plt files, etc. in the user profile. Technically, we store this information in the “roaming profile per-user application data folder,” or “in the user profile.” The location of this folder depends on the version of Windows you are running. Whatever the folder, we store our information in the Meyer 2001 v4.0 (English) subfolder of this application data folder (the Russian version stores it in Meyer 2001 v4.0 (Russian) instead). The folder locations for the various versions of Windows are given below.

1. On Windows NT 4.0 and Windows 2000, the application data folder is %UserProfile%\ Application Data (on Windows 2000, %APPDATA% also works.)

   1. For a user called Bruce on Windows 2000, our folder might be C:\Documents and Settings\ Bruce\ Application Data\ Meyer 2001 v4.0 (English).

   2. But for a user called Ginny on Windows NT 4.0, our folder would be C:\WinNT\ Profiles\ Ginny\ Application Data\ Meyer 2001 v4.0 (English).

2. On Windows 95, Windows 98, Windows 98 Second Edition, and Windows Me, the application data folder is in one of two places: %WINDIR%\ Application Data (if profiles are disabled) or %WINDIR%\ Profiles\ username\ Application Data (profiles enabled).

   1. For a user called Henry on Windows 9x, the application data folder is under C:\WINDOWS\ Profiles\ Henry\ Application Data\ Meyer 2001 v4.0 (English).

   2. Or if it’s not there, it’ll be under the directory C:\WINDOWS\ Application Data\ Meyer 2001 v4.0 (English).

3. A Custom Install option is also available to enable installation to other, non-default directories.

Application File Extensions

General
.plt	Default Plot configuration file
.tod	Tip of the Day file
.axt	Axis Template file
.adt	Acquired Data file
.dat	Raw Data
.def	Default Data File
.tmp	Temporary Data File
MKey
.key	MKey File
MFrac/MF2D/MWFlood
.usr	User Database
.dbs	Database
.fdb	Fluid Database (“system,” i.e., vendor)
.pdb	Proppant Database (“system,” i.e., vendor)
.adb	Acid Database (“system,” currently generic)
.fie	Fluid Import/Export File
.pie	Proppant Import/Export File
.aie	Acid Import/Export File
.nwb	Real-Time Near-Wellbore Table File
.3dc	Three-Dimensional Plot Configuration
.las	Log Data File
.emf	Exodus Export File
MView
.vhd	MView Header File
.log	MView Filter Log
.stp	Meyer Data Acquisition Setup File
MinFrac
.mwz	Wizard Template

Application File Extension Summary

	MFrac	MView	MinFrac	MProd	MNpv	MFast
Data file	.mfr	.mvd	.m20	.mpr	.npv	.mfa
Output file	.fd*	-	-	.pod	.nod	-
Last Input	.mfl	-	-	.mpl	.npl	-
Plot Config	.fpc	.vgc	.mpc	.ppc	.npc	.apc
Plot text blocks	.apt	.vgt	.mpt	.ppt	.npt	.apt
Plot Templates	.mtp	.vtp	-	.ptp	.ntp	.atp
Units	.mfu	.mvu	.mmu	.mpu	.mnu	.mtu

Database Installation

The Meyer 2001 Installer will preserve the current user databases when you install the new version. There is no chance of them being overwritten or lost. If you have more than one version of a user database on your computer, the installer will pick the most recently modified version and copy it to the appropriate default directory for your use. No user interaction is necessary.

Hasp Driver

Installer automatically installs the hasp driver. Updated the Hasp device driver to version 4.13. This updates the Hasp device driver to be compatible with the latest Windows operating systems (Windows 95/98, Windows NT 4.0, Windows Me, and Windows 2000).

All Apps

Long File Name Support

All of the Meyer applications now use long file names for input, output, database, unit and configuration files. Following is a list of general Windows considerations for long file names:

1. The path and file name cannot exceed 255 characters (i.e., Windows MAX_PATH).
2. The following characters are not allowed in filenames or paths: < > : " / \ |. These characters are reserved for Windows.
3. The application must not use reserved words, such as AUX, CON, and PRN, as filenames or directory names.
4. Implemented long file name support when displaying an opened file in the title bar, Most Recent File list, and Window menu by substituting path names with \...\. This allows the applications to display the long file name in those areas.

Application Data Folder Support

All working files, user databases, plot configuration files are stored in a sub-folder of the user profile’s Application Data folder. In previous versions of the software, this was stored in the application folder. By having these files in the user profile, if more than one person uses a computer, each user will have their own copies of these files. Locked down environment is also supported.

Working Files

The Meyer applications now use temporary working files not only for input files, but also for output and other configuration files associated with the input files. This change allows you to open and run read-only files because the original (including the output) files are only changed when you save them. This also enables the creation and running of untitled projects without having to save to a file first.

Starting Folder for Open/Save-as Dialogs

When selecting a file name for opening or saving files associated with the input file, it is useful to keep them in the same folder. The Open/Save-as dialogs for the following tasks now start in the folder of the currently opened input file:

• selecting a report bitmap,
• exporting a plot,
• exporting a report,
• exporting an Exodus file (MFrac),
• importing a log file (MFrac),
• selecting a data-set file (MView),
• exporting data as text (MView),
• merging data files (MView),
• selecting an MFrac output file (MProd), and
• selecting an MProd output file (MNpv).

Read Only Files

You can now open and save Read Only files. The file attribute is changed during the save operation.

Last Opened Files

The Meyer apps now remember the last six files opened, as opposed to four in the previous release. Now any file that does not exist in the Most Recent Used file (MRU) list that is selected/opened will be deleted from the list.

Application Shortcuts

Upgraded all applications with consistent shortcuts under the file menu. Previously, only some of the applications had shortcuts.

Report Window

Sized the report window to fit inside the frame window when it is created and displayed. This way the user does not have to scroll up then size it to see the contents of the window. (Easier user interaction with the applications.)

Menu Item Consistency

Reorganized the File and Window menu items to make the applications more consistent.

API Calls

Converted of a number of API calls from 16-bit to 32-bit (SendMessage(), PostMessage(), etc.) in preparation for 32-bit.

Date Format on Printed Plot

The date on the printed plots had a hard-coded format. The printed date now uses the system’s short date format.

New Look and Feel

Sunk the border in the main window for all the apps. Added new bitmaps and gave the apps the standard application background color of Windows. Now when the user changes the application background color in the display properties dialog, each Meyer app that is opened will change its background to that new color.

MFrac

Enhanced Fracture Propagation Methodology

The numerical algorithm that controls fracture initiation and height growth has been improved. The minimum horizontal stress as a function of time based on geometric and time considerations has also been implemented. This enhancement accounts for a number of different effects which were normally assumed to be second order and negligible. However for certain cases these second order effects become first order. This addition is important for fracture initiation in very small intervals and for cases where excessive height growth occurs. These enhancements are explained by the discussion below:

1. If a fracture is initialized over a perforated interval where the fracture is setup to initiate over the entire perforation interval where the interval consists of a low stress zone with height initiation in the higher bounding stress zones, the fracture propagation criteria will now determine the redistribution of stresses for calculating the propagating minimum horizontal stress as a function of time and will not automatically fix the initial inlet boundary condition at the initial higher stress level (e.g., if the perforation zone is mostly in a pay zone layer with a confining stress of 5000 psi but is also initiated a foot into an upper stress zone with a 6000 psi confining stress, in Meyer 2000 (MFrac v3.5) the higher initiation pressure would be fixed as the boundary condition. Now the fracture will initiate in the upper layer but will quickly retreat to the zone of lower confining stress (negative height growth) resulting in reduced height growth and a lower fracture pressure (but a higher net pressure!).

2. This methodology is important for cases where the zones are small and the stress deviates substantially over the fracture initiation zone.

3. This change is also important in some cutting re-injection and waste disposal applications.

4. The major application is for initiation of vertical fractures from horizontal wells where the perforation height is small compared to the final fracture dimensions.

5. The height growth algorithm was also changed to allow for negative net pressures.

6. Selecting the fracture to initiate over the minimum stress zone usually negated problems with specifying an unrealistic boundary condition as in the case above.

Low Efficiency Fractures

Changed the numerical convergence solution for low efficiency fractures. This was implemented in MWFlood to prevent solution oscillations for efficiencies less than 1.0e-05. This also applies in MFrac for efficiencies less than 1%. This change helps stabilize the leakoff rate for large fluid loss cases if the injection rate changes. The fracture may however still close depending on the leakoff rate, time step and fracture volume. Smaller time steps normally help stabilize these types of problems and more accurately determine when the fracture will close.

Improved Multi-Zone BHTP Calculations

Improved the calculation of the bottomhole treating pressure (BHTP) for multi-zone cases. The solution is now more implicit in the frictional pressure loss calculations between fractures.

Proppant Movement

Improved the proppant transport solution during shut-in. Now if the proppant does not bridge or screen-out it is allowed to have movement in the fracture (lateral and vertical). Before once the pumps were stopped (zero rate) and the proppant starts to screen-out, the proppant transport solution set a flag which did not allow any movement of the suspended proppant laterally. This change will be most noticeable in the final proppant distribution for cases with large pad volumes and little settling. In this case the proppant will continue to flow toward the tip of the fracture during closure.

Proppant Flowback

Changed the proppant flowback option (on/off switch) for both flowback and no proppant flowback. This option is now available for both fluid loss type models (i.e., standard and fluid type dependent leakoff). This feature has been enhanced to better track the proppant screen-out position near the wellbore during flowback when the proppant is not allowed to flow back through the perforations. Larger flow back volumes (flowback volumes larger than the last proppant stage) are now modeled more rigorously.

Wellbore Deviation Table

The maximum number of rows in the wellbore deviation table has been increased from 50 to 500. This was necessary to allow the user to more accurately input the wellbore configuration for highly deviated and varying wellbore deviations.

Wellbore Schematic

The wellbore schematic plot has been modified to allow for a finer scale resolution of the proppant staging at low proppant concentration levels.

Foam Treatment Report

The total N₂ and CO₂ volumes have been added to MFrac’s report for foam treatments. These volumes are reported for the foam schedule input data and for the real-time surface treatment-schedule output data.

MView

Real-Time Data Window’s Digital Display View

The real-time data window has been modified to allow easier switching been view modes. In addition to the raw data and translated data tabular view modes, a new digital display view has been included. This digital window displays the “digital” data in individual windows. The order of the parameters in the selection list determines the order in the digital display.

Improved File Open and Save dialogs

Improved File Open and Save dialogs in MView by adding more text file filter types.

View and Build Plot Order

Changed the view and build plot order under the plot menu in MView to the progression of first building and then viewing a plot.

Meyer 2001—Bug Fixes and Corrections

Following is a list of the major bugs, anomalies and quirks fixed in Meyer 2001. All problems brought to our attention since Meyer 2000 (our previous release) have been addressed. This list only includes the major corrections that we feel may have impacted a number of our clients or bugs for which there was no work around. We have made a concerted effort to clean up the code and increase consistency throughout.

All Apps

Displaying of Bitmaps in Reports

Fixed a problem with displaying of a bitmap in the reports. The original code was checking for files with all capitals in the extension of a file name. Therefore, the app would not open a bitmap with an extension other than all capitals. The app would give an error that it could not find the bitmap even though the file existed. The extension checking is now case insensitive.

Organizing Plot Templates

Fixed the problem with the displaying of the template path and file names in the Organize Template window. Sometimes part of the file name and extension would get cut off and therefore the user could not scroll over to see the template name.

Flicker

Prevented flicker of the main app frame windows by not allowing horizontal and vertical redraw under painting.

Data Directories for Current Application

In the Data Directory dialog, the browse button for the current application was not disabled or grayed out.

Net-Pressure Plot Legend

The user was not able to edit the left-axis legend names of two of the net-pressure diagnostic plots.

Text Block Configuration

The way identifiers were assigned to text blocks in some cases caused a new text block to use an old identifier, losing the configuration information (e.g. font, position, etc.) for the old text block.

Dell Laptop Latitude CPx

A problem with the Dell Latitude systems causes the Meyer applications to give an access violation (general protection fault) error on Windows 98. This occurred when an MDI child window was closed and the operating system sent back an incorrect WM_MDIACTIVE message. Our software now checks to make sure this message sent by the operating system is valid. This was actually a bug in the Dell Laptop operating system. Normally it is assumed that the operating system sends back the message in the correct format.

Legend Units

In certain cases, the units in multi-axis legends didn’t match up correctly (i.e., the legend index was incorrect).

MFrac

Database Entry Import

Importing a database entry with an existing code and choosing to overwrite would cause the new entry to be written to an undefined location in the user database. This has been fixed.

Self Similar Closure

All rates during self similar closure are now set to zero. Previously, the last rate was listed in the report and displayed on the plots.

Foam Plot Templates

A few foam plots were not being generated if a plot template, which contained them, was loaded. The following foam plots were affected: Wellbore plots #5, #6, and #8; Treatment plot #5.

Real-Time Foam Report

In the Output section the real-time foam report, below the surface treatment schedule (pumped) table, the total slurry/liquid volumes incorrectly include the wellbore fluid volume.

Dual Flow (Tubing and Annulus)

When injecting down annulus and tubing, the total rate was used instead of the individual annulus and tubing rates for calculating frictional pressure losses.

Annulus Friction

If the wellbore hydraulic option was set to “user database,” the frictional pressure loss for annular flows was calculated from the fluid friction table incorrectly for some cases. This generally occurred if the Reynolds number was between the laminar and turbulent flow regions.

Acid Rock-Embedment Strength

The conductivity as a function of rock embedment strength < 20000 psi was incorrect in the original Nierode paper. This was bought to our attention by a user. To correct this in the code, the C2 coefficient was changed from C2 = 19.9-1.3 ln S_RE to C2 = 13.9-1.3 ln S_RE, where S_RE is the rock embedment strength (i.e., the coefficient 19.9 was changed to 13.9).

Real-Time CO₂ Rate

The real-time CO₂ rate reported was actually the real-time N₂ rate.

Division By Zero

If the fracture net pressure went to zero, the momentum height growth function could cause a division by zero if certain rare conditions were met. These conditions included cases where the fracture was perforated in a very high stress zone and propagates into a low stress layer causing the net pressure to go to zero or during acid fracturing when the fracture may open and close rapidly. This release version can now have a negative net pressure which also eliminates this anomaly (see also Enhanced Fracture Propagation Methodology above).

BHTP References

The frictional pressure losses between multi-zone fractures were used incorrectly in the calculation of the BHTP references specified below the second perf zone. This only affected multi-zone cases.

Heat Transfer

The heat transfer in-situ properties for a gas formation were incorrect. This may have inadvertently affected some fluid rheology calculations when heat transfer was on depending on the fluid rheology and specified fluid properties.

Wellbore Volume

Wellbore frictional pressure loss calculations were incorrect when the wellbore volume reference depth was different than the “zero” reference depth.

Wellbore Restrictions

Restrictions not in the tubing caused undefined behavior when running the simulator.

MView

“Save Data as Text File”

When the “Save Data as Text File” command was used, the user could exit the application while the file was still being written (i.e., before the application finished writing the file).

Parameters Enter Key

Fixed the problem with the parameters dialog disappearing when the user presses the enter key.

Imported File Exceeds Maximum Row Limit

There was no error message when the imported test file exceeded the max row limit; the import was just aborted. Now an error message appears.

Russian Version

In the Russian version, increased the size of the drop down list boxes within the filters and shifts tabs of the data setup dialog within MView. The user can now make out the contents of the list box if the units are in English.

24 Hour Clock Rollover

MView will add 24 hours to the time if it thinks the clock has rolled over to the next day. Generally this makes good sense. However, the time sent in real time may go backward without a new day occurring if the data acquisition resends a data buffer. Following is an example of an actual real time data set where the data buffer was resent:

12:46:04
12:46:05
12:46:06
12:46:07
12:46:08
12:46:04 <--- resending of data buffer
12:46:05
12:46:06
12:46:07
12:46:08

Now we check if the data has been resent and do not add 24 hours to the clock. This is quite rare since most data acquisition systems do not resend data buffers.

Meyer Data Acquisition & MView

Append

Some sequences of starting up Meyer Data Acquisition & MView could cause them to lose track of each other and overwrite data when you clicked append, or vice versa (i.e., if MView shuts down and Meyer Data Acquisition is paused, and then re-start MView, Meyer Data Acquisition could read in the data from the temporary file and then append the data in memory). This problem is very rare but it has happened.

Real-Time Reset

Non-real-time data plots were losing their data (being reset) when the real-time data from MView was reset (e.g., opening a file in MView). These plots should have ignored the real-time reset messages from MView.

MFast & MinFrac

Data Validation

Added data validation in the data dialog within MFast and MinFrac. These apps would crash if a field was left blank and the user selected OK. The fix restores the apps’ variables on this dialog when the user attempts to ignore the input data out of range warning message. If a field is left blank we now restore the original contents.