All Apps—Enhancements
Additional Units. Added a number of
different units and unit types, specifically: units dealing with filter
cake properties, volumetric and mass concentrations, and numerous other
units.
Alphabetical Order. Many items in
the user interface are now sorted alphabetically:
- The acid, fluid, and proppant databases in MFrac and MPwri.
- The lists on the Heat Transfer screen in MFrac.
- The lists on the Thermal/Water Front Data screen in MPwri.
- The phone book in MView.
- The units screens.
Command-Line File | Open. It
is now possible to open files in all the apps from the Windows command
line, including Untitled files.
Exporting Reports. When exporting a
report to a file, the file now automatically opens with the default
Windows file viewer after exporting.
File Management Error Checking.
Greatly improved file management error checking code. It is now much
more difficult to crash the applications by opening an invalid
file.
File Structure and Format. The new
file format is one of the most noticeable enhancements to all the
applications. The main advantage of this new format is that all the
input, output, and support data stored in a single file. For example,
for MFrac all the data is stored in one .mfrac file which is about
ten (10) times small than the old .mfr input file.
Following is a list of the new Meyer 2003 SE file
extensions.
| Program |
Main Data File |
Plot Template File |
Units File |
| MFast |
.mfast |
.atp |
.mtu |
| MFrac |
.mfrac |
.mtp |
.mfu |
| MinFrac |
.minfrac |
.mwz |
.mmu |
| MNpv |
.mnpv |
.ntp |
.mnu |
| MProd |
.mprod |
.ptp |
.mpu |
| MPwri |
.mpwri |
.mtp |
.mfu |
| MView |
.mview |
.vtp |
.mvu |
Importing Output Files Into MNpv, MProd,
and MView. When importing output files into these applications,
you no longer have to save the file in the “exporting” application to
make changes visible to the “importing” application. For example, if
you re-run an MProd file that you are importing into MNpv, you no
longer have to save the MProd file before re-running MNpv.
Industry-Standard Zip Format. The
new files are in the industry-standard .zip format, so they can be
saved with a .zip extension and sent directly via email.
Moving Linked Files. When an
application file and a linked file are in the same folder, the files
will still work if you move them both to a different folder. For
example, if you have an .mview file that references a .txt
file, and you move both files to another computer, you do not have to
update the .txt file pathname in Data Sets | Setup to make
the files work together on the new computer.
No Limit to the Size of an Imported Text
File. There is now virtually no limit to the size of the text
file imported with the import text file screens (e.g., Import Log File
in MFrac, Import Data File in MinFrac, Data Sets | Setup in
MView). The maximum total number of lines imported remands the same:
86,400 for MFrac and MView; 16,382 for MinFrac.
There are now virtually no field or line length limits. Previously,
fields were truncated to 34 characters, and the total line length
was truncated to 8,192 characters. The old line length limit still
applies to real-time data acquired through Meyer Data Acquisition
(MACQ).
User Interface for Upgrading Files.
The user interface for upgrading files has been completely
rewritten.
All Apps—Changes
Application Data Folders. Moved
Application Data folders to the “Meyer & Associates, Inc”
folder.
Importing Output Files Into MNpv, MProd,
and MView. When importing output files into these applications,
you must now select the main file, not the output file. For example, in
MNpv, when importing output data from MProd, you must now select
the .mprod or .mpr file, not the .pod file. Similarly,
in MProd and MView, when importing output data from MFrac, you must now
select the .mfrac or .mfr file, not the .fd1, .fd2, etc.
file.
Increased Maximum Allowable Injection Rate
to 500 bpm. Increased the injection rate maximum limit
from 150 bpm to 500 bpm in MFrac, MFast, MinFrac,
and MView.
Units Screen. The units screen
location and size is now application specific. Previously, all apps
except MNpv shared the same location and size for the Units screen.
All Apps—Bug Fixes
Odd Filenames Fix. The apps now
handle odd filenames (e.g. wrong extension, no filename) correctly in
all cases.
Property Sheets Fix. Prior to
Meyer 2003 SE, property sheets would not appear if the system
font name was less than seven characters long. This mainly affected
users running Chinese Windows.
Report Crash Fix. Fixed a report
crash that would bring down a Windows 9x system when the Data
Description “comments” text ended with a blank line.
Sample Files Fix. Sample files now
work “out-of-the-box” no matter what folder you choose to install the
software.
MFrac—Enhancements
Ellipsoidal Fluid Loss. Added
ellipsoidal (2D) fluid loss using Koning’s solution. This is a major
enhancement to the classical linear fluid loss (1D Carter)
methodology used in most fracturing simulators. Linear fluid loss is
still available as an option.
Ellipsoidal fluid loss allows you to better model leak-off in low
efficiency treatments (i.e., frac-packs). The ellipsoidal model can
have an extremely large impact on the fluid loss rate for cases when
the fluid front is comparable to the characteristics fracture length
and height dimensions. Please refer to the Meyer 2003 SE
User’s Guide Appendices for additional information.
Fluid Loss History. Added an option
to MFrac and MPwri to remember the fluid loss history. The option
allows you to determine the effect a minifrac has on the main fracture
treatment efficiency, time to screen-out (frac-packs), reduced pad
volume, etc. It can be activated under the Fluid Loss model in the
General tab of the Options screen.
This change incorporates a moving grid for each formation layer to
keep track of the fluid leak-off resistant mechanisms as a function of
time and position. You can now model the common observation of
increasing fracture efficiency with subsequent injections. Please refer
to the Meyer 2003 SE User’s Guide Appendices for additional
information.
Allow Perforation Zone Overlap.
When error checking in the zones screen in MFrac/MPwri, the apps now
error check only on the center of perf zone. This allows perf zones to
overlap, and zone centerline depths to be equal.
Defaulted Pay Zone Interval to Perf
Interval. The Pay Zone interval now defaults to the perforated
depths when starting with a new file.
LAS Log Import. The LAS log import
now remembers the data and column selections, if importing the file
with same name as the last log file imported.
Proppant Embedment. Proppant
Embedment (concentration per unit area) can now be specified in the
Proppant Criteria Dialog.
Proppant Transport—Permeability and
Distribution Calculations. A new transport tracking methodology
was implemented to better model the proppant permeability of the
settled bank and suspended proppant. This enhancement also includes the
effects of embedment and a more rigorous handling of lightweight
proppants. The change also fixes a problem with proppant indexing for
alternating pad/proppant stages.
Redesign of Graphical Treatment
Schedule. The MFrac Graphical Treatment Schedule has been
redesigned. The Treatment Schedule now consists of two windows, which
are joined by a splitter bar.
The top window contains a spreadsheet showing all the current
stages. This gives you a full view of all the stages’ data. The window
also contains a new Parameters list box that allows you to display
arbitrary real-time data from MView.
Wellbore Deviation—Linear
Segments. Added an option for linear segments in the Wellbore
Deviation Table. This option enables you to input MD and TVD with
discontinuous deviation angles. A continuous angle build rate over a
given section with the original curve-linear methodology may be more
rigorous but requires a greater number of TVD and MD data sets.
3D Plot Error Checking. MFrac
now gives a warning message if it is unable to open the VRML file for
the 3D Plot.
MFrac—Changes
Definition of Net Pressure.
Although MFrac and MPwri do not use net pressure in the fracture
propagation solution, it is presented in numerous plots and in the
report. In many cases it would be useful to have more than one net
pressure depending on your reference (i.e., your definition of net
pressure or closure pressure). However, we will only use one value
which we will define as the pressure difference between the pressure in
the fracture and an average weighted minimum horizontal stress in the
fracture which controls the opening-closure pressure. For example, if
you have a fracture with a height of 100 feet in
a 100-foot thick zone with a uniform minimum horizontal stress
of 5000 psi over the entire height except for one inch
at 4500 psi in center, what would be the approximate value of
the closure pressure? This is not necessarily the minimum stress in the
perforation or pay zone (i.e., 4500 psi in this case). If the
pressure in the fracture is 5500 psi, the net pressure is
more closely approximated by 500 psi (5500–5000) than
by 1000 psi (i.e., 5500–4500). Prior to
Meyer 2003 SE, a value of about 1000 psi would have
been reported as the net pressure.
This new definition of net pressure more closely relates to the
pressure above the closure pressure than does the old definition. The
net pressure in previous versions was defined as the fracture pressure
minus the absolute minimum horizontal stress in a pre-specified
peroration zone. This change in definition also becomes apparent for
those who have seen negative net pressures (i.e., if the perforations
are in a higher stress zone and the fracture breaks into the adjacent
over- and under-burdens with lower stresses). This negative net
pressure occurs because the fracture pressure is less than the minimum
horizontal stress in the perforation zone.
Also in some cases, the MFrac BHP may match the measured BHTP, but
the corresponding net pressure in MinFrac does not match the MFrac net
pressure at ISIP. This is also evident when poro-elastic and
thermal-elastic stresses are included, e.g. in MPwri. Since for
multi-layer zones, the closure pressure changes depending on the
fracture size relative to the zone dimension, this new definition of
net pressure will more closely resemble the net pressure we think of as
ISIP minus the closure pressure.
MFrac—Bug Fixes
Database Record Creation Fix. The
screen to add a new fluid, proppant, or acid to the database no longer
starts out with junk data in the form fields.
Keyboard Item Selection Fix. The
fluid, proppant, and acid import/export screens did not allow you to
select the items in the list box by keyboard. Also the mouse did not
allow standard shortcuts like Ctrl+Left Mouse.
Graphical Treatment Schedule Fixes.
Prior to Meyer 2003 SE, MFrac allowed two Graphical Treatment
Schedule windows to open at the same time, which could cause a crash.
Also, the Insert and Delete did not work from the keyboard in the
Graphical Treatment Schedule.
Prior to Meyer 2003 SE, MFrac had a drawing bug in the
Graphical Treatment Schedule when you selected a stage on the plot.
When the stage was selected, it was highlighted with the use of blocks
surrounding the stage, but when the window was moved, the blocks failed
to repaint properly, causing a glitch. The Select Rock Properties zones
window had the same problem.
Prompting for Fluid, Proppant, and Acid
Database Conflicts Fix. When you are prompted to rename the
fluid or proppant and enter a code there is a message that states: “An
entry with that code already exists in the database. Replace the
database entry?” In Meyer 2003, this message would appear even
when the fluid or proppant code did not actually exist in the
database.
3D Plot Fixes. MFrac now
shades non-wireframe 3D plots correctly when you select both EOJ
and Closure, and it shows the correct colors when selecting colors for
EOJ and Closure. Also, it no longer corrupts the output VRML file when
a zone name contains a double-quote character.
MinFrac—Enhancements
Drag Lines and Line Slope Options.
MinFrac now offers you the ability to drag lines on the plots. You can
also specify a slope for the lines based on fixed slopes (1/4, 1/2, 1,
2). Drag Line, Line 1 Slope, and Line 2 Slope
options were added to the Select Points menu.
Net Pressure Display. Added Net
Pressure to the text box in the MinFrac plots.
Recovery of Temporary Files.
MinFrac can now perform meaningful recovery of temporary files.
MFast—Changes
Plot Configuration File. MFast now
initializes its default plot configuration file.
Storage of the Unit Set Name. MFast
no longer stores the unit set name in the file, but rather in the
prefs, just like all the other applications. Previously, MFast stored
the unit set name in the file, and the unit selections in the
prefs.
MNpv/MProd—Enhancements
MProd Import from MFrac. It is now
possible to view the report, plots, etc. in an MProd file that uses
MFrac output data, even if you don’t have access to the original MFrac
file.
MNpv/MProd—Bug Fixes
Enter Key Fix. Prior to
Meyer 2003 SE, the Enter key didn’t work in the Data
Description Dialog of MNpv and MProd.
Prompting to Run Simulators Fix.
MNpv and MProd no longer prompt you to run the simulator after you’ve
just run it. Also, MNpv no longer thinks it needs to run every time you
click OK in a plot selection screen.
Report Fixes. MNpv no longer closes
the report when the Units screen is canceled. Also, MProd no longer
uses the wrong MFrac output file to generate the report.
MView—Enhancements
Binary File Warning. When choosing
a file for Data Sets | Setup in MView, MView now displays a
warning if you choose a binary file.
Increased Maximum Parameters and Channels
to 200. Increased the maximum number of Parameters and
Channels from 50 to 200.
Meyer Data Acquisition. The phone
book is now accessible for dialing while acquiring data. A separate
start/stop function for each port allows the output port to be
configured after you start acquiring data.
No Limit to the Size of an Imported Text
File. There is now virtually no limit to the size of the text
file imported with the import text file screens (e.g., Import Log File
in MFrac, Import Data File in MinFrac, Data Sets | Setup in
MView). The maximum total number of lines imported remands the same:
86,400 for MFrac and MView; 16,382 for MinFrac.
Real-Time Data Sets | Setup.
The grid in Real-Time Data Sets | Setup now displays all the raw
real-time data. The grid is updated as data is acquired, adding rows
and columns as needed.
Real-Time Data Window. The
Real-Time Data Window now allows you to configure the color and number
format for each parameter in the Digital Display. Also, you can now
re-order the parameters without having to delete and re-create the
parameter list.
Selecting Channels into Multiple
Parameters. Channels in Data Sets | Setup may now be
selected into more than one parameter at a time.
Simulation Setup Dialog. The
Simulation Setup screen in MView is now split into two tabs. The first
tab has required parameters while the second panel has additional
parameters. These additional parameters will be sent to MFrac in
real-time/replay mode.
MView—Changes
Processing of Real Time Data when a Pop-Up
Window is Open. MView now processes real-time data from MACQ
even when a menus and input data screens are open.
Real-Time Column Selections.
Real-Time Data Sets | Setup no longer restricts column selections
before real-time data has arrived. Previously, if no data had been sent
from MACQ, you could not make any column selections, so you would
always lose at least the first few rows of data.
Simulation Setup. MView now dims
unavailable “Required” parameters in Simulation Setup. Previously,
these parameters appeared in a drop-down box with one choice: “Not
Available.”
Status Bar. Added a status bar
after clicking OK in Real-Time Data Sets | Setup. This was
required since MView can now import a very long file, limited only by
available memory, so the setup may take a very long time.
MView—Bug Fixes
Fix Default Plot Titles. MView no
longer initializes the axis titles and curve names with random words
when building a plot for the first time.
Fix “Reset Plot Text to Default”
Checkbox. Removed the confusing “Reset Plot Text to Default”
checkbox from the Build Plots screen. MView now resets the axis titles
and curve names on a per-plot bases when you change the parameter-axis
settings in the Build Plots screen.
