fix: verify if CI breaks due to ProcessPool

Author: cdpaiva

snazzy_processing/snazzy_processing/pipeline.py

@@ -1,4 +1,4 @@
-from concurrent.futures import ProcessPoolExecutor, as_completed
+from concurrent.futures import ThreadPoolExecutor, as_completed
 from datetime import datetime
 import shutil
 
@@ -27,7 +27,7 @@ def measure_vnc_length(embs_src, res_dir, downsampling, threshold_method="multio
     lengths = []
     ids = []
 
-    with ProcessPoolExecutor() as executor:
+    with ThreadPoolExecutor() as executor:
         futures = [
             executor.submit(calculate_length, emb, downsampling, threshold_method)
             for emb in embs
@@ -109,7 +109,7 @@ def calc_activities(embs_src, res_dir, window):
     # NOTE: number of workers is limited here because it was crashing jupyter
     # on a machine with low RAM. More workers will result in faster processing
     # but also more RAM usage
-    with ProcessPoolExecutor(max_workers=4) as executor:
+    with ThreadPoolExecutor(max_workers=4) as executor:
         futures = [
             executor.submit(calc_activity, act, stct, window)
             for act, stct in zip(active, struct)

snazzy_processing/snazzy_processing/vnc_length.py

@@ -50,6 +50,7 @@ def get_length_from_csv(file_path, columns=(1,)):
 
 
 def get_output_data(length_data, downsampling, frame_interval):
+    length_data = np.array(length_data)
     t = length_data.size
     time = np.arange(t) * frame_interval * downsampling