Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add common commands to matrix workspaces in Python #3498

Closed
NickDraper opened this issue Mar 16, 2011 · 2 comments
Closed

Add common commands to matrix workspaces in Python #3498

NickDraper opened this issue Mar 16, 2011 · 2 comments
Assignees
Labels
Framework Issues and pull requests related to components in the Framework High Priority An issue or pull request that if not addressed is severe enough to postponse a release.

Comments

@NickDraper
Copy link
Contributor

This issue was originally TRAC 2651

This could be implemented in:

  1. PythonAPI\src\workspaceproxies.cpp
  2. PythonAPI\MantidFramework.py

I suppose implementing it in C++ and exposing it is the best way.

The following options are uncontraversial (although only work on matrix workspaces):

  1. Clone
  2. Transpose
  3. Rebin (possibly also RebinToWorkspace, rebunch and regroup)
  4. ConvertUnits
  5. Crop
  6. Save (SaveNexus)
  7. Rename

These might be worth while:

  1. Mask.Extract (ExtractMasking)
  2. Mask.ApplyWS (Maskdetectors using a MaskedWorkspace)
  3. Mask.Apply (Maskdetectors specified detectors or spectra)
  4. Mask.ApplyBins (Maskbins)
  5. Integrate
  6. Sum (SumSpectra)
  7. Merge (MergeRuns)
  8. ReplaceSpeacialValues
  9. SolidAngle
  10. Scale

These I'm not too sure about:

  1. Load (Overwriting existing data, not the best way)
  2. Delete (it would be deleting itself and therefore rensering it's own handle invalid)

These would only work within Mantidplot (Martyn set's a magic flag):

  1. Display (shows the matrix)
  2. Plot (1D or colour map depending on dimensionality)
  3. DisplayInstrument
    We could make plot work standalone if MatplotLib was available.

The names I have suggested are just suggestions, have a think about the overall user experience.

@NickDraper
Copy link
Contributor Author

@NickDraper (2011-04-27T07:35:26):
Bulk move of tickets at the end of iteration 28


@NickDraper (2011-06-27T08:20:12):
"New" tickets moved at the code freeze of iteration 29


@NickDraper (2011-09-19T09:30:01):
Bulk move of tickets to iteration 31 at the iteration 30 code freeze


@NickDraper (2012-01-09T09:41:58):
Moved to iteration 33 at iteration 32 code freeze


@NickDraper (2012-04-30T14:10:05):
Moved at end of release 2.1


@NickDraper (2012-08-10T12:43:05):
Moved at the end of release 2.2


@NickDraper (2012-10-28T11:38:20):
Moved to milestone 2.4


@NickDraper (2013-04-29T09:49:26):
Moved to r2.6 at the end of r2.5


@NickDraper (2013-07-26T14:01:42):
Moved to the Backlog after R2.6


@NickDraper (2014-02-14T11:04:53):
Bulk move to assigned at the introduction of the triage step

@NickDraper NickDraper added High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Framework Issues and pull requests related to components in the Framework labels Jun 3, 2015
@martyngigg
Copy link
Member

This is very old and not something we plan to take forward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Framework Issues and pull requests related to components in the Framework High Priority An issue or pull request that if not addressed is severe enough to postponse a release.
Projects
None yet
Development

No branches or pull requests

3 participants