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
Traceback (most recent call last):
File "/mnt/9/yuan_jianwen/tools/miniconda/envs/cellbender/lib/python3.7/multiprocessing/queues.py", line 242, in _feed
send_bytes(obj)
File "/mnt/9/yuan_jianwen/tools/miniconda/envs/cellbender/lib/python3.7/multiprocessing/connection.py", line 200, in send_bytes
self._send_bytes(m[offset:offset + size])
File "/mnt/9/yuan_jianwen/tools/miniconda/envs/cellbender/lib/python3.7/multiprocessing/connection.py", line 393, in _send_bytes
header = struct.pack("!i", n)
struct.error: 'i' format requires -2147483648 <= number <= 2147483647.
The embarrassing thing is that I used "for i in files" to run many jobs when they would get stuck because of the error. Removing " --estimator-multiple-cpu" would save the error but sacrifice speed. How can I just let it break instead of Stuck in one step?
The text was updated successfully, but these errors were encountered:
I run:
cellbender remove-background
--input $h5ad
--output pact5.h5
--projected-ambient-count-threshold 5
--checkpoint-mins 120
--learning-rate 0.0001
--training-fraction 0.9
--low-count-threshold 150
--cuda --posterior-batch-size 128 --epochs 150 --estimator-multiple-cpu.
It would get the error:
Traceback (most recent call last):
File "/mnt/9/yuan_jianwen/tools/miniconda/envs/cellbender/lib/python3.7/multiprocessing/queues.py", line 242, in _feed
send_bytes(obj)
File "/mnt/9/yuan_jianwen/tools/miniconda/envs/cellbender/lib/python3.7/multiprocessing/connection.py", line 200, in send_bytes
self._send_bytes(m[offset:offset + size])
File "/mnt/9/yuan_jianwen/tools/miniconda/envs/cellbender/lib/python3.7/multiprocessing/connection.py", line 393, in _send_bytes
header = struct.pack("!i", n)
struct.error: 'i' format requires -2147483648 <= number <= 2147483647.
The embarrassing thing is that I used "for i in files" to run many jobs when they would get stuck because of the error. Removing " --estimator-multiple-cpu" would save the error but sacrifice speed. How can I just let it break instead of Stuck in one step?
The text was updated successfully, but these errors were encountered: