[LPD] [Correct] Fix mistakes in parallel-gain non-combining mode
1 unresolved thread
1 unresolved thread
Merge request reports
Activity
Filter activity
added 1 commit
- 3cf34d07 - Fix more silly mistakes in non-combining parallel gain correction
501 501 " # Replicate corrected cell and pulse IDs from high gain to other gains.\n", 502 502 " tmp_cell = np.zeros_like(in_cell)\n", 503 503 " tmp_pulse = np.zeros_like(in_pulse)\n", 504 " sel = np.zeros_like(in_cell)\n", 504 " sel = np.zeros_like(in_cell, dtype=np.bool_)\n", 505 505 "\n", 506 506 " cursor_in = cursor_out = 0\n", 507 " for afc in actual_frame_count:\n", 507 " for afc in actual_frame_counts:\n", 508 508 " for gg in range(3):\n", 509 509 " tmp_cell[cursor_out : cursor_out+afc] = in_cell[cursor_in : cursor_in+afc]\n", 510 510 " tmp_pulse[cursor_out : cursor_out+afc] = in_pulse[cursor_in : cursor_in+afc]\n", 511 511 " sel[cursor_out : cursor_out+afc] = 1\n", changed this line in version 3 of the diff
Thanks! I don't mind either type, but couldn't fully grasp the difference from the docs. What I found though:
Introduce numpy.bool as the new canonical name for NumPy’s boolean dtype, and make numpy.bool_ an alias to it. Note that until NumPy 1.24, np.bool was an alias to Python’s builtin bool. The new name helps with array API standard compatibility and is a more intuitive name.
So
np.bool_
seems to be future-proof.Edited by Philipp Schmidt
mentioned in commit 90db1d36
changed milestone to %3.15.5
Please register or sign in to reply