Skip to content

Notebook gallery

Each notebook runs on its own: download it and requirements.txt into an empty folder and follow its first cell. Without a project address it works on a synthetic log served on your own computer, so nothing real is read or published. To work in your project, put the configuration.json from Connect → Use Python in that folder and run ophiolite login there first. Open a starter pack is the exception: it reads a starter pack you downloaded, without a project.

Every notebook here is run before a release: downloaded into an empty folder with a fresh kernel, and, all but the starter pack notebook, against a project of the release.

Read one gamma-ray curve exactly as it was uploaded, with its units and depth reference, and plot it.

  • Data: A synthetic five-sample gamma-ray log, or a log in your project.
  • Modes: runs on your own computer without a project; runs in your project after ophiolite login.
  • Download: read-a-well-log.ipynb and requirements.txt

Pick clean and shale values, compare the five methods, publish one result and add a second version with a changed pick.

  • Data: A synthetic five-sample gamma-ray log, or a log in your project; publishing creates a result only you can see until you share it.
  • Modes: runs on your own computer without a project; runs in your project after ophiolite login.
  • Download: shale-volume-from-gamma-ray.ipynb and requirements.txt

Compute a 30 Hz Ricker wavelet, check its strongest frequency against the declared one, upload it and add a second version.

  • Data: Computed on your computer; uploading creates a wavelet only you can see until you share it.
  • Modes: runs on your own computer without a project; runs in your project after ophiolite login.
  • Download: make-a-wavelet.ipynb and requirements.txt

Take two rocks from a well log, build a wedge model, compute its synthetic with a Ricker wavelet and read the tuning thickness.

  • Data: Rock values measured on the HON-GT-01 excerpt, or recomputed from the HON-GT-01 log in your project; publishing creates results only you can see until you share them.
  • Modes: runs on your own computer without a project; runs in your project after ophiolite login.
  • Download: make-a-wedge-model.ipynb and requirements.txt

Send a seismic volume larger than one request in parts, continue it after an interruption, and read the original back by ranges.

  • Data: A synthetic 19 MiB volume made on your computer; sending creates a volume only you can see until you share it.
  • Modes: runs on your own computer without a project; runs in your project after ophiolite login.
  • Download: large-files.ipynb and requirements.txt

Upload a folder of well logs in one step and read one report that says what became of each file and which wellbore each log names.

  • Data: A synthetic folder of five files made on your computer; uploading creates files only you can see until you share them.
  • Modes: runs on your own computer without a project; runs in your project after ophiolite login.
  • Download: a-well-folder-in-one-report.ipynb and requirements.txt

Compute the two-way times of a two-layer velocity model, write them as a time-depth table with its declarations, and upload it.

  • Data: Computed on your computer; uploading creates a table only you can see until you share it.
  • Modes: runs on your own computer without a project; runs in your project after ophiolite login.
  • Download: time-depth-table.ipynb and requirements.txt

Draw two field outlines as a GIS file stores them, a hole kept empty, declare what the file leaves open, and upload them as a map layer.

  • Data: Drawn on your computer; uploading creates a map layer only you can see until you share it.
  • Modes: runs on your own computer without a project; runs in your project after ophiolite login.
  • Download: grids-and-gis-files.ipynb and requirements.txt

Publish a result and a second version, then read how each was made, what changed between them, what was made from the log, and whether it can be made again.

  • Data: A synthetic five-sample gamma-ray log, or a log in your project; publishing creates a result only you can see until you share it.
  • Modes: runs on your own computer without a project; runs in your project after ophiolite login.
  • Download: how-was-this-made.ipynb and requirements.txt

Publish a result, open its exact version in the Workspace from the notebook, and add the next version with its Send again line, which refuses once someone else added one first.

  • Data: A synthetic five-sample gamma-ray log, or a log in your project; publishing creates a result only you can see until you share it.
  • Modes: runs on your own computer without a project; runs in your project after ophiolite login.
  • Download: open-it-here.ipynb and requirements.txt

Say which column holds what, review what a table of formation tops would add, then add it and read one line per set.

  • Data: A synthetic six-row tops table made on your computer; adding it creates sets of tops only you can see until you share them.
  • Modes: runs on your own computer without a project; runs in your project after ophiolite login.
  • Download: a-spreadsheet-becomes-wells-and-tops.ipynb and requirements.txt

Read the layers QGIS opens from your project, every collection page by page, see why a path is not placed, and draw the wellbore paths in plan view.

  • Data: Two pages written in the notebook, or the layers you may read in your project; reading changes nothing.
  • Modes: runs on your own computer without a project; runs in your project after ophiolite login.
  • Download: layers-for-a-gis.ipynb and requirements.txt

Browse a folder of well logs in your organisation’s storage bucket, add it read from your storage each time, and see why a file that later changes is reported instead of read.

  • Data: Two synthetic gamma-ray logs made on your computer, or a folder of a storage connection your organisation added; nothing is written to your storage.
  • Modes: runs on your own computer without a project; runs in your project after ophiolite login.
  • Download: well-logs-in-a-bucket.ipynb and requirements.txt

Check a tool and run it on your computer, add it to your project privately, enable it, and run it as a colleague who is asked once to trust it.

  • Data: Two synthetic formation tops and the SDK’s sample depth-shift tool; in your project it adds a private tool only you and the administrators see until one enables it.
  • Modes: runs on your own computer without a project; runs in your project after ophiolite login.
  • Download: share-a-procedure.ipynb and requirements.txt

Read the projects you reach and the last day your access to each lasts, then who has access to this project, through what, and until when.

  • Data: A synthetic project with four people, or your project; nothing is changed, and who has access is shown to project administrators only.
  • Modes: runs on your own computer without a project; runs in your project after ophiolite login.
  • Download: who-has-access-until-when.ipynb and requirements.txt

See where the wells you may read are located, draw them, and read one well’s data together with its wellbores’.

  • Data: Three synthetic wells, one with a wellbore and a log, or the wells you may read in your project; reading changes nothing.
  • Modes: runs on your own computer without a project; runs in your project after ophiolite login.
  • Download: where-are-my-wells.ipynb and requirements.txt

Keep a spreadsheet as it is with its units and missing-value marker, read a database table, and join the two on the well name.

  • Data: A synthetic six-sample spreadsheet and a three-well database made on your computer; keeping the spreadsheet creates a table only you can see until you share it.
  • Modes: runs on your own computer without a project; runs in your project after ophiolite login.
  • Download: a-spreadsheet-and-a-database-joined.ipynb and requirements.txt

Read the same table of wells from a SQL Server and an Oracle database at their recorded revisions and check that both give the same wells at the same coordinates.

  • Data: Three Groningen wells typed as each system returns them; in a project, the two SQL sources you selected, read only.
  • Modes: runs on your own computer without a project; runs in your project after ophiolite login.
  • Download: wells-from-sql-server-and-oracle.ipynb and requirements.txt

Search the Dutch oil and gas portal NLOG for wells, see what it holds for each one, bring their positions into your project and draw them on a map.

  • Data: What NLOG listed for the HON-GT wells on 1 October 2026 (Source: NLOG.NL), or NLOG itself through your project; bringing wells in creates wells only you can see until you share them.
  • Modes: runs on your own computer without a project; runs in your project after ophiolite login.
  • Download: public-repository-to-map.ipynb and requirements.txt

Shale volume and density porosity from a log in your project with the notebook’s own functions, published back as a result that names the exact log version it came from.

A log from your project as a lasio LASFile: every lasio cell of the original runs on it after one changed line.

Build a LAS file from a table with lasio and upload it to your project as an original in one call.

A deviation survey becomes a well path with wellpathpy, and the same survey kept in your project gives the same positions through Ophiolite.

Make a working tool for a step and a kind of data, valid as it is made, and see which pairs have a start.

Write the residual report’s steps as a recipe, check it, and in your project run it step by step, continuing after a stop.

  • Data: A recipe written in the notebook; in your project the well set and the surface you name, and the residual tool your project holds.
  • Modes: runs on your own computer without a project; runs in your project after ophiolite login.
  • Download: a-recipe-runs-again.ipynb and requirements.txt

Run a tool on your computer, then run its card’s “Run again” line: the same tops again, and a refusal once the tool changed.

  • Data: Two synthetic formation tops and a tool made from the well-tops template; nothing is added to a project in either mode.
  • Modes: runs on your own computer without a project; runs in your project after ophiolite login.
  • Download: run-it-again.ipynb and requirements.txt

Read the seismic and well files of a starter pack you downloaded, draw one inline with the wells on it, and check what you read against the values the pack was built with.

  • Data: The starter pack folder you downloaded; the notebook reads nothing else and sends nothing.
  • Modes: runs on your own computer against a starter pack you downloaded, with the network off.
  • Download: open-a-starter-pack.ipynb and requirements.txt

requirements.txt installs the exact SDK these notebooks were published with.