Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • A ADIOS2
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 97
    • Issues 97
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 9
    • Merge requests 9
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • CI/CD
    • Code review
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Podhorszki, Norbert
  • ADIOS2
  • Issues
  • #1912
Closed
Open
Issue created Dec 21, 2019 by Podhorszki, Norbert@pnbOwner

io.AvailableAttributes()

Created by: guj

There is a test in TestNativeHDF5WriteRead.cpp EXPECT_EQ(1, io.AvailableAttributes(var4Name).size()) That I am currently removing b/c var4 only shows at ts=1 and this test is called after. browsing all time steps. Thus it thinks var4 is not a valid var.

So would like to. confirm that io.AvailableAttribtues() applies to only the current engine ts? If so this test above makes is not right. It should be 0 instead of 1.

Assignee
Assign to
Time tracking