Ticket #11635 (new)

Opened 5 years ago

Last modified 5 years ago

Frames and Axis issues

Reported by: Owen Arnold Owned by: Anton Piccardo-Selg
Priority: blocker Milestone: Release 3.5
Component: Framework Keywords: vates
Cc: Blocked By:
Blocking: Tester:

Description (last modified by Anton Piccardo-Selg) (diff)

You can treat this as an umbrella ticket. The issues that have plagued paraview regarding model coordinates and axis MUST be fixed in the next version of Mantid. Minimum steps would be (not necessarily in this order) :

  1. Move to ParaView 4.4 and check that existing issues have been resolved
  2. Enable switching between non-orthogonal and orthogonal respresentations (ask owen)
  3. Ensure that cube axis can be sensibly applied and customised everywhere that we would need them
  4. We should be able to throw up 2D labels to be be locked to 3D/4D points in space.
  5. QuadView should default to have the slice increment move by 1 exactly in every dimension.

Attachments

Re__Implementation_Question__Text_in_ParaView(1).zip​ (3.6 KB) - added by Anton Piccardo-Selg 5 years ago.

Change History

comment:1 Changed 5 years ago by Owen Arnold

  • Keywords vates added

comment:2 Changed 5 years ago by Owen Arnold

  • Description modified (diff)

comment:3 Changed 5 years ago by Anton Piccardo-Selg

  • Description modified (diff)

comment:4 Changed 5 years ago by Anton Piccardo-Selg

Regarding 3:

It seems that GridAxes which are in the current master branch of ParaView provide more flexibility and options, e.g. text fonts and sizes

​http://www.kitware.com/blog/home/post/871

comment:5 Changed 5 years ago by Anton Piccardo-Selg

Regarding 4:

Utkarsh has provided us with a demonstrator how to create teh 2D text labels. It is attached to the ticket.

Changed 5 years ago by Anton Piccardo-Selg

comment:6 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​12473

Note: See TracTickets for help on using tickets.