We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Via trial and error, it seems the correct order of arguments is different from the documentation (http://projects.bigcat.unimaas.nl/pathvisiorpc/documentation/pathway-statistics/) and published examples. I resolved stack trace errors with this parameter order: #3 pgex #4 gdb dir #5 pathway dir #6 criteria #7 result dir
Confirmed order in code: https://github.com/PathVisio/PathVisioRPC/blob/master/src/org/pathvisio/xmlrpc/StatExport.java#L72
The argument order in the examples coincidentally matches that needed for getPathwayStatList() https://github.com/PathVisio/PathVisioRPC/blob/master/src/org/pathvisio/xmlrpc/PathVisio.java#L1048
This example should be included in the stats docs. It is in fact what most people probably expect to find here (like me).
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Via trial and error, it seems the correct order of arguments is different from the documentation (http://projects.bigcat.unimaas.nl/pathvisiorpc/documentation/pathway-statistics/) and published examples. I resolved stack trace errors with this parameter order:
#3 pgex
#4 gdb dir
#5 pathway dir
#6 criteria
#7 result dir
Confirmed order in code: https://github.com/PathVisio/PathVisioRPC/blob/master/src/org/pathvisio/xmlrpc/StatExport.java#L72
The argument order in the examples coincidentally matches that needed for getPathwayStatList()
https://github.com/PathVisio/PathVisioRPC/blob/master/src/org/pathvisio/xmlrpc/PathVisio.java#L1048
This example should be included in the stats docs. It is in fact what most people probably expect to find here (like me).
The text was updated successfully, but these errors were encountered: