Ticket #4471 (closed: fixed)

Opened 9 years ago

Last modified 5 years ago

Odd behaviour with SmoothNeighbours depending upon storage location

Reported by: Owen Arnold Owned by: Owen Arnold
Priority: critical Milestone: Release 2.1
Component: Mantid Keywords:
Cc: campbellsi@… Blocked By:
Blocking: Tester: Roman Tolchenov

Description

Identified in #4075.

This is probably and issue associated with the NearestNeighbours search.

Fix the underlying issue and enable usage of managed workspaces with SmoothNeighbours.

Attachments

ManagedWorkspaceIssue.py​ (786 bytes) - added by Owen Arnold 9 years ago.

Change History

comment:1 Changed 9 years ago by Owen Arnold

refs #4075. Disable managed workspaces. See #4471

Changeset: 1d70848daea66e6dbabdc03133334276dc9592ec

comment:2 Changed 9 years ago by Owen Arnold

  • Status changed from new to accepted

Changed 9 years ago by Owen Arnold

comment:3 Changed 9 years ago by Owen Arnold

Could not verify this issue on my machine. See script. Always get 'Success' as output with default tolerances set.

This was reported several weeks ago, has the cause been fixed?

comment:4 Changed 9 years ago by Owen Arnold

refs #4471. Disable managed/unmanaged checking

Changeset: 72aa4421180e3a82b31bc9304e7d28e52a08f309

comment:5 Changed 9 years ago by Owen Arnold

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

comment:6 Changed 8 years ago by Roman Tolchenov

  • Status changed from verify to verifying
  • Tester set to Roman Tolchenov

comment:7 Changed 8 years ago by Roman Tolchenov

  • Status changed from verifying to closed

Ran the script, one workspace was in memory the other was on disk. Result returned "Success!"

comment:8 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​5318

Note: See TracTickets for help on using tickets.