Wells from your files

LAS headers and well-tops tables name the wells they belong to. When those wells are not in your project yet, Ophiolite lists them after the upload or import finishes, and creates them, with their wellbores, when you confirm. Every file and sheet is then linked to its well or wellbore. Nothing is created before you press the button, and you can undo it while nothing else refers to the new wells.

A name is matched the same way everywhere: TM-2, tm 2 and TM-02 are one name, and a name you once said is another name for a well (TM3C for Tubbergen-Mander-3C) is matched from then on. A LAS header names a wellbore; a column of a table names a well. When both name the same well, it becomes one well with its wellbore, never two.

In Workspace

1. Add your files: a folder of LAS files with Add data, a tops table as in A spreadsheet becomes wells and tops. When the upload or import has finished, its report says how many wells its files name that are not in the project (“21 files and 2 tables name 9 wells that are not in this project.”). Choose Review the wells.

2. The list shows each name once, what the files call it (“Named as a wellbore in 7 files.”) and where they say it (“The LAS header of RUN_06.las names the wellbore “TM-2”.”). Add files from another upload or import adds the wells of your other uploads and imports to the same list.

3. Answer the names you know. Nothing is chosen for you:

   • Create it: a new provisional well (and its wellbore, for a LAS file).
   • This is one I have: choose the well or wellbore. The name stays as another name for it.
   • Not this one: nothing is created or linked for this name.

   A name two of your wellbores share asks which one; it is never created again.

4. Press Create these 9 as provisional wells (the count follows your answers; with every name answered the button is Save your answers). The result says what happened: “Created 9 wells and 8 wellbores. Linked 24 files and sheets. 0 left.”

Provisional wells have no registry number yet; you can attach one later on the well’s page. People who can read the files can see the wells created from them. The well’s page shows the other names it was given (“Also known as: TM3C (Ana, 7 October).”) and Activity names who added them.

Remove the wells this created undoes it: the wells and wellbores are removed, the files stay and are no longer linked to a well. It is refused while other data refers to the wells; the sentence names that data.

In Python

Bring the uploads and imports whose files name wells. The examples use a LAS file and a tops table of the geothermal well HON-GT-01 and NLOG’s tops workbook (public data from NLOG.NL, the Dutch subsurface portal):

folder = "F-MIX"                        # HON-GT-01.las, whose header names the wellbore HON-GT-01
table = "hon_gt_01-tops.csv"            # well, surface, md_m: the tops of well hon_gt_01
workbook = "nlog-tops.xlsx"             # the tops of HON-GT-01 and NLW-GT-01

Upload the folder and import the tables; each is one run, and the list is made over all of them:

upload = client.upload_runs.upload(folder, attribution="NLOG.NL", rights_confirmed=True)
first = client.imports.from_table(table, "well-tops", {"well": "well", "name": "surface", "md": "md_m"}, declarations={"depth_unit": "m"})
second = client.imports.from_table(workbook, "well-tops", {"well": "Well", "name": "Formation", "md": "Top MD (m)"}, declarations={"depth_unit": "m"})
runs = [upload.run_id, first["run"]["id"], second["run"]["id"]]

List the wells they name. The list reads and changes nothing, in the same words as Workspace:

from ophiolite.well_names import list_lines, result_line, went_back_line

listed = client.well_names.proposals(runs)
print("\n".join(list_lines(listed)))

Create every name nothing you can read is called, and link every file and sheet. digest says which list you reviewed: if the files or who can read them changed since, nothing is created and you list again:

accepted = client.well_names.accept(runs, digest=listed["digest"], create_all=True)
print(result_line(accepted))

To answer names one by one, pass create=["TM-2"], is_={"TM3C": wellbore_id} or skip=["TM-9"]; link_exact_only=True links only the names that have their one match and creates nothing. The same command_id returns the same answer, so an accept retried after a lost connection does not create twice.

Go back removes what the accept created while nothing else refers to it; the files stay:

back = client.well_names.go_back(runs)
print(went_back_line(back))

A refusal is raised with the sentence Workspace shows (“The files or who can read them changed after you opened this list. Nothing was created. Open the list again.”); the service’s own text is kept as server_message.

On the command line

ophiolite wells from-run UPLOAD IMPORT IMPORT
ophiolite wells from-run UPLOAD IMPORT IMPORT --create-all
ophiolite wells from-run UPLOAD --create "TM-2" --is "TM3C=WELLBORE" --skip "TM-9"
ophiolite wells from-run UPLOAD --link-exact-only

Without a decision the command prints the list and changes nothing; --dry-run with a decision does the same. --create-all and --link-exact-only cannot be given together. ophiolite upload ends its report with the wells its files name and the command that lists them. --json prints the service’s answers.

When it is refused

You see	What to do
Only people who can edit this project can add wells. Ask a project administrator to give you edit access.	Ask an administrator for edit access.
The files or who can read them changed after you opened this list. Nothing was created. Open the list again.	List again and answer the new list.
A well called TM-3C was added since you opened the list. …	List again; the name now links to that well.
“TM3C” could mean more than one wellbore you can read. Choose which one.	Answer This is one I have with the one you mean.
The files in … are still being read. Wells can be created when they finish.	Wait for the upload or import to finish.
This list names 640 wells. Ophiolite creates up to 500 at once. …	Create 500, then list again.
The wells were not removed: later data refers to them. …	Remove or move that data first, or keep the wells.
Only the person who created these wells, or a project administrator, can remove them.	Ask that person or an administrator.
Choose between 1 and 50 uploads or imports to list the wells they name.	List fewer runs at a time.