Ticket #2030 (closed: wontfix)

Opened 10 years ago

Last modified 5 years ago

Python Binary Operations don't delete temp workspaces from history script

Reported by: Martyn Gigg Owned by: Martyn Gigg
Priority: trivial Milestone: Release 2.3
Component: Mantid Keywords:
Cc: Blocked By:
Blocking: Tester: Vickie Lynch

Description

When doing an operation with a double a temporary workspace is necessary. This is taken care of when using the standard operators but when a script is produced from the workspace history it is missing the delete because it's not logged.

This needs fixing in some manner, whether logging deletes or just creating a simple DeleteWorkspace algorithm

Change History

comment:1 Changed 10 years ago by Nick Draper

  • Priority changed from major to trivial

This only occurs infrequently and will only use a very small quantity of memory (and the user can see and delete the WS anyway).

Therefore priority decreased.

comment:2 Changed 10 years ago by Nick Draper

  • Milestone changed from Iteration 26 to Iteration 27

Bulk move of tickets to iteration 27, if your ticket is essential for Iteration 26 then move it back.

comment:3 Changed 10 years ago by Nick Draper

  • Owner set to Martyn Gigg
  • Status changed from new to assigned

I think a deleteworkspace algroithm is the best option.

comment:4 Changed 10 years ago by Martyn Gigg

  • Status changed from assigned to accepted

comment:5 Changed 10 years ago by Martyn Gigg

(In [8895]) Added a simple DeleteWorkspace algorithm and corrected a minor argument problem in WorkspaceCreationHelper. Having Rename and DeleteWorkspace will provide more consistency in scripts when performing these operations. Refs #2030

comment:6 Changed 10 years ago by Nick Draper

  • Milestone changed from Iteration 27 to Iteration 28

Bulk move of tickets at the end of iteration 27

comment:7 Changed 9 years ago by Nick Draper

  • Milestone changed from Iteration 28 to Iteration 29

Bulk move of tickets at the end of iteration 28

comment:8 Changed 9 years ago by Nick Draper

  • Milestone changed from Iteration 29 to Iteration 30

Accepted and assigned tickets moved at iteration 29 code freeze

comment:9 Changed 9 years ago by Nick Draper

  • Milestone changed from Iteration 30 to Iteration 31

Bulk move of tickets to iteration 31 at the iteration 30 code freeze

comment:10 Changed 9 years ago by Nick Draper

  • Milestone changed from Iteration 32 to Iteration 33

Moved to iteration 33 at iteration 32 code freeze

comment:11 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:12 Changed 8 years ago by Nick Draper

  • Milestone changed from Release 2.2 to Release 2.3

http://www.mantidproject.org/Release_Notes_2_2_Full_List

comment:13 Changed 8 years ago by Martyn Gigg

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

This has been open for quite some time and was not even spotted by a user but by us. I think we may just have to accept this is a limitation of the mechanism.

comment:14 Changed 8 years ago by Vickie Lynch

  • Status changed from verify to verifying
  • Tester set to Vickie Lynch

comment:15 Changed 8 years ago by Vickie Lynch

  • Status changed from verifying to closed

Minor problem that will not be fixed

comment:16 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​2877

Note: See TracTickets for help on using tickets.