Starting from the octave_version, I created that branch, with the docker mechanism.
I have octave 4.2.2 on my machine, so that I used docker to run your code under octave 5.2.0.
I updated the README file to indicate how to create and use the docker image, which should work from linux machine.
I could then launch your program using the command indicated in the README file, which is like launching the command ./run_pepato left BLF ./test_data ./output, but within the docker image.
An output file is generated, but the resulting output file differs from the one stored in test_data.
More surprisingly, the results is not constant from a call to another. If I call twice the program, the output file obtained is not the same. Are you experiencing the same from your environment?
Once we understand why the output is not constant, and if the output is validated by you, we could then proceed on the merge process. I propose to merge docker branch into octave_version, but this is not clear to me if this should be brought to the dev or master branch.
We would then have to continue the adjustment of the input - output structure. To be compatible with the general scheme, we expect to provide as input the name of each input file, and not the directory containing each file. Also we expect having each pi score stored in separate file, not into a single one. But we can have a look at this later on.
Starting from the
octave_version, I created that branch, with the docker mechanism. I have octave 4.2.2 on my machine, so that I used docker to run your code under octave 5.2.0.I updated the README file to indicate how to create and use the docker image, which should work from linux machine.
I could then launch your program using the command indicated in the README file, which is like launching the command
./run_pepato left BLF ./test_data ./output, but within the docker image.An output file is generated, but the resulting output file differs from the one stored in
test_data. More surprisingly, the results is not constant from a call to another. If I call twice the program, the output file obtained is not the same. Are you experiencing the same from your environment?I attach the latest output file I got. subject_0005_run_001_output.log
Once we understand why the output is not constant, and if the output is validated by you, we could then proceed on the merge process. I propose to merge docker branch into octave_version, but this is not clear to me if this should be brought to the dev or master branch.
We would then have to continue the adjustment of the input - output structure. To be compatible with the general scheme, we expect to provide as input the name of each input file, and not the directory containing each file. Also we expect having each pi score stored in separate file, not into a single one. But we can have a look at this later on.