Ticket #2513 (closed: fixed)

Opened 10 years ago

Last modified 5 years ago

Provide Time Information

Reported by: Owen Arnold Owned by: Owen Arnold
Priority: major Milestone: Iteration 28
Component: VATES Keywords:
Cc: Blocked By:
Blocking: Tester: Michael Reuter

Description

Use the mapping time dimension in the MDWorkspace to provide the actual numerical range for times in VisIT. We lack the ability to deal with Units at the moment this will need to be fixed later.

Change History

comment:1 Changed 10 years ago by Owen Arnold

  • Status changed from new to accepted

comment:2 Changed 10 years ago by Owen Arnold

(In [9591]) re #2513

comment:3 Changed 10 years ago by Owen Arnold

  • Status changed from accepted to verify
  • Resolution set to fixed

comment:4 Changed 9 years ago by Michael Reuter

  • Status changed from verify to assigned
  • Owner changed from Owen Arnold to Michael Reuter

comment:5 Changed 9 years ago by Michael Reuter

  • Owner changed from Michael Reuter to Owen Arnold

comment:6 Changed 9 years ago by Owen Arnold

  • Status changed from assigned to accepted

comment:7 Changed 9 years ago by Owen Arnold

  • Status changed from accepted to verify

comment:8 Changed 9 years ago by Owen Arnold

When the MDWorkspace is first loaded (select a .sqw file) the time range should automatically set itself to the energy range.

comment:9 Changed 9 years ago by Michael Reuter

  • Status changed from verify to verifying
  • Tester set to Michael Reuter

comment:10 Changed 9 years ago by Michael Reuter

  • Status changed from verifying to closed

I have verified this behavior while doing the work for the GUI mockup.

comment:11 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​3360

Note: See TracTickets for help on using tickets.