Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[cmd] error in Kp-finder command #48

Closed
Bioswinger opened this issue Nov 4, 2020 · 3 comments
Closed

[cmd] error in Kp-finder command #48

Bioswinger opened this issue Nov 4, 2020 · 3 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@Bioswinger
Copy link

Bioswinger commented Nov 4, 2020

Quickstart guide notebook

command used: pyntacle keyplayer kp-finder -i AdvSeek.adjm -k 2 -m 1 -t mreach

error: the program return an empty .tsv file

There is the same problem also using the brute-force option

@mazzalab mazzalab self-assigned this Nov 10, 2020
@mazzalab
Copy link
Owner

do you receive an error message? Can you report it here?
Can you open another issue about the brute-force error, reporting the error message also for this?

@mazzalab mazzalab added the bug Something isn't working label Nov 10, 2020
@mazzalab mazzalab added this to the 1.3 release milestone Nov 10, 2020
@Bioswinger
Copy link
Author

it seems there aren't errors. The files are corretly imported and both the plot and the tsv file are generated.

my output:

Using greedy optimization algorithm for searching the optimal key player set for the requested key player metrics
Node set size for key-player search: 3
Writing report in txt format
Plotting network and run results in /mypath directory with PyntacleInk

@mazzalab
Copy link
Owner

there is actually a bug. You specify mreach in the command line but it matches m-reach inside the code. This cause to leave the last half of the report file empty.

@mazzalab mazzalab reopened this Nov 10, 2020
@mazzalab mazzalab mentioned this issue Nov 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants