Documente Academic
Documente Profesional
Documente Cultură
INTRODUCTION
In This Section
ABOUT THIS MANUAL
OBJECTIVE OF THIS MANUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 INTENDED AUDIENCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 HOW THIS MANUAL IS ORGANIZED . . . . . . . . . . . . . . . . . . . . . . . . 1 HOW TO OBTAIN HELP/SUBMIT SUGGESTIONS . . . . . . . . . . . . . . . . . 2
Revised: 2 4 - A u g u s t - 0 1
Page INTROi
INTRODUCTION
Page INTROii
Revised: 24-August-01
INTRODUCTION
INTENDED AUDIENCE
This manual in NOT intended to be self-instructional. It is intended for mining professionals who have received training in the use of MineSight software. A corresponding workbook that explains the system flow, and an example set for a sample problem are available.
Revised: 24-August-01
Page INTRO-1
INTRODUCTION
This manuals format and content have been refined through use by our users who offer suggestions and constructive criticism. Suggestions may be submitted on a MineSight memo included at the end of this chapter (photocopy as needed) or by writing to us at: Mintec, Inc. 3544 E. Ft. Lowell Rd. Tucson, AZ 85716-1705
Page INTRO-2
Revised: 24-August-01
INTRODUCTION
Revised: 24-August-01
Page INTRO-3
INTRODUCTION
Load topography into block model Load model codes into model Model interpolation; kriging User coded subroutines for mine model Plot model bench plans Plot contoured model data Statistical analysis of model data Plot model cross-sections
Raw Project Data 200-SERIES M200V1 M201V1 M203V1 M204V1 M206V1 M216V1 300-SERIES M303V1 400-SERIES M401V1 Check drill-hole data Load drill-hole data base List drill-hole assay data List drill-hole survey data Plot drill-hole collar plan Plot drill-hole cross-section Calculate variograms for drill-hole data Statistical analysis of drill-hole assays
Vn = more than one version of the program exists Pit Design 700-SERIES M701V1 M654Vn M717TS M718V1 M720V1 M721V1 Geometric pit expansion Plot expanded pit Initialize floating cone routine Create a condensed model Calculate economic pits Plot economic pits
Reserves & Schedules 700 & 800-SERIES M659V1 Block partials from expanded pit M728V1 Block partials from economic pit M710TS Initialize reserve descriptors M711V1 Compute reserves M712V1 Calculate reserve summaries M706SM GSM resource by cutoff M708SM Basic GSM resources by mine categories M709SM Targeting from GSM resources M805V1 Production scheduling
Composite Data 500-SERIES M501V1 M501SM M503V1 M504V1 506V1 M516V1 Mine Models 600-SERIES M601V1 M649V1 M655V1 M654Vn M656V1 M657Vn M630V1 Initialize model (block, surface, GSM) Load digitized data into VBM file Plot intersection of digitized data; cutting plane Plot digitized data Generate model codes from digitized data Generate model codes from digitized topography Load surface topography model Composite over benches Composite over seams List composite data Plot composite bench maps Sort composite data for interpolation Plot composite cross-sections
Page INTRO-4
Revised: 24-August-01
MineSight Memo Mintec, Inc. 3544 E. Ft Lowell Rd Tucson, Arizona 85716-1705 Fax (520) 325-2568
FROM:
PROGRAM:
REVISION DATE:
PLATFORM:
PC
Workstation
PROBLEM DESCRIPTION: (Please attach any applicable input, output or other reference information)
REFERRED TO:
COMPLETED:
LIST EXCEPTIONS:
AUTHORIZED BY:
GETTING STARTED
In This Section
OVERVIEW OF FILES
TYPE OF FILE: ASCII OR BINARY . . . . . . . . . . . . . . . . . . . . . . . . . . 1 PURPOSE OF FILE: INPUT OR OUTPUT . . . . . . . . . . . . . . . . . . . . . . . 1 M ineSight DATA FILES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 FILE NAMING CONVENTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Data Files Run Files Input/Output Data Files Printer Output Files Plot Files PROJECT DIRECTORY FILES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Peripheral Interface Files Menu System Files Temporary Files The Defil Sub-Directory Files
Revised: 24-August-01
Page START-i
GETTING STARTED
Page START-ii
Revised: 24-August-01
GETTING STARTED
OVERVIEW OF FILES
TYPE OF FILE: ASCII OR BINARY
M ineSight uses two types of files: ASCII and binary. ASCII (American Standard Code for Information Interchange) files are written in alphabetic and numeric characters, that is, readable text. ASCII files may be opened and edited by using your computers text editor. Most ASCII files are sequential, meaning they are accessed line by line. Examples of ASCII files are:
MineSight run files, containing the options and parameters needed to run a program
Revised: 24-August-01
Page START-1
GETTING STARTED
The M ineSight file naming conventions described below are those used in the menu system. They are applicable to PC, Sun and VAX systems.
Data Files Use the leading characters of the filename for the project identification. Make the file reference number the last two characters of the filename. The extension for a data file is DAT. Examples: SAMP10.DAT for the sample project PCF GOLD11.DAT for a gold project Assay File
Run Files The leading characters of the filename are RUN. The last three are a reference to the program the run file will execute. The extension is alphabetic and is sequenced according to the order in which the runs are made (e.g., A=first run, B=second run, etc.). Examples: RUN201.A for the first run file for M201V1 RUN203.B for the second run file for M203V1
Page START-2
Revised: 24-August-01
GETTING STARTED
Input/Output Data Files The leading characters of the filename are DAT. The last three are a reference to the program requiring or generating the data. The extension is I followed by an alphanumeric reference for input and O followed by an alphanumeric reference for output. Examples: DAT201.IA for the input file for M201V1 DAT207.OA for the output file from M207V1
Printer Output Files The leading characters of the filename are RPT. The last three are a reference to the program from which the report is being produced. The extension is L (for Listing) followed by an alphabetic sequence character indicating the order in which the report was produced. Examples: RPT201.LA RPT204.LB
for the first printer output file from M201V1 for the second printer output file from M204V1
Plot Files The leading characters of the filename are PLT. The last three are a reference to the program from which the plot file is being produced. Both ASCII and binary plot files are generated for processing by M122V1. The extension contains an indication as to whether the file is ASCII or binary, as well as an alphabetic sequence character indicating the order in which the plot was produced. Examples: PLT607.PBA for the first binary plot file from M607V3 PLT721.PAC for the third ASCII plot file from M721V1
Revised: 24-August-24
Page START-3
GETTING STARTED Temporary Files All files that start with PIP and some that start with FOR are temporary files created by the menu system procedures. Files beginning with TMP are temporary work files. These are deleted when a procedure finishes successfully. If a procedure is interrupted, either by the user or by an error, the PIP/TMP files may not be erased. If you notice any on your disk, you can manually erase them. Files starting with FOR can also be temporary report files. They are created when you do not specify a report file name.
Page START-4
Revised: 24-August-01
GETTING STARTED
Icons
Menu Choices
LOAD DATA
FTR INDEX FTR QUERY SAVE VBM UTILITIES GRID DISP MODL
CURS ATTR
Info
Radar 1 2 3
Revised: 24-August-01
Page START-5
GETTING STARTED
ICONS
Zoom Out Icon Restores the project window to the previous zoom window
Metafile Manager Controls use of metafiles through the index file, PROJMETA.NDX
Add Objects Icon Allows you to create text and figures for overlays that can then be stored as metafiles
Hardcopy Icon Creates Postscript, HPGL or CGM output files from the current screen image
Page START-6
Revised: 24-August-01
GETTING STARTED
2.
3.
Click right to exit the help text. Position the mouse inside the help menu box and click right to exit a help menu.
Revised: 1August01
Page START-7
GETTING STARTED
INTERACTIVE PROGRAMS
M ineSight program names that end with TS or FS indicate that the program is interactive. Type the command to run the program according to your computer system (e.g., MEDS M202FS). All further information necessary for the program run is requested on the screen. In the TS program documentation, all computer messages and responses are written in bold caps. All user responses are in caps only. FS programs are illustrated with sample screens, showing the forms used for data input and reports.
Revised: 24August01
GETTING STARTED
RUN INFORMATION
The next line is your description of the run which will be listed at the top of each page of printed output. You can enter up to 80 characters on this line.
RUN OPTIONS
The number and type of options and parameters vary with each program and are listed in each programs documentation. They are entered in the run file as: option = value1 value2 . . . / comment
NAMES LINE
Each Names Line has the following format: MEDSpgmnm 10=filename ##=filename The first 10 columns are the system and program name (MEDSpgmnm). The first 4 columns (MEDS) can be any letters, such as COAL, URAN. They are followed by a program name (e.g., 101V1). Do not include the M (M101V1) in the program name. 10=filename is the name of the Project Control File that every M ineSight program accesses. ##=filename is the name of each additional file required by the particular program. This information is found in each programs documentation. ## is the MineSight data file reference number. The Names Line can sometimes require two lines of input. If so, add a semicolon at the end of the first Names Line, then start the second one with the same program name (MEDS-nnnVn) and the additional filenames. A sample Names Line for M201V1 is: MEDS-201V1 10=SAMP10.DAT 11=SAMP11.DAT; MEDS-201V1 12=SAMP12.DAT 3=RPT201.LA
where option is a 3-5 letter command (listed below) and value is the required numeric or alphanumeric values. You can enter values for several successive options on a single line for the ALF, IOP, PAR, MAP and PLT commands. Use at least one blank space to separate each value (e.g., if IOP1=1 and IOP2=2, both IOP values may be listed on one line: IOP1=1 2). The / ends the input of information; anything following it is considered to be a comment for your own information. The types of commands that are used in a run file are described below.
Commands with Numeric Values IOP# = value(s) PAR# = value(s) MAP = values PLT = values Integer run options Real number parameters Map limits Plot specifications
NOTE: The # in IOP and PAR commands is an integer between 1 and 40. The IOP values are integers while the PAR, MAP and PLT values are real numbers.
Revised: 24August01
Page START-9
GETTING STARTED Commands to Control Item Selection from Files GET# = label(s) PUT# = label(s) UPD# = label(s) INP# = label(s) OUT# = label(s) Items to be retrieved from a file Items to be stored into a file Items to be updated in the file Items to be input by the program Items to be output by the program
Commands to Supply Additional Run Information COM COM* DOC Comment line to be listed on the first print page Comment line to be listed on the first print page and in the Project History File Comment line to be listed at the top of each print page
NOTE: The # above is the M ineSight data file reference number. The labels must begin with an alphabetic character and be separated by at least one blank column. In some cases, it may be necessary to use two lines to contain all of the item labels. Start the second line with the same command and reference number as the first. You do not need a semi-colon at the end of the first line as in the Names Line.
NOTE: There can be any number of comment lines and up to five DOC lines per run, with each DOC line containing a maximum of 50 characters.
Auxiliary Commands ALF# = label(s) FMT# = ( ... ) RUN = label Alphanumeric labels FORTRAN format statements (See section below) Option in some programs to specify type of run
Commands to Specify Run Alternatives ITM# = label value Definition of run items The # above refers to a sequential integer value starting with 1 for the first ITM command. ITM commands must always be numbered sequentially regardless of the order of listing in the documentation. Commonly used ITM commands are RANGE, OMIT and TABLE. ITM# = label-nn RANGE min-value max-value RANGE tells the program to use a range of values for label-nn beginning with min-value and ending with maxvalue. The program will automatically decrease the minvalue and increase the max-value by the rounding factor that is set for the project when it is initialized. ITM# = label-nn OMIT min-value max-value OMIT tells the program to omit the values for label-nn from min-value to max-value. ITM# = label-nn TABLE IOPm IOPn TABLE tells the program to look for a table of values for label-nn in IOPm through IOPn. Label-nn is an item selected from MineSight data file nn. You can use any range of IOPs between 1 and 40 unless they are already used in the program. This example from M208RP limits the ROCK codes used to 1, 3 and 6 only. ITM1 = ROCK TABLE 30 32 IOP30 = 1 3 6
Commands to Control Print Output PAG = n n = number of lines to print on each page (Default = 60 for 6 lines per inch) Level of print output Prints a full summary of files to be used during the run and, in some programs, will print a run summary on the screen. Prints a summary of items for each file on the screen along with other information which will aid the engineer on call in resolving any problems.
I-O = 0, 1 or 2 I-O = 1
I-O = 2
END
The END line indicates the end of options and parameters for a run. This line is required in every run file.
ADDITIONAL DATA
The documentation for each program will inform you of any data that may be required after the END line. Some examples are boundary points, drillhole selection lines, and input data lines.
Page START-10
Revised: 24-August-01
GETTING STARTED
An example of a FORTRAN format statement is: (10A1,2F10.0,1X,I5) FORTRAN formats are always entered in parentheses.
Revised: 24-August-01
Page START-11
GETTING STARTED
C O Comment Lines M COM D H D A T A L O A D F U N C T I O N C O M COM LOAD DRILLHOLE DATA TO FILES 11 & 12. COM REF#s TO BEGIN STORING DATA ARE BY DEFAULT SET TO COM ONE FOR INITIAL LOAD. IOP1 = 1 / FIRST DATA UNIT TO BE STORED IN FILE 11 IS REF# 1 IOP2 = 1 / FIRST DATA UNIT TO BE STORED IN FILE 12 IS REF# 1 IOP3 = 19 / n=UNIT# TO READ DATA; 0=DATA IN RUN FILE IOP4 = 0 / 0=LIMIT PRINT OUTPUT; 1=PRINT ALL INPUT IOP6 = 1 / 1=ADD INTERVALS IF DH GAPS; 0=IGNORE GAPS COM INPUT DATA FORMATS SHOULD BE THE SAME AS THE COM M200 RUN. FMT1 = (1X,10A1,3F10.2,A1,F8.0,A1,F6.0,F1.0,F8.0) FMT2 = (1X,10A1,3F9.2,F7.2,F7.3) COM ASSAY ITEM ORDER WITHIN INPUT DATA. INP11= FROM -TO- -AI- T-CU MOLY I-O = 1 / LIST A LINE OF INFO FOR EACH DH INPUT END End Line Run Options
Page START-12
Revised: 24-August-01
GETTING STARTED
b. c.
b.
c.
d.
e.
d.
f.
b.
c.
c.
Revised: 24-August-01
Page START-13
GETTING STARTED
Page START-14
Revised: 24-August-01