There are several advantages in using Anaconda to
install not only Pyntacle, but also Python and other packages: it is
cross platform (Linux, MacOS X, Windows), you do not require
administrative rights to install it (it goes in the user home
directory), it allows you to work in virtual environments, which can be
used as safe sandbox-like sub-systems that can be created, used,
exported or deleted at your will.
You can choose between the full Anaconda and its lite version,
Miniconda. The difference between the two is that Anaconda comes with
hundreds of packages and can be a bit heavier to install, while
Miniconda allows you to create a minimal, self-contained Python
installation, and then use the Conda command to install additional
packages of your choice.
In any case, Conda is the package manager that the Anaconda and
Miniconda distributions are built upon. It is both cross-platform and
language agnostic (it can play a similar role to a pip and virtualenv
combination), and you need to set it up by running either the Anaconda
installer or the
Miniconda installer, choosing the
Python 3.7 version.
The next step is to create a new Conda environment (if you are familiar
with virtual environments, this is analogous to a virtualenv).
Warning: Windows users could experience some issues when installing Conda or Miniconda in folders that
whose name contains whitespaces (e.g. "%userprofile%\John Doe\Miniconda"). This is a known bug,
as reported here and
here. If this occurs,
we recommend to create a new directory with no whitespaces (e.g. "%userprofile%\John_Doe\) and install Conda in there.
Open a windows prompt or (even better) an
Anaconda prompt
, and type:
Independently of the OS in use, if you need CUDA support, you must
also install the CUDA toolkit by downloading and installing the Toolkit from the
NVIDIA website.
NOTE GPU-base processing is an experimental feature in the current version (1.3), and is not covered by the command-line interface. This is because of weird behaviors of Numba with some hardware configurations that we were not be able to describe and circumvent so far. Although currently accessible by APIs, the GPU feature will be stable in the release 2.0, when Pyntacle will have covered the possibility to manage huge matrices for which replacing fine-grained parallelism with GPU computing would make sense.
[command-line] The algorithm that decides the computing configuration to be used to analyze a give graph was updated to exclude the possibility to run multi-process and multi-threaded at the same time. This is still possible by accessing directly to the APIs.
[command-line] Renamed option from -T/--threads to -O/--nprocs to avoid clashes with other synonymous options
[API] Removed all decorator methods that over-checked the sanity of the arguments of methods. These resulted to improve.
[PyntacleInk] bug #28 "initial value" and "value" are swapped, solved
[Tests] bug #25 "gr-finder bruteforce test fails", solved
Minor:
[command-line] bug #23 "the command line option --type m-reach in kp-finder produces no output", solved
[API] removed the max_distance argument from all methods
[API] removed the seed from each methods. Postponed to later versions the implementation of clever manner of controlling randomness of number generators
the default number of forked processes is now 1 and not equals to the total number of available processors -1
PyntacleInk is a web-based, javascript-based visualizer based on the sigmajs library. It is
designed to integrate with Pyntacle command-line library and replaces the igraph-based plotter.
Graphical plots will be now be produced in a html file within the pyntacle results directory, containing detailed
summarization of each Pyntacle run performed on the input file. This file is updated at each run, making graphical
expolration of results more intuitive.
New major feature: Group centralities. A redesign of single-node centralities that accounts for the centrality of groups have been added to Pyntacle and a new command, groupcentrality has now been added to the Pyntacle command line. Its behavior is similar to the keyplayer command. Users can compute group centrality indices for predetermined sets of nodes or perform group centrality-based searches for sets of nodes that optimize predetermined group centrality scores
Octopus redesign
All graphs imported from either the command line or through the io_stream methods now have the same id-->node name pairing, with the exceptions of pickled igraphs (binary)
Node isolates are now removed from graphs when imported through any Pyntacle import istance
GPU-based computation of the shortest paths using the Floyd-Warshall algorithm is now an experimental feature and is disabvled in the Pyntacle command line. Users can choose to override this behavior in the Pyntacle library by using the correct Cmode enumerator
Added exceptions and specific behaviors to unusual group-based search calculations that caused exceptions before