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
  • #1585

Closed
Open
Created Aug 07, 2017 by James Willenbring@jmwilleMaintainer

ROL: Explicitly uses GlobalOrdinal=int with Tpetra, doesn't need to

Created by: mhoemmen

@trilinos/rol Line 292 of rol/example/PDE-OPT/TOOLS/assembler.hpp (in Trilinos develop) explicitly calls Tpetra::createOneToOne<int,int>. This forces use of GlobalOrdinal = int. See #74 (closed) for why we don't want this.

The line is easy to fix: just do this:

myUniqueStateMap_ = Tpetra::createOneToOne (myOverlapStateMap_);

That is, let createOneToOne deduce its template parameters on its own. It can do so by looking at the input argument.

There are a few other places in the file that force this constraint, e.g., line 231:

Teuchos::Array<int> myGlobalIds;

(replace int with GO and define GO as Tpetra::Map<>::global_ordinal_type).

Assignee
Assign to
Time tracking