{
    "document_id": 16824,
    "page": 63,
    "width_pt": 612,
    "height_pt": 792,
    "rotation": 0,
    "pipeline_version": "paddleocr-vl-1.6+paul-48",
    "engine": "paddleocr_vl",
    "source_run_id": 16935,
    "item_count": 6,
    "counts_by_type": {
        "caption": 1,
        "footer": 1,
        "heading": 1,
        "text": 3
    },
    "build_ms": 1,
    "items": [
        {
            "id": "p63.1",
            "order": 1,
            "type": "text",
            "bbox": {
                "l": 68.64,
                "t": 718.56,
                "r": 543.6,
                "b": 496.08
            },
            "text": "During the course of the project, we were able to successfully transfer data onto the computer’s memory so that the information wouldn’t be erased or altered in any way. At first, we had many complications with writing the code, but as we continued to develop our skills, the complications and errors became less and the codes would run with greater ease. Among the many important things we learned were that coding is very tedious and you have to pay careful attention to everything that you are putting into that specific coding program. Mistakes that are coded using Python, for example, can be very hard to identify and correct if the debugging features (figure 1) in Python were not robust. Once the code was completed, the data we had collected was visualized using two different types of graphs. Low-resolution graphs were created to conserve data bandwidth when sharing, while high-resolution graphs were created for publication."
        },
        {
            "id": "p63.2",
            "order": 2,
            "type": "text",
            "bbox": {
                "l": 73.2,
                "t": 470.64,
                "r": 546,
                "b": 416.64
            },
            "text": "Traceback (most recent call last):\nFile \"C:\\Users\\leah.jackson\\Desktop\\env-data\\python\\analyze.py\", line 4, in <module>\nimport matplotlib\n\nImportError: No module named 'matplotlib'",
            "attrs": {
                "block_label": "algorithm"
            }
        },
        {
            "id": "p63.3",
            "order": 3,
            "type": "caption",
            "bbox": {
                "l": 69.6,
                "t": 407.76,
                "r": 541.92,
                "b": 384.24
            },
            "text": "Figure 1. The “error traceback” messaging feature within the Python scripting shell environment is very useful for highlight code errors. This message is generated anytime a syntax error is committed.",
            "attrs": {
                "block_label": "figure_title"
            }
        },
        {
            "id": "p63.4",
            "order": 4,
            "type": "heading",
            "bbox": {
                "l": 244.32,
                "t": 356.16,
                "r": 367.92,
                "b": 343.92
            },
            "text": "Methods and Materials",
            "attrs": {
                "block_label": "paragraph_title"
            },
            "level": 3
        },
        {
            "id": "p63.5",
            "order": 5,
            "type": "text",
            "bbox": {
                "l": 68.16,
                "t": 336,
                "r": 543.84,
                "b": 114.24
            },
            "text": "To be able to save digital information properly, the following items are needed: a computer, the latest version of Python IDLE, the program SourceTree, and plenty of time because this process can take a lot of it. Using Source Tree, we can share the changes made on the document with our peers and vice versa. In order to save the information without someone getting to it and altering it, we would use PuTTyGen to generate either a public or private key to control access. Generating the private key will assure that any information on there will not be accessed by anyone else other than the owner or permitted user. When making changes to the information, we would have to commit those changes and then proceed to push the changes, which our peers would then pull to have changes saved to their version of the file. One good thing about Source Tree is that even if the changes are deleted from the person's computer it is still saved to Source Tree as a backup for emergencies."
        },
        {
            "id": "p63.6",
            "order": 6,
            "type": "footer",
            "bbox": {
                "l": 299.04,
                "t": 60,
                "r": 313.2,
                "b": 49.68
            },
            "text": "59",
            "attrs": {
                "block_label": "number"
            }
        }
    ],
    "excluded_furniture": {
        "first": [],
        "last": []
    }
}