[SOT] Split NumpyVariable for separate array/number handling #71216
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.
PR Category
Execute Infrastructure
PR Types
Bug fixes
Description
Currently, when creating
numpy.ndarraywithin the dynamic-to-static function, both SOT-based and AST-based dynamic-to-static approaches encounter segmentation faults when processing numpy ndarrays.The solution involves splitting
NumpyVariablehandling into two distinct cases:numpy.Number(already supported in SOT) andnumpy.ndarray(to be supported subsequently).When encountering operations between paddle.Tensor and numpy.ndarray, it will fall back to dynamic graph execution.
This issue currently causes identical segmentation faults in the
Co-Deformable-DETR-R50_CINNmodel ofPaddleDetection.https://github.com/PaddlePaddle/PaddleDetection/blob/59d5f5ebebc2a380f5f07dd413a056b75af01f2a/ppdet/modeling/assigners/hungarian_assigner.py#L415
This PR is under @SigureMo ’s guidance.
PCard-66972