Closed antonkulaga closed 6 years ago
This is a duplicate of #37 and should be fixed in 1.1.14. Please reopen if you are using 1.1.14+ and still seeing the error.
@jdidion yes, probably the problem was that I used your later atropos docker container without checking that it is outdated. I've build my own container based on master, this error dissapear, now I have a new one https://github.com/jdidion/atropos/issues/48
Thanks, I'll take a look.
On Oct 7, 2017, at 9:33 AM, Anton Kulaga notifications@github.com wrote:
@jdidion yes, probably the problem was that I used your later atropos docker container without checking that it is outdated. I've build my own container based on master, this error dissapear, now I have a new one #48
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
I will also check on my side. Sometimes collaborators send us crappy data. In my case I have 22442394 in both files, so the files seem to be ok
No updates in docker hub? Still get same error
You are right, I need to push a new version to DockerHub. Will open a separate issue for that. Please test on the latest version and open a new issue if you still get the error.
Atropos crashes with "OverflowError: int too large to convert to float"
the commands that I run with latest atropos docker container were:
I can give the input files if needed but they are quite large (several gb-s)