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

Transposed array is not equal to its explicit equivalent #699

Open
stxue1 opened this issue Jul 2, 2024 · 0 comments
Open

Transposed array is not equal to its explicit equivalent #699

stxue1 opened this issue Jul 2, 2024 · 0 comments
Labels
bug Something isn't working interop Bears on spec compatibility

Comments

@stxue1
Copy link

stxue1 commented Jul 2, 2024

When transpose is called on an array, it is not considered equal to its explicitly typed counterpart:

version 1.1

workflow wf {
  input {}
  Array[Array[Int]] a = [[1,2,3]]
  output {
    Array[Array[Int]] a_transposed = transpose(a)
    Array[Array[Int]] a_expected = [[1],[2],[3]]
    Boolean equal = a_transposed == a_expected
  }
}
{
  "dir": "/home/heaucques/Documents/wdl-conformance-tests/20240702_105206_wf",
  "outputs": {
    "wf.a_expected": [
      [
        1
      ],
      [
        2
      ],
      [
        3
      ]
    ],
    "wf.a_transposed": [
      [
        1
      ],
      [
        2
      ],
      [
        3
      ]
    ],
    "wf.equal": false
  }
}

The WDL 1.1 spec has a good example of this case as well implemented as part of their unit tests

@stxue1 stxue1 changed the title Transpose is not equal to its explicit equivalent Transposed array is not equal to its explicit equivalent Jul 2, 2024
@mlin mlin added bug Something isn't working interop Bears on spec compatibility labels Jul 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working interop Bears on spec compatibility
Projects
Status: Backlog
Development

No branches or pull requests

2 participants