Mpwt

Latest version: v0.8.6

Safety actively analyzes 682404 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 6

0.8.0

Add:

- new option Complex Inference `--cp` (issue 75).
- function get_ptools_version to extract Pathway Tools version.
- `-dump-flat-files-biopax` option with Pathway Tools 26.0 (issue 76).
- the possibility to use already present input files (issue 79).

Fix:

- numerous issues with give_permission.
- issue in mpwt figure.
- issue if there are files in input folder (issue 80).

Modify:

- import pwt_wrapper log creation.

0.7.2

Fix:

- an issue with log creation with Pathway Tools 26.0.

0.7.1

Add:

- support for specifying reference PGDB (with taxon_id file) to be used in PathoLogic.
- warning message when there is a missing pathologic.log file during log file creation (before mpwt crahses with a python error associated with `species_pathologic_informations`).

Fix:

- an issue where mpwt does not stop if there is an error in pwt_input_files.
- input files not created if mpwt uses PGDB from ptools-local.

Modify:

- update readme.

0.7.0

This version should be compatible with Pathway Tools 25.5.

The behaviour of mpwt has been changed in this version. Before 0.7.0 mpwt will wait for all the PathoLogic processes to end before going to the next step. But if there was an error with one process, it will stop and no outputs were created even for successful processes.
Now, mpwt run the processes independently. This means that for example if you have 3 organisms (Org_A, Org_B and Org_C). If the process for Org_A fails but the processes for Org_B and Org_C succeed, then you will have an output folder containing results for Org_B and Org_C (whereas in older version no results were created).

Add:

- mpwt can take as input PathoLogic files without fasta. It will output a warning message but it should be usable. This should make mpwt compatible with PathoLogic files created by EsMeCaTa.
- new option --permission/permission to choose the permission level for PGDB in ptools-local or output folder (useful when working with a container in a cluster).
- changelog file.
- citation in readme.

Fix:

- issue with missing tmp path in run_move_pgdb.
- issue with topf (especially when using a GFF file some fields like dbxref were not correctly used).
- issue that prevents mpwt from killing Pathway Tools process that enters the Lisp Listener.
- issue with pathway prediction score not being correctly return to its previous value.
- String not Boolean and path incorrect in Readme (issue 70).
- Issue with Pathway Tools 25.5 when checking log (issue 71). The way of parsing the 'PGDB contains' line has been modified to be more robust. The parsing with str.split() has been replaced with a parsing with regex.
- numerous typos.

Modify:

- refactor mpwt code to run each process independently from the other (issue 68). Creation of the functions run_mpwt (to launch a complete run of mpwt on one organism) and independent_mpwt (to launch multiple run_mpwt on each inputs).
- refactor log creation. Instead of a function taking as input a list of dictionary (check_pwt) use 2 functions (check_mpwt_pathologic_runs and extract_pathologic). The first one takes as input a list of the paths to the input folder containing pathologic.log file and an output folder. Then it uses the second function (extract_pathologic) for each pathologic file to extraction the informations.
- replace docopt with argparse.
- update readme.
- year in license code.
- update mpwt workflow svg according to the changes in mpwt code. Put a white background (useful when using a GitHub dark theme).

0.6.3

This version should be compatible with Pathway Tools 25.0.

Fix:

- Issue with Pathway Tools 25.0 when checking log (issue 67).

0.6.2

Fix:

- Issue with encoding of flat_files_creation.log (issue 66).

Modify:

- Use setup.cfg for version.

Page 2 of 6

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.