You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running computation, the process uses extremely high amounts of memory and is much slower compared to the computation with restricted domain values [-1.0, -0.5, 0.0, 0.5, 1.0]. The more items are included in the data, the slower and memory eager it becomes. I tested it on two systems for about 2,400 data points in total:
MacOS with python=3.9.6, numpy=1.26.4, and krippendorff=0.6.0
=> The computation needs more than 60 secs time and consumes 32GB of memory, but finishes.
Ubuntu Linux with python=3.10.12, numpy=1.26.4, and krippendorff=0.6.0.
=> The computation takes too long (I had to kill the process due to memory issues) and consumes some hundreds of GB within seconds. (Unfortunately, in one unsupervised case it even led to a complete depletion of RAM and OS killed important processes...)
I am running Krippendorff's alpha with level_of_measurement=interval for arbitrary data and without restricted domain values. This means, there are:
When running computation, the process uses extremely high amounts of memory and is much slower compared to the computation with restricted domain values [-1.0, -0.5, 0.0, 0.5, 1.0]. The more items are included in the data, the slower and memory eager it becomes. I tested it on two systems for about 2,400 data points in total:
=> The computation needs more than 60 secs time and consumes 32GB of memory, but finishes.
=> The computation takes too long (I had to kill the process due to memory issues) and consumes some hundreds of GB within seconds. (Unfortunately, in one unsupervised case it even led to a complete depletion of RAM and OS killed important processes...)
The process appears to go crazy at the line 117
preds.csv
targets.csv
I am not sure whether this problem is related to this numpy bug report:
numpy/numpy#26395
The text was updated successfully, but these errors were encountered: