Pathomx Linux Developer Release

A developer release of Pathomx (Python3) is now available. This release can be installed by using the ./ script from the cloned Github repository. This script installs all dependencies (via apt-get and pip) that are required for Pathomx to run. This developer release is an important first step to ... Continue reading



PyQtConfig: a simple API for handling, persisting and synchronising configuration within PyQt applications. This module was built initially as part of the Pathomx data analysis platform but spun out into a standalone module when it became clear it was quite useful. Continue reading

Pathomx v3.0.2 released

Pathomx v3.0.2 has been released for both Windows and MacOS X. This marks the first stable, bug-fixed release for the v3.0 line featuring the new IPython-kernel with cluster support for parallel processing of tools. Continue reading

Pathomx v3.0.0 Release Candidate 2

The final release candidate for Pathomx v3.0.0 is available for both Mac and Windows. This latest version features the new IPython backend providing parallel processing (via IPython ipcluster support), numerous bugfixes and improvements to the UI and figure outputs. While a development version it is considered stable enough for regular use. If you’re a current user of Pathomx, please download and test with your own hardware and data, see how it holds up and then report any problems! Continue reading

MetaPath is now Pathomx

MetaPath has now been renamed Pathomx. The name change was neccessary due to a name clash with another piece of published bioinformatics software, but it also better reflects the focus on analysis of multi-omics data in a pathway context. Continue reading

Transmit extra data with signals in PyQt  gui

Signals are a neat feature of Qt that allow message-passing between different areas of your program. To use a signal you attach a function to be called in the event of the signal firing, usually accepting a small item of data about the signal state. However, there is a limitation: the signal can only emit the data it was designed to do. So for example, a QAction has a .triggered that fires when that particular action has been activated. Unfortunately the receiving connected function only receives one thing: checked=True or False. In other words, the receiving function has no way of knowing which action triggered it. This is usually fine. You can tie a particular action to a particular function. However, sometimes you want to trigger multiple actions off the same type of action, and treat them differently. Here’s a neat trick to do just that. Continue reading

cx_Freeze and PySide on Mac  gui

I’d had success using py2app for building Mac binaries for distribution but wanted to give cx_Freeze a go since it’s cross platform - allowing builds for Windows, Linux, and more. Unfortunately, attempting to build using cx_Freeze was resulting in errors: libpyside-python2.7.1.1.dylib: No such file or ... Continue reading