Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
ParaView
ParaView
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 2,003
    • Issues 2,003
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 57
    • Merge Requests 57
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • ParaView
  • ParaViewParaView
  • Issues
  • #14312

Closed
Open
Opened Sep 30, 2013 by Kitware Robot@kwrobot
  • Report abuse
  • New issue
Report abuse New issue

multicore ux

This issue was created automatically from an original Mantis Issue. Further discussion may take place here.


Improve user experience by making multicore easier. one idea is to make startup with the multicore option more like the normal "connect to server" process giving the user a pvsc like dialog to change the number of cores.

another idea is adding a command line option to control the number of cores. This might be able to leverage the existing client mpi initialization option, switching to multicore when more than 1 core is requested.

this was discussed on the mail list http://public.kitware.com/pipermail/paraview-developers/2013-October/002500.html

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: paraview/paraview#14312