Ticket #5063 (assigned)

Opened 9 years ago

Last modified 5 years ago

Look into wrong instrument display using remote desktop (VPN)

Reported by: Anders Markvardsen Owned by: Anyone
Priority: minor Milestone: Backlog
Component: MantidPlot Keywords:
Cc: Blocked By:
Blocking: Tester:

Description (last modified by Anders Markvardsen) (diff)

When using remote desktop to a Windows 7 computer with the following spec:

OS Name Microsoft Windows 7 Professional Version 6.1.7601 Service Pack 1 Build 7601 Other OS Description Not Available OS Manufacturer Microsoft Corporation System Name NDW892 System Manufacturer Dell Inc. System Model OptiPlex 980 System Type x64-based PC Processor Intel(R) Core(TM) i7 CPU 870 @ 2.93GHz, 2927 Mhz, 4 Core(s), 8 Logical Processor(s) BIOS Version/Date Dell Inc. A05, 03/11/2010 SMBIOS Version 2.6 Windows Directory C:\Windows System Directory C:\Windows\system32 Boot Device \Device\HarddiskVolume2 Locale United Kingdom Hardware Abstraction Layer Version = "6.1.7601.17514" User Name CLRC\ajm64 Time Zone GMT Daylight Time Installed Physical Memory (RAM) 8.00 GB Total Physical Memory 7.99 GB Available Physical Memory 1.93 GB Total Virtual Memory 16.0 GB Available Virtual Memory 9.33 GB Page File Space 7.99 GB Page File C:\pagefile.sys

Areas of the SANS2D detectors when viewed in Mantidplot gets populated with the wrong information.

See the attached picture, which shows to the left the 'front' detector and to the right the 'rear' detector. Click on Pick tab to get information about the individual detectors. When doing this it display back that parts of the 'rear' detector, as approximately shown by the red circle in the attached picture, belongs to the 'front' detector bank where in fact it belongs to the rear detector bank.

Perhaps this is just an issue for VPN into this particular computer.

Attachments

Capture.PNG (27.1 KB) - added by Anders Markvardsen 9 years ago.

Change History

Changed 9 years ago by Anders Markvardsen

comment:1 Changed 8 years ago by Nick Draper

  • Milestone changed from Release 2.1 to Release 2.2

Moved at end of release 2.1

comment:2 Changed 8 years ago by Nick Draper

  • Status changed from new to assigned
  • Owner set to Anders Markvardsen

I think we have had problems with this before with remote usage, and I don't think we solved it then. Talk to Roman about this, to see if he has any ideas.

comment:3 Changed 8 years ago by Nick Draper

  • Milestone changed from Release 2.2 to Release 2.3

comment:4 Changed 8 years ago by Nick Draper

  • Milestone changed from Release 2.3 to Release 2.4

Moved to release 2.4

comment:5 Changed 8 years ago by Nick Draper

  • Milestone changed from Release 2.4 to Release 2.5

Moved at the code freeze for release 2.4

comment:6 Changed 7 years ago by Nick Draper

  • Milestone changed from Release 2.5 to Release 2.6

Moved to r2.6 at the end of r2.5

comment:7 Changed 7 years ago by Nick Draper

  • Status changed from assigned to new

comment:8 Changed 7 years ago by Nick Draper

  • Milestone changed from Release 2.6 to Backlog

Moved to the Backlog after the code freeze for R2.6

comment:9 Changed 7 years ago by Anders Markvardsen

  • Description modified (diff)
  • Milestone changed from Backlog to Release 3.1

comment:10 Changed 7 years ago by Anders Markvardsen

  • Summary changed from Wrong instrument display using remote desktop (VPN) to Look into wrong instrument display using remote desktop (VPN)

comment:11 Changed 7 years ago by Anders Markvardsen

  • Owner changed from Anders Markvardsen to Anyone

I have verified that on Windows the reported display problem is still present. Speaking to Roman then this is estimated to by a major work to fix.

This effect is only seen in 3D view.

For example for the sans instrument selecting side-by-side option for SANS2D and the VPN view is correct.

Pushed this ticket to anyone since it may still be a bug we would like to fix at some point in the future....

So far, to my knowledge, I am the only mantid user who have experience this problem.

comment:12 Changed 7 years ago by Nick Draper

  • Milestone changed from Release 3.1 to Backlog

Moved to backlog at the end of Release 3.1

comment:13 Changed 7 years ago by Nick Draper

  • Status changed from new to assigned

bulk move to assigned at the into of the triage step

comment:14 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue 5909

Note: See TracTickets for help on using tickets.