Petrel Tutorial Link
On the left side of your screen is the Input pane. This is not a file browser; it is a database tree.
Golden Rule: Petrel only stores paths to your data. It does not embed files. If you move a seismic SEG-Y file on your hard drive, Petrel will lose track of it. Always organize your project folders before importing.
Petrel is a popular workflow platform for geoscience and reservoir modelling. This tutorial gives you a concise, hands-on guide to go from data import to a simple static model and basic visualization. Follow each step in order; default settings are used where choices aren’t specified. petrel tutorial
Horizons follow seismic reflectors.
Common Mistake: Auto-tracking jumps across faults. You must manually edit the horizon picks. Use the Edit Picks tool to delete obviously wrong picks (e.g., cycle skips). On the left side of your screen is the Input pane
Certainly! However, since "Petrel Tutorial" could refer to various resources (e.g., a YouTube series, a PDF guide, a paid online course, or a university handout), I’ll provide a general review based on common features of introductory Petrel tutorials. If you have a specific tutorial in mind (e.g., from SLB, a specific instructor, or platform), please clarify for a more tailored review.
Before any work begins, raw data must be imported into the project. Petrel supports various formats (LAS, DLIS, SEGY, etc.). Golden Rule: Petrel only stores paths to your data
Now we bring well logs into the 3D grid.
A typical Petrel workflow follows a logical sequence often referred to as the "Seismic-to-Simulation" workflow.
With data loaded, the next phase is interpreting seismic reflectors. In Petrel’s Seismic Interpretation window, users display inline and crossline sections, adjust color maps (e.g., seismic “wiggle” or variable density), and pick horizons. A typical tutorial exercise involves:
Fault interpretation follows a similar logic. Users map fault sticks on vertical sections, then generate fault surfaces using the Fault Modeling process. At this stage, the quality of the structural framework—how faults terminate and intersect—determines the robustness of the final grid. Tutorials often stress that less is more: starting with major faults before adding minor splices avoids computational instability.
