Open GoogleCodeExporter opened 9 years ago
I think the supplemental material was designed to be run from the 'root'
directory and not the src directory, but Cliburn would be the one to answer
that.
Original comment by Jacob.Frelinger@gmail.com
on 5 Dec 2013 at 10:14
Even if it were only looking in the root folder, it would find more files that
match *npy than it was expecting:
~/py-fcm/samples/data$ ls -1 *.npy
CD3CD45_0.000000_0_xs.npy
CD3CD45_0.015625_1_xs.npy
CD3CD45_0.031250_2_xs.npy
CD3CD45_0.062500_3_xs.npy
CD3CD45_0.125000_4_xs.npy
CD3CD45_0.250000_5_xs.npy
gate_0_1.npy
gate_3_2.npy
gate_4_2.npy
Original comment by erin.sim...@gmail.com
on 5 Dec 2013 at 10:47
Sorry about the issues - PLoS requested that we change folder names etc to
match the journal conventions at the pre-print stage, which is probably the
reason the scripts are broken.
Original comment by cliburn....@gmail.com
on 5 Dec 2013 at 10:51
Original issue reported on code.google.com by
erin.sim...@gmail.com
on 5 Dec 2013 at 6:29