Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
OpenWalnut Core OpenWalnut Core
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 82
    • Issues 82
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • OpenWalnut
  • OpenWalnut CoreOpenWalnut Core
  • Issues
  • #186

Closed
Open
Created May 08, 2017 by Mathias Goldau@mathOwner

-RM-237-MR-WMColormapper applies old properties to new texture

How to reproduce:

  • enable debug output
  • load t1 dataset
  • apply scalarsegmentation module to t1 module
  • apply colormapper module to scalarsegementation module
  • set threshold to e.g. 10% in scalarsegementation module

you should see that the new texture has an value range from [1,1] which is invalid as actually it is [0,1]. This is due to line:

dataSet->getTexture()->getProperties()->set( m_lastDataSet->getTexture()->getProperties(), true );

in WMColormapper.cpp, short after "Replacing texture", around line 264. The problem thereby is, that the minimum, and scale properties will be copied though they might not be applicable to the new texture as the minimum might have changed. You can circumvent this, by adjusting threshold in scalarsegmentation module before applying the colormapper to it.

(from redmine: created on 2013-02-07, closed on 2013-02-08)

Assignee
Assign to
OpenWalnut 1.3.1
Milestone
OpenWalnut 1.3.1
Assign milestone
Time tracking