MediaWiki API result

{
    "batchcomplete": "",
    "query": {
        "pages": [
            {
                "ns": 0,
                "title": "API",
                "missing": ""
            },
            {
                "pageid": 1,
                "ns": 0,
                "title": "Main Page",
                "revisions": [
                    {
                        "user": "Markusblatt",
                        "timestamp": "2022-03-29T13:43:32Z",
                        "slots": {
                            "main": {
                                "contentmodel": "wikitext",
                                "contentformat": "text/x-wiki",
                                "*": "= Getting started with OPM =\n\nWe have a [[Quick Installation]] guide, showing how to install the opm-core library.\n\nThe [[FPGA setup and building]] guide explains how to compile and use the ''bitstream'' for the FPGA-enabled Flow simulator.\n\nThe [//opm-project.org/?page_id=43 tutorials] section contain some tutorials for programmers using opm-core.\n\nConsult the [//meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.\n\n'''''Please note that the content of this wiki is in the process of being updated, many parts are not current!'''''\n\n= User documentation for selected programs =\n* Black-oil reservoir simulator Flow:\n** [[Black-oil simulator|Black-oil simulator]]\n** [[Thermal simulator|Thermal simulator]]\n** [[Water evaporation|Water evaporation]]\n** [[Salt precipitation|Salt precipitation]]\n* [[CO2 sequestration]]\n* [[Enhanced oil recovery]]\n* [[Geothermal flow_onephase_energy]]\n*  [[Upscaling]]\n\n= Developer Information =\n\n=== How to contribute ===\n\nOPM tries to follow a development model which is as open as possible. Therefore, all development happens on [//github.com/OPM github]. The process of contributing changes is the following:\n* Fork the module for which you want to propose a change on github\n* Locally create a new branch of the module's repository which contains your changes\n* Push this branch to your personal github fork\n* [https://help.github.com/articles/using-pull-requests Create a pull request]\n* To make a pull request (PR) easy to review (and likely to be merged):\n** A PR should contain a single feature, preferably with a unit test.\n** It should not be too large. If you change lots of lines in lots of files in an automatic refactoring, show the script/commands you used.\n** If you change existing code, do not mix feature changes and (large amounts of) pure formatting changes (use a separate PR for that).\n** [http://codeinthehole.com/writing/pull-requests-and-other-good-practices-for-teams-using-github/ Some more tips on PRs]\n* After some discussion, one of the module maintainers will either merge your changes, or your changes will be rejected with an explanation why they are a bad idea.\n* Often, you will be asked to make some modification to the code in the PR. Do this locally, and push the changes to the same repo and branch that you used for the PR. It will be updated automatically (as a corollary, do not use this branch for unrelated development -- start a new one instead).\n\n=== Coding standard ===\n\nWe do not at the moment mandate a specific coding standard, but in practice we try to have a\nhomogenous code base, and encourage all contributors to follow certain practices.\n\nThese are listed in the [[Suggested coding standard]].\n\n=== List of module maintainers ===\n\nThe current module maintainers (and their github user names) are:\n\n* '''opm-common''': Atgeirr Rasmussen (@atgeirr), B\u00e5rd Skaflestad (@bska), Arne Morten Kvarving (@akva2), Joakim Hove (@joakim-hove), Markus Blatt (@blattms)\n* '''opm-material''': Tor Harald Sandve (@totto82), Atgeirr Rasmussen (@atgeirr)\n* '''opm-grid''': Atgeirr Rasmussen (@atgeirr), B\u00e5rd Skaflestad (@bska), Markus Blatt (@blattms) and Robert Kl\u00f6fkorn (@dr-robertk)\n* '''opm-models''': Tor Harald Sandve (@totto82), Atgeirr Rasmussen (@atgeirr)\n* '''opm-simulators''': Atgeirr Rasmussen (@atgeirr), B\u00e5rd Skaflestad (@bska) and Robert Kl\u00f6fkorn (@dr-robertk)\n* '''opm-tests''': Alf Birger Rustad (@alfbr), Torbj\u00f8rn Skille (@tskille) and B\u00e5rd Skaflestad (@bksa).\n* '''opm-upscaling''': Arne Morten Kvarving (@akva2)\n* '''ResInsight''': Magne Sjaastad (@magnesj) and Jacob St\u00f8ren (@JacobStoren)\n\n=== Jenkins information ===\n\n[https://ci.opm-project.org Jenkins dashboard].\n\nInformation about [[Jenkins triggers]].\n\n=== Nightly binary packages for Ubuntu and Red Hat ===\n\nList of available [https://opm-project.org/package/ nightly images] generated by Jenkins. Note that in order to use the Ubuntu binaries you must add the PPA containing these nightly binaries:\n # NOTE: you may need to sudo some of these apt commands!\n # Add gpg key for repository\n wget -qO - https://opm-project.org/package/nightly-bionic/repokey.gpg | apt-key add -\n # Add repo itself\n apt-add-repository https://opm-project.org/package/nightly-bionic\n # Look at available nightly versions\n apt-cache show libopm-simulators1-bin\n\n=== Static analysis tools ===\n\nInformation about [[static analysis tools]] available.\n\n=== Help for release managers ===\n\n[[Notes for managing release 2016.10]]\n\n=== Data required for output and restarting ===\n\n[[Data for output and restart]]\n\n=== Notes on Debian Packages ===\n\n[[Debian Packaging Workflow]]\n\n= Viewing ECLIPSE summary files =\n[//resinsight.org/ Resinsight] provides a state-of-the art solution for all post-processing of reservoir simulation, including plotting functionality for summary files. Resinsight can be installed from [//opm-project.org/?page_id=245 packages or source].\n\n== Through lightweight GUI ==\nFor those who like to keep clicking at a minimum, a lean plotting tool is found i qsummary. No binaries are available at the moment, so you will need to compile yourself from: \nhttps://github.com/OPM/qsummary\n\n== Through command-line ==\nA command-line application named ''summary'' is distributed with OPM packages, and can be compiled from source in https://github.com/OPM/opm-common\nIt will give you direct access to any summary vectors, which subsequently can be handled through gnuplot, spreadsheet, or whatever you choose.\n\n== Through Python script ==\nThe script is found in opm-utilities. The script in question is a Python script and some requirements must be satisifed:\n\n<ol>\n   <li> You need the Python packages <tt>matplotlib</tt> and <tt>numpy</tt>.</li>\n   <li> You must compile/enable ERT Python packages when building ert. Then make sure that the path <tt>CMAKE_INSTALL_PREFIX/python</tt> is in your <tt>PYTHONPATH</tt>.\n</ol>\n\nWhen everything is installed the <tt>summaryplot</tt> application can be used, it can plot mulitple realisations:\n\n<pre>\nsummaryplot WWCT:OP_1 CASE1.DATA CASE2.DATA\n</pre>\n[[File:Profile.png|border]]\n\n== Plots ==\nThe full Norne model is run once a week, and PDF document with all the well results is generated: http://95.85.43.55/plots/"
                            }
                        },
                        "comment": ""
                    }
                ]
            }
        ]
    }
}