Ticket #1713 (closed: fixed)

Opened 10 years ago

Last modified 5 years ago

In Python workspace algebra doesn't log or write to workspace history

Reported by: Steve Williams Owned by: Martyn Gigg
Priority: minor Milestone: Iteration 26
Component: Python Keywords:
Cc: Blocked By:
Blocking: Tester: Michael Whitty

Description

Nick suggested to me that workspace algebra in C++ should behave like a sub-algorithm calls. However when called from Python there should be logging and history.

To test, run this Python w = LoadRaw("MAR11001.raw", "d")[0] a = w+w

the resulting workspace d_p_d has no history and only the first operation wrote to the log

Change History

comment:1 Changed 10 years ago by Martyn Gigg

  • Status changed from new to accepted

comment:2 Changed 10 years ago by Martyn Gigg

(In [7915]) Polised up the binary operators in Python so that they are now all controlled from the same place. Also killed another ticket by ensuring that when the binary op algorithms are run that they are run as top-level algorithms so that they log their behaviour. Re #2025 Re #1713

comment:3 Changed 10 years ago by Martyn Gigg

There is one outstanding issue that as been span out into a separate ticket concerning the deletion of temporary workspaces when running a script generated from the workspace history. When doing an operation with a double a temporary workspace is necessary but deleting this isn't logged so in the history generated version it stays around. Ticket #2030

comment:4 Changed 10 years ago by Martyn Gigg

  • Status changed from accepted to verify
  • Resolution set to fixed
  • Milestone changed from Unassigned to Iteration 26

comment:5 Changed 10 years ago by Michael Whitty

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

comment:6 Changed 10 years ago by Michael Whitty

  • Status changed from verifying to closed

the operations are written to the workspace history as described.

comment:7 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue 2560

Note: See TracTickets for help on using tickets.