Closed sklages closed 3 years ago
Looks like we never used or tested loading directly from a run folder. There is a bug in valid_to_load
when doing that, we are missing 'Tile' metrics.
The ZeroDivisionError
is nasty little issue unique to Python. We have not encountered it yet, so did not guard against it. This is due to one or more of your tiles have zero PF.
I can fix both bugs and put in a test case for the second one. We don't have regression tests setup around this yet, so there may be more unknown issues when loading from a run folder directly.
okay, no worries. I am happy to test :-)
pip install interop
still lists 1.1.22
.. am I too impatient? ;-)
It should have been ready, it looks like the docker image failed to download and the build failed.
This will take a little time to fix, due to recent updates to github and travis I have lost permissions to just kick off a build manually.
It should all be working now. I need to dig in and see why docker is having so many network issues.
Now it worked,
Installing collected packages: interop
Attempting uninstall: interop
Found existing installation: interop 1.1.22
Uninstalling interop-1.1.22:
Successfully uninstalled interop-1.1.22
Successfully installed interop-1.1.23
Thank you!
results in a
ZeroDivisionError
:Using
indexing()
with the run_folder path works:Result:
Can you reproduce this?
Addendum
For the latter there are some values missing:
Cluster Count PF
and% Demux
...That looks even weirder for some other runs:
Not sure what's going wrong here.