Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[lang] Fix the element_type of the AnyArray #8192

Merged
merged 5 commits into from
Jun 19, 2023

Conversation

lin-hitonami
Copy link
Contributor

@lin-hitonami lin-hitonami commented Jun 15, 2023

🤖 Generated by Copilot at d183bb1

Summary

🐛🧮🚀

Fix a bug in AnyArray.get_type that caused incorrect type inference for external arrays. Add a new function get_external_tensor_element_type to the Python export module to support the bug fix.

get_type had bug
wrong function for array
fixed in autumn wind

Walkthrough

  • Fix a bug in the get_type method of the AnyArray class that caused incorrect type inference and compilation errors for external arrays (link)
  • Add the get_external_tensor_element_type function to the Python export module to expose the C++ function that returns the element type of an external array (link)

Stack from ghstack (oldest at bottom):

<!--
copilot:all
-->
### <samp>🤖 Generated by Copilot at 0176872</samp>

### Summary
📝🔬🆕

<!--
1.  📝 - This emoji can represent the change of modifying the `decl_ndarray_arg` function to pass the `element_type` to the `AnyArray` constructor, since this is a code change that involves writing or editing some code.
2.  🔬 - This emoji can represent the change of adding `element_type` argument to `AnyArray` constructor and using it in `get_type` and `grad` methods, since this is a code change that involves improving the type handling and gradient computation of arbitrary arrays, which are related to scientific or mathematical operations.
3.  🆕 - This emoji can represent the change of introducing a new argument to the `AnyArray` constructor, since this is a code change that involves adding a new feature or functionality to the existing code.
-->
Improved type handling and gradient computation of `AnyArray` arguments in Taichi kernels and functions. Added `element_type` parameter to `AnyArray` constructor and `decl_ndarray_arg` function.

> _To declare an array argument_
> _We pass the element type along_
> _This helps `AnyArray`_
> _To know what to say_
> _When it calls `get_type` or `grad`_

### Walkthrough
*  Add `element_type` argument to `AnyArray` constructor and store it as an attribute ([link](https://github.com/taichi-dev/taichi/pull/8192/files?diff=unified&w=0#diff-2e623ee0b0eec1b200fead36c0627a3c54738f6d83d79757398dc67decc01da8L18-R20), [link](https://github.com/taichi-dev/taichi/pull/8192/files?diff=unified&w=0#diff-575efc738df7b1202370c2531ec82232dc7f287b2bec4999af03ef40da4f5deeL111-R111))
*  Return stored `element_type` in `AnyArray.get_type` method instead of inferring from pointer ([link](https://github.com/taichi-dev/taichi/pull/8192/files?diff=unified&w=0#diff-2e623ee0b0eec1b200fead36c0627a3c54738f6d83d79757398dc67decc01da8L36-R37))
*  Pass stored `element_type` to `AnyArray` constructor in `AnyArray.grad` method to preserve type information in gradient array ([link](https://github.com/taichi-dev/taichi/pull/8192/files?diff=unified&w=0#diff-2e623ee0b0eec1b200fead36c0627a3c54738f6d83d79757398dc67decc01da8L43-R44))






[ghstack-poisoned]
@lin-hitonami lin-hitonami requested a review from ailzhang June 16, 2023 07:34
<!--
copilot:all
-->
### <samp>🤖 Generated by Copilot at 0176872</samp>

### Summary
📝🔬🆕

<!--
1.  📝 - This emoji can represent the change of modifying the `decl_ndarray_arg` function to pass the `element_type` to the `AnyArray` constructor, since this is a code change that involves writing or editing some code.
2.  🔬 - This emoji can represent the change of adding `element_type` argument to `AnyArray` constructor and using it in `get_type` and `grad` methods, since this is a code change that involves improving the type handling and gradient computation of arbitrary arrays, which are related to scientific or mathematical operations.
3.  🆕 - This emoji can represent the change of introducing a new argument to the `AnyArray` constructor, since this is a code change that involves adding a new feature or functionality to the existing code.
-->
Improved type handling and gradient computation of `AnyArray` arguments in Taichi kernels and functions. Added `element_type` parameter to `AnyArray` constructor and `decl_ndarray_arg` function.

> _To declare an array argument_
> _We pass the element type along_
> _This helps `AnyArray`_
> _To know what to say_
> _When it calls `get_type` or `grad`_

### Walkthrough
*  Add `element_type` argument to `AnyArray` constructor and store it as an attribute ([link](https://github.com/taichi-dev/taichi/pull/8192/files?diff=unified&w=0#diff-2e623ee0b0eec1b200fead36c0627a3c54738f6d83d79757398dc67decc01da8L18-R20), [link](https://github.com/taichi-dev/taichi/pull/8192/files?diff=unified&w=0#diff-575efc738df7b1202370c2531ec82232dc7f287b2bec4999af03ef40da4f5deeL111-R111))
*  Return stored `element_type` in `AnyArray.get_type` method instead of inferring from pointer ([link](https://github.com/taichi-dev/taichi/pull/8192/files?diff=unified&w=0#diff-2e623ee0b0eec1b200fead36c0627a3c54738f6d83d79757398dc67decc01da8L36-R37))
*  Pass stored `element_type` to `AnyArray` constructor in `AnyArray.grad` method to preserve type information in gradient array ([link](https://github.com/taichi-dev/taichi/pull/8192/files?diff=unified&w=0#diff-2e623ee0b0eec1b200fead36c0627a3c54738f6d83d79757398dc67decc01da8L43-R44))






[ghstack-poisoned]
@lin-hitonami lin-hitonami changed the title [lang] Record the element_type of the AnyArray [lang] Fix the element_type of the AnyArray Jun 16, 2023
@taichi-gardener taichi-gardener merged commit d183bb1 into gh/lin-hitonami/11/base Jun 19, 2023
taichi-gardener pushed a commit that referenced this pull request Jun 19, 2023
ghstack-source-id: 938770dea60ac879c40fe25d4f67a50b44b03234
Pull Request resolved: #8192
@taichi-gardener taichi-gardener deleted the gh/lin-hitonami/11/head branch June 19, 2023 01:25
L2ncE pushed a commit to L2ncE/taichi that referenced this pull request Jun 20, 2023
ghstack-source-id: 938770dea60ac879c40fe25d4f67a50b44b03234
Pull Request resolved: taichi-dev#8192
PGZXB pushed a commit to PGZXB/taichi that referenced this pull request Jul 13, 2023
ghstack-source-id: 938770dea60ac879c40fe25d4f67a50b44b03234
Pull Request resolved: taichi-dev#8192
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants