Category Archives: General

GitHub Inventory and Housekeeping

Hello ArchaeoPY,

We are thrilled by the positive responses to our paper at the 2015 CAA UK hosted at Bradford this past weekend.

Chrys and Finn have finished taking inventory of what is currently in the ArchaeoPY repository. As a result, we have shuffled some things around, renamed some code to be more descriptive, and deleted a few extraneous files. A short inventory of what is currently available below:

ArchaeoPY Modeller - 2D resistivity and magnetic responses modeller over simple features. 3D modelling has been derived, but still needs to be implemented. Hasn't been forgotten--just taken a back seat to other tasks!


Filters: Contains filters (analytical signal and peak-finding, which for example, we recently used on EMI and mag data)

GUI Templates: Contains the base ArchaeoPY templates generated from Qt Designer... These may be re-thought at a later time. Originally ArchaeoPY was meant to have a template GUI, to which users could utilise to their own needs by importing in modules. Currently this template GUI is mpl, which contains a matplotlib canvas, with plotting and clearing buttons.

IO: Various in>out code. Includes binary data viewer and binary data savers (to dxf, txt, or png); image processing and saving GUI; EMI regridding GUI.

Plotting: Basic plotter GUI, now with statistical information and trendline plotting; multiple subplots plotting from the same file; and, in progress, multiple subplots from different files.

Positional: EMI (xyz data) regridding, grid sorting, geotiff with open layers.

Processing: scikit image processing, geophysical data processing.

We are still getting the hang of GitHub; so if you have any questions or comments, please leave them below or tweet/facebook/google groups us!



ArchaeoPY meetings

Welcome new ArchaeoPY members! Please find the online ArchaeoPY presentation here.  With the beginning of the new University term, ArchaeoPY will be more active, with regular meetings scheduled every Thursday, from 12:00 - 1:00 PM in the Master's computer room, Phoenix SW. For non-Bradford based members, the meetings' topics, information, and any discussions arising from the meeting, will be posted here. If there are members outside of Bradford who are interested in being involved, we can work out a way of streaming the meetings.

Exciting new changes are being implemented, with ArchaeoPY switching to an iPython notebook based server: more info, coming soon on In the mean time, follow us on Twitter, like us on Facebook, or subscribe to the ArchaeoPY Google Groups to receive notifications.


Hello Archaeopy! It has been awhile since our last post. It has been a busy past two months full of conferences and fieldwork, but these have inspired upcoming tutorials and challenges! We would appreciate some feedback regarding how ArchaeoPy is administrated. Our new plan is to release challenges monthly (with the next challenge issued next week, on the 17th... so there is still time to complete the first challenge and submit your entry for the mystery prize!) with virtual meetings being held and broadcast every fortnight. Also, what do people think of a mailing list, for the between meeting times, for any questions, comments, or ideas? We will we be sending around invitations to a google group, to those who are subscribed as users. Please let us know in the comments below, on the facebook page, or via tweet what you think of these changes!

Continue reading

Behind the Curtain: Modules, Packages, and Libraries

Following a question asked after our Geolunch session, "What is numpy?" We thought it would be useful to provide a brief overview of python's modules, packages, and libraries: what they are and how they are useful.

Since ArchaeoPy focuses on scientific applications, we often want to reuse the same functions and variables. Luckily for us, python has a great selection of modules and packages that we can use to simplify our projects; instead of having to define our own functions and variables with each project.

A module is a file that contains definitions of functions, variables, and classes that can be imported and run in other modules. A package is a directory of modules. A library is a collection of packages and modules.

Python already has a great standard library with built-in functions, constants, and types that we will regularly use. However, we will often want and need to go beyond the standard library tools, and to that end, there is a range of other powerful numeric and scientific libraries and modules that we can utilise. Below lists just few of which we frequently utilise for our scientific applications (hopefully familiar from the code in our Geolunch presentation and in our ArchaeoPy repository):

NumPy: Numpy is one of our fundamental packages because it handles and processes arrays, which are what we use to structure our geophysical data.

matplotlib: matplotlib is a plotting library. In our examples, we have used matplotlib to produce greyscales.

PyQt: We have used PyQt to create our graphical user interfaces (GUI).

Getting Started Guide

Hello! This guide will help you to get started with ArchaeoPY. This will cover installations you will need, how to utilise our repository, and how to get going running code. Stay tuned for Python Basics and Coding Basics guides! We are just in the process of putting them into a more GitHub/external-user-friendly form from our ipython notebook server.

1. Getting Started: Anaconda:

First things first, you will need Python installed on your computer. We recommend running Python 2.7 through Anaconda:

Continue reading