Professional Documents
Culture Documents
Reserves Reporting Using PITRES PDF
Reserves Reporting Using PITRES PDF
Global
Figure 1. Setup for MS3D reserves.
Mining
Software The second and third panels (see Figure 2a and 2b) contain information for the file and report
setup and the area of the model to use. The reserves can be generated from a VBM pit or set of
Solutions
polygons, from the old DIPPER B- and S-file pits, from Gridded Surface File (GSF) surfaces including
Since MineSight® Economic Planner (MSEP) shells, from external partials files [e.g., from MineSight®
1970 Interactive Planner (MSIP)/M650IP or MS3D], or from rectangular boundaries specified on the panel
requesting the easting, northing, and elevation boundaries. The VBM and old Dipper options should
generally not be used but are left on the panel for backward compatibility. MS3D pits are more accurate
and have replaced the VBMs. MSEP GSF surfaces have replaced the Dipper B- and S-files.
The recommended approach for doing incremental reserves on pit phases is to design the cumulative
pit for each phase, run Pitres on each of these, and then run Pitinc to generate the incremental
reserves between the Ascii summary files. This is critical to avoid double accounting when using any
material priority options.
Page 1
Reserves Reporting Using Pitres
The File Setup and Reporting Detail panels have the prompts for the reporting options, the
optional Zone Input File, and whether or not to create a scheduling file [for MineSight® Strategic
Planner (MSSP), etc]. Output files include the report itself, the SCD scheduling file, and a reserve
summary file. If insitu or diluted grades were requested for reporting, they will be output to both the
reserves summary file and the scheduling file. The scheduling file Material Classes can be
generated using either the cutoffs or the Zone Item. If using cutoffs, the cutoff and material class names
are specified directly within Pitres on the CUTOFF panel. If using the Zone Item, then an MSSP
material class is made for each zone setting the material class name to the zone name. If a Zone Input
File is used, then only the zones from the Zone Input File will be output to the SCD file. If a Zone
Input File isn’t used, then the zones will be named 1,...,4000 and all 4,000 will be output. (NOTE:
4,000 is the new limit on the number of unique zones in the model). It is highly recommended that
a Zone Input File be used when using the scheduling Zone Item option. NOTE: The cutoff bin
reporting is DISABLED when using the Zone Item option.
Global
Mining
Software
Solutions
Since
1970
Page 2
Reserves Reporting Using Pitres
The report file can be a fully detailed report with every zone on every bench (default), just a final
summary of the total for each zone for the entire run along with the final bench summary (option 1), or
the same as option 1 with an additional summary of all zones for each bench (option 2).
The Zones and Cutoffs option allows all zones and cutoffs to be reported in the totals section. It
makes it easier for cutting and pasting into a spreadsheet. This option is only valid when a Zone Input
File is being used.
Reserves can be summarized to a larger block height for cases where the original block height is a
multiple of the actual bench height (e.g., oil sands often model on 1m bench heights but report in 15m
bench heights).
Zone parameters can be input to Pitres through the panel defaults or through the Zone Input
File. The Zone Input File is the same format as the M650IP Zone Input File with optional extra
values for dilution density, grade dilution, and ore/waste cutoffs by grade item. The yield% is ignored
in Pitres, but must be set to 100% for M650IP. If using the ore/waste cutoff by grade item, then a
“#GRADE G1 G2 G3 ... ” line must be used in the Zone Input File. A dilution grade can be specified
and if used, it must be set for all grade items, followed by the optional cutoff grades for each grade item
and an optional set of 0/1 flags. A 0 means waste material below the cutoff (default), and a 1 means waste
material above the cutoff. The format for the Zone Input File is: Zone Name, Zone#, Dens, Yield%,
Recov%, Diln%, Diln Dens, Diln grades, Cutoffs Grades, and Cutoff Flags.
The Zone Input File can be set up using procedure Pitzon or with a text editor. Other notes
include:
− The Zone Input File is optional and if not used, all zones are assumed to be between 1 and
4000 and recovery is set to 100% and dilution to 0 for all zones.
− Pitres handles up to 4,000 zones with zone numbers up to 99999. The zone name can be up
to eight characters.
− Recovery and dilution are specified as percentages. The dilution grades, ore/waste cutoffs, and
cutoff flags from the zone lines are matched up to the grade item order from the GRADES
lines regardless of the order in which they are specified on the Pitres panel. If the dilution
grades are not specified, they default to 0.
− If the recovery for any zone is 0 or it fails one of the grade cutoff tests, then it is only reported
if the insitu grade option has been requested (i.e., it will only show up as waste if the diluted
grade option is requested).
− Any zones that exist in the model but are not specified in the Zone Input File are wasted. A
WARNING message is issued.
− The # indicates a comment and can be placed anywhere within the file.
The File Setup panel also has a prompt for item naming when multiple zones per block are involved.
Global The item names can be specified using an alpha or numeric suffix or they can be given unique names
Mining for the same grade item for each different zone. The model item panel displayed depends upon how the
Software prompt is answered. If the tick box is left off, then the panel will be as shown in Figure 3a. If it is on, it
Solutions will appear as in Figure 3b.
Since
1970
Page 3
Reserves Reporting Using Pitres
Page 4
Reserves Reporting Using Pitres
Reserves can optionally be reported within up to 100 cutoff bins or cumulative above each cutoff (see
Figure 4). The cutoffs are used as a less than test. That is, if the cutoffs are 1.0, 2.0, or 3.0, then the cutoff
bins range from >=0 to <1, >=1 to <2, >=2 to <3, and >=3, respectively.
The cutoff bins can also used as material classes for the scheduling file. The material class label for each
cutoff can optionally be specified on the panels (the first for less than cutoff1, second for >=cutoff1, etc.).
If the labels are not specified, they will default to ORE+nn.nn where nn.nn is the grade cutoff value.
The omit first grade item option is used for creating scheduling material classes from a range of
ZONE codes (i.e., it is only used for binning). For example, zones 1-25 might be LCAP, 26-50 OXIDE,
51-75 SUP, etc. The Zone Item can then be used as the first grade item and the appropriate material
classes created without the Zone Item showing up in the scheduling file as a grade item. An alternative
method is to use Modcls to create scheduling material classes, use that item as the zone code, and use
the option to create the Material Classes from the Zone Item.
Material can be wasted using either a greater than or less than cutoff test on a single grade item using
the panel prompts. In addition, cutoffs can be specified on each grade item using the Zone Input File as
described earlier in this paper. The insitu grades are always used for the ore/waste cutoff tests regardless
of whether insitu or diluted grades are being reported. If using an ore/waste cutoff test for multiple grade
items, then the material is wasted for a zone if any one grade item fails its cutoff test.
Normally, any missing grade item in a block causes the entire zone to be wasted. The treat missing
grades as 0 will dilute the ore instead of wasting the zone for any block with missing grades.
Page 5
Reserves Reporting Using Pitres
Page 6
Reserves Reporting Using Pitres
The current Pitres limits are 4,000 zones total for the entire model numbered from 1 to 99,999, 30
zones per block, 30 grade items per zone, 100 cutoff bins, and 99 waste types number from 1 to 99.
Page 7
Reserves Reporting Using Pitres
Global
Mining
Software
Solutions
Since
1970
Page 8
Reserves Reporting Using Pitres
Global
Mining
Software
Solutions
Since
1970 Figure 8b. Pitsum sample of L-G summary – second panel.
Page 9
Reserves Reporting Using Pitres
Global
Mining
Software
Solutions
Since
1970
Figure 9a. Example of Modcls with existing Class Input File. Figure 9b. Sample Class Input File.
Page 10
Reserves Reporting Using Pitres
Figure 10 shows the panel for building the Class Input File manually. This example just shows part
of the full set. In certain cases, it is easier to use a text editor or Microsoft® Excel for easier copying of
groups of lines/cells.
Figure 10. Modcls example for manually building the Class Input File.
Figure 11 shows the panel for building the Class Input File automatically. In this case, one item is
setup using the minimum, maximum, and increment (SEAM) and the other with a list of distinct values
(DIST). The net result of this setup is actually the same as the seam.cls case because of using a seam
range of 100. Each distance group then goes from 101-200, 201-300, 301-400, 401-500 which is the
same as adding 100 to the base seam number for each distance interval.
Global
Mining
Software
Solutions
Since
1970 Figure 11. Modcls example for AUTO building the Class Input File.
Page 11