MediaWiki API result

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "Running_scripts_in_the_background",
        "continue": "gapcontinue||"
    },
    "warnings": {
        "main": {
            "*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce> for notice of API deprecations and breaking changes."
        },
        "revisions": {
            "*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
        }
    },
    "query": {
        "pages": {
            "54": {
                "pageid": 54,
                "ns": 0,
                "title": "Refined table",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "\nThe ''refined table'' is the result of the alignment iteration. ''Dynamo'' produces one refined table per iteration and reference.\n\nIt follows the ''Dynamo'' [[Table convention|convention]] for tables. In particular, ''Dynamo'' should fill some columns in a  ''refined table'' during alignment:\n* columns 3 (marks if the particle was actually used for the average produced at the iteration)\n* columns 4-9 (the alignment parameters)\n* column 10 10 (the cross correlation coefficient computed for the alignment particle)\n* column 34: In [[Multireference alignment|multireference projects]], the reference number that the particle has been assigned to.\n\n==Accessing the refined table ==\nThe {{t|ddb}} command provides easy access to the results of the project. Here some examples of syntax\n\nDisplay the name of the last computed table (by default, from reference 1)\n<tt>ddb myProjet:t -d</tt> \n\nDisplay the name of the tables computed for all iterations at one given reference:\n<tt>ddb myProjet:t:ite=*:ref=2 -d</tt> \n\nRead the refined table of iteration 3 into workspace variable {{t|myTable}}\n<tt>ddb myProjet:t:ite=1 -d</tt> \n\n==Sanity checks with the refined tables==\n\nDuring a project, it is useful to check how an alignment is going. The ''refined table'' gives a couple of handy options to check it visually.\n\n\n===Checking the aligned particles===\nYou can apply the computed alignment parameters into a few particles to check if they make sense. This is specially useful with membrane proteins.\n\n<tt>ddbrowse -p myProject </tt>\nwill open {{t|ddbrowse}} onto the data and the last available refined table of project {{t|myPoject}}\n\n{{docfunction|dynamo_data_browse|ddbrowse}}\n\n===Checking the orientations===\nYou can sketch the positions and orientations of particles after an alignment iteration. This is useful when scanning how a set particles selected by [[Seed oversampling]] is evolving during the iterarion.\n\nUse {{t|dtplot}} with the {{t|oriented_positions}} option as {{t|profile}}\n{{docfunction|dynamo_tableplot|dtplot}}"
                    }
                ]
            },
            "35": {
                "pageid": 35,
                "ns": 0,
                "title": "Resolution",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "'''Article under construction'''\n\n\n\n\nOne of the most widespread ways of simultaneously measuring resolution and driving the alignment is the so called \"golden standard\" method. A version of this approach is available in ''Dynamo'' with the name [[adaptive bandpass filtering]]  \n\n==Template bias==\n\n\n==Resolution and convergence=="
                    }
                ]
            }
        }
    }
}