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

Unexpected behavior in the DIPY workflow script #1488

Closed
parichit opened this Issue Mar 27, 2018 · 2 comments

Comments

Projects
None yet
1 participant
@parichit
Contributor

parichit commented Mar 27, 2018

Description

The workflow script that extends the base workflow class does not behave as expected always.

The following URL contains the commit of a small test script for DIPY workflows. This script simply checks if the file provided by the user exists in the system or not? However, if the file does not exist then it reports a message (under the else block).

When the script is run with a valid file path then the output is as expected and it reports the file to be existing. But, when an invalid file path is given then instead of executing the code under the else block it just throws an error-trace. The error trace is expected below:

Way to reproduce

Note that there is no file named '1' in my system so it should execute the code under the else block.

python check_scratch() /Users/schmuck/Documents/1

Traceback (most recent call last):
File "check_scratch.py", line 53, in
run_flow(CheckScratch())
File "/Users/schmuck/Documents/dipy/dipy/workflows/flow_runner.py", line 82, in run_flow
return flow.run(**args)
File "check_scratch.py", line 44, in run
for fpath in io_it:
File "/Users/schmuck/Documents/dipy/dipy/workflows/multi_io.py", line 253, in iter
IO = np.concatenate([I, O], axis=1)
ValueError: all the input arrays must have same number of dimensions

@parichit

This comment has been minimized.

Contributor

parichit commented Mar 27, 2018

This is the commit URL to see the script

parichit@15cb39d

@parichit

This comment has been minimized.

Contributor

parichit commented Mar 28, 2018

Closing the issue to re-try after fixing the PEP8 formatting style in the code.
@skoudoro : Thanks for the pointers.

@parichit parichit closed this Mar 28, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment