Pathomx Linux Developer Release04.01.2015
A developer release of Pathomx (Python3) is now available. This release can be installed by using the ./developer_release_linux_python3.sh 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 ...
Pathomx v3.0.2 released26.10.2014
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.
Pathomx v3.0.0 Release Candidate 207.10.2014
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!
Pathomx v3.0.0alpha4 for Mac15.07.2014
PyQt5 support in Matplotlib27.06.2014
Pathomx v2.5.0 released30.04.2014
Below is a short snippet to implement a color-picker attached to a button in Qt. Clicking on the button pops up a dialog (native) to select a color. The color is shown by the color of the button face. A right-click option is included to allow clearing of the color ...
Pathomx (née MetaPath) v2.2.0 released07.02.2014
MetaPath is now Pathomx04.02.2014
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.
Transmit extra data with signals in PyQt13.01.2014
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.
MetaPath v2.0.0 has been released today! This latest version features a new visual editor for construction fo analysis workflows, new analysis plugins, graphing powered by Matplotlib and all sorts of other goodness. Downloads are available for Windows and MacOS X.
It’s been a while since I’ve posted an update on MetaPath development, which is finally forming into a solid package ready for publication. The latest version is available here on Github, with binary packages to follow in the near future. It’s quite a transformation from earlier versions, so I thougth I’d take some time to walk through the new features and ideas, with a few notes on implementation.