Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T Trilinos
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 936
    • Issues 936
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 22
    • Merge requests 22
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • James Willenbring
  • Trilinos
  • Issues
  • #4087

Closed
Open
Created Dec 19, 2018 by James Willenbring@jmwilleMaintainer0 of 3 tasks completed0/3 tasks

Xpetra: missing access routine getData for Xpetra::Vector

Created by: mayrmt

@trilinos/xpetra @lucbv

Expectations

It might be desired to have a specialized access routine getData() for the Xpetra::Vector that does not call the base class routine in Xpetra::MultiVector.

Current Behavior

To access the data in a Xpetra::Vector, one has to call the base class routine with argument getData(0) to access the data of the very first column in the multivector, although it is clear that the Xpetra::Vector only has one column.

Motivation and Context

This would emphasize the fact that the Xpetra::Vector just has one column and make it more convenient to access its data.

Definition of Done

  • add getData() and getDataNonConst() to Xpetra::Vector class
  • add documentation
  • add test

Possible Solution

The Xpetra::Vector::getData() could just call Xpetra::MultiVector::getData(0).

Additional Information

Please let me know if this idea is total nonsense or if there are reasons to not do that.

Assignee
Assign to
Time tracking