[Edit] Python (Pytorch): .cat() #6485
Open
Conversation
This file contains 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
mamtawardhani
added
enhancement
|
|
||
| <details> | ||
| <summary>2. Can I concatenate tensors of different data types or devices?</summary> | ||
| <p>No. All tensors must have the same data type and must be on the same device (e.g., all on CPU or all on GPU). Mismatches will raise an error. |
There was a problem hiding this comment.
Can add backlink to CPU and GPU
There was a problem hiding this comment.
We don't have one for GPU, added 1cpu blog link (It has better content than docs)
|
|
||
| A new tensor resulting from concatenating the input tensors along the specified dimension. | ||
|
|
||
| ## Example 1: Concatenating tensors along the first dimension |
There was a problem hiding this comment.
This line -"The output shows the two tensors and the concatenated tensor along the first dimension:" is repetitive in all three examples. Consider rewriting it. We are saying the same thing in the example heading, then description of example and output description.
Radhika-okhade
added
status: review 1️⃣ completed
status: waiting for author
and removed
status: under review
| @@ -115,9 +115,9 @@ tensor([[ 1, 2, 3, 7, 8, 9], | |||
| [ 4, 5, 6, 10, 11, 12]]) | |||
| ``` | |||
|
|
|||
| ## Example 3: Concatenating tensors along the third dimension | |||
| ## Example 3: Appending Tensors on the Depth Dimension | |||
There was a problem hiding this comment.
I prefer the earlier name
|
|
||
| The example below showcases concatenating tensors along the third dimension using the `.cat()` function: | ||
| This example illustrates how to append tensors along the third dimension (axis 2), effectively stacking them in depth using the `.cat()` method: |
There was a problem hiding this comment.
Suggested change
| This example illustrates how to append tensors along the third dimension (axis 2), effectively stacking them in depth using the `.cat()` method: | |
| This example shows how to append tensors along the third dimension (axis 2), effectively stacking them in depth using the `.cat()` method: |
| @@ -75,9 +75,9 @@ tensor([[ 1, 2, 3], | |||
| [10, 11, 12]]) | |||
| ``` | |||
|
|
|||
| ## Example 2: Concatenating tensors along the second dimension | |||
| ## Example 2: Stacking Tensors Across the Second Axis | |||
There was a problem hiding this comment.
I prefer the earlier name
| @@ -33,9 +33,9 @@ torch.cat(tensors, dim=0, out=None) | |||
|
|
|||
| A new tensor resulting from concatenating the input tensors along the specified dimension. | |||
|
|
|||
| ## Example 1: Concatenating tensors along the first dimension | |||
| ## Example 1: Merging Tensors Along Dimension 0 | |||
There was a problem hiding this comment.
I prefer the earlier name
Co-authored-by: Radhika-okhade <[email protected]>
Co-authored-by: Radhika-okhade <[email protected]>
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.
Description
[[Edit] Python (Pytorch): .cat()
Issue Solved
Closes #6472
Type of Change
Checklist
mainbranch.Issues Solvedsection.