Fix TypeError crash in multiplex_looms from pandas 3.0 string dtype - #2
Merged
Merged
Conversation
np.char.split(index, '_') raised "TypeError: string operation on non-string array" because pandas 3.0's default StringDtype (future.infer_string) makes index.astype(str) return an object-dtype ndarray rather than a real numpy unicode array. np.char functions require an actual '<U'/'S' dtype array, so force conversion with np.asarray(..., dtype=str) instead. Verified on the euler cluster by reproducing the exact failing pooling job (seed_1, pool_3.0, robust=False) directly against the pipeline's conda env: it previously crashed with this exact traceback and now completes successfully, producing all expected output files. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
np.char.split(index, '_') raised "TypeError: string operation on non-string array" because pandas 3.0's default StringDtype (future.infer_string) makes index.astype(str) return an object-dtype ndarray rather than a real numpy unicode array. np.char functions require an actual '<U'/'S' dtype array, so force conversion with np.asarray(..., dtype=str) instead.
Verified on the euler cluster by reproducing the exact failing pooling job (seed_1, pool_3.0, robust=False) directly against the pipeline's conda env: it previously crashed with this exact traceback and now completes successfully, producing all expected output files.