<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Learnings on Aziz&#39;s Portfolio | Amirul Abdul Aziz</title>
    <link>//azizamir.github.io/learnings/</link>
    <description>Recent content in Learnings on Aziz&#39;s Portfolio | Amirul Abdul Aziz</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 07 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="//azizamir.github.io/learnings/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>1D Basin Modeling</title>
      <link>//azizamir.github.io/learnings/learning-04/</link>
      <pubDate>Sun, 07 Jun 2026 00:00:00 +0000</pubDate>
      
      <guid>//azizamir.github.io/learnings/learning-04/</guid>
      <description>I was enrolled in practical courses on 1D basin modeling in September 2025. Throughout this course, I learned the fundamentals of basin modeling and common workflow of 1D basin modeling using Petromod software.
Data Importing Importing the well &amp;amp; calibration data to be used for modeling process.
Figure 1. Well &amp;amp; calibration data importing
Model Setup Creating the 1D model and importing the main data (stratigraphy, age, thickness, deposition, erosion, lithology, PSE, TOC, kinetic, and HI) &amp;amp; boundary condition data (PWD, SWIT, HF).</description>
    </item>
    
    <item>
      <title>Qualitative Seismic Interpretation</title>
      <link>//azizamir.github.io/learnings/learning-01/</link>
      <pubDate>Sun, 07 Jun 2026 00:00:00 +0000</pubDate>
      
      <guid>//azizamir.github.io/learnings/learning-01/</guid>
      <description>I was enrolled in practical courses of qualitative seismic interpretation in February 2024. I gained practical experience in using Petrel features &amp;amp; perform effective seismic interpretation.
Seismic Data Loading Importing .segy data, converting .segy into .zgy data to generate time slices, and reconnecting missing data.
Figure 1. Types of seismic data and bit &amp;amp; petrel troubleshooting features
Data Preparation for Seismic Intepretation Preparing the seismic data by adjusting the color table, opacity, and utilize the bump mapping features to enchance seismic interpretation process.</description>
    </item>
    
    <item>
      <title>Quantitative Seismic Interpretation</title>
      <link>//azizamir.github.io/learnings/learning-02/</link>
      <pubDate>Sun, 07 Jun 2026 00:00:00 +0000</pubDate>
      
      <guid>//azizamir.github.io/learnings/learning-02/</guid>
      <description>I was learned quantitative seismic interpretation through a public lecture course in November 2024. This course taught me how to perform various seismic QI implementations, such as AVO modeling, pre-stack seismic inversion, and post-stack seismic inversion using demo data with Hampson-Russell software.
AVO Modeling Performed AVO modeling, including fluid replacement modeling (FRM), well log conditioning, wavelet &amp;amp; synthetic seismogram extraction, pick analysis, and AVO attribute volume analysis to analyze how different fluid types will affect rock property &amp;amp; AVO responses.</description>
    </item>
    
    <item>
      <title>Static Reservoir Modeling</title>
      <link>//azizamir.github.io/learnings/learning-03/</link>
      <pubDate>Sun, 07 Jun 2026 00:00:00 +0000</pubDate>
      
      <guid>//azizamir.github.io/learnings/learning-03/</guid>
      <description>As part of my learning routines, I’m reviewing my knowledge on reservoir modeling, particularly on static reservoir modeling workflow through a public course from March to October 2024. The course using the Gulfaks field, an oil &amp;amp; gas field located in the Norwegian part of the North Sea shelf that operated by Statoil since 1986, as the demo data. Throughout this course, I learn a complete workflow of reservoir static modeling, from data loading to volumetric calculation.</description>
    </item>
    
  </channel>
</rss>
