- MNE version: 1.0
- operating system: linux
When I trained the classifier in one dataset and tested it in another dataset, and tried to get the d values, I found that the progress bar showed the transformation of the estimator not finishing. However, the output d value had the correct shape, and the values seemed right. But I still worried that there was something wrong I didn’t notice. here is my code snippet:
data_learn_pp = data_learn[o][r][:, :, start:end]
# (188, 72, 5)
x_train = np.expand_dims(np.mean(data_learn_pp, axis=2), axis=2) # (188, 72, 1)
time_gen = GeneralizingEstimator(clf, scoring='roc_auc', n_jobs=n_jobs, verbose=True)
n_trials = epo_data_obj_roi_ds_arr_trans_per.shape
dvalues = 
for ntp in range(n_trials):
X = np.expand_dims(epo_data_obj_roi_ds_arr_trans_per[ntp, :, :], axis=0) # (1, 72, 245)
dvalue = np.squeeze(time_gen.decision_function(X)) # (245,)
# len(dvalues): 56, i.e., n_trials
dval = np.asarray(dvalues)
Here is the screenshot of the progress bar:
For each trial, the progress bar showed that only 20 time points in 245 time points had been calculated, but strangely my output
dvalue had the shape of (245,) instead of (20,).
Hello, do you also see this problem with
Thank you very much for your reply!
When I set n_jobs=1, the transforming generalizing estimator bar became shorter, here is the screenshot:
I found that the number of processed time points corresponded to the number of n_jobs I set. if I set n_jobs=1, the processed time point is 1 as I circled with red color. if I set n_jobs=20, the processed time points is 20 as I posted in the original picture.
However, the output dvalue’s shape is still correct and the value looked normal.
The number you’re referring to is simply the current number (count) of jobs that’s being processed.
It appears to me that somehow all the output in your window is kind of messed up.
But as long as the results you’re getting are correct, there’s nothing to worry about.
Although the output looked normal, I’m still confused about why the processing bar didn’t finish and the processing percentage is always stopped in the n_jobs I set / the total number of the time points, which did not make sense. In the normal case, the processing bar should stop at 100% percent, i.e., 245/245. (245 is the number of time points in an epoch after downsample).
By the way, what do you mean by the output in my window is messed up, I don’t get it
It appears the progress bars don’t display correctly, and content appears in lines where it shouldn’t. Everything is a bit out of order.