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

Masking redesign - design document #9757

Closed
NickDraper opened this issue Feb 7, 2014 · 2 comments
Closed

Masking redesign - design document #9757

NickDraper opened this issue Feb 7, 2014 · 2 comments
Assignees
Labels
Extra Attention Testers and Gate keepers should pay extra attention as this affects core aspects. Framework Issues and pull requests related to components in the Framework

Comments

@NickDraper
Copy link
Contributor

This issue was originally TRAC 8914

This ticket is blocks : TRAC9273

Some previous documents are here
https://github.com/mantidproject/documents/tree/master/Design/Masking

"Revisit requirements
Plan for development"

Keywords: SSC,CORE,2014,All, masking

@NickDraper
Copy link
Contributor Author

@NickDraper (2014-02-14T10:59:49):
Bulk move of tickets out of triage (new) to assigned at the introduction of the triage state


@PeterParker (2014-03-19T14:40:08):
There is a problem with the current state of LoadMask/SaveMask, whereby date information corresponding to the run being masked does not survive the "roundtrip" of being written out and then read back in. This is problematic for runs which use an older version of an instrument's IDF.

There are more details in http://trac.mantidproject.org/mantid/ticket/9205, which is a ticket to implement a makeshift solution to this problem that will suit the needs of the SANS ISIS interface. A redesign of masking should probably include something more substantial.


@NickDraper (2014-10-08T12:45:35):
Moved to backlog to make room for VATES adoption acceleration project


@NickDraper (2014-12-03T11:29:41):
Move all SSC tickets to critical by default


@NickDraper (2015-03-10T15:49:01):
Batch modify all SSC tickets to critical priority (this will also show up as an update for all those already as critical)


@martyngigg (2015-03-20T16:01:05):
Time estimate for design: 1 month. Very long due to experience in the past on trying to pin down requirements and come up with a sound design

@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 SSC Extra Attention Testers and Gate keepers should pay extra attention as this affects core aspects. labels Jun 3, 2015
@NickDraper NickDraper self-assigned this Jun 3, 2015
@NickDraper NickDraper removed the High Priority An issue or pull request that if not addressed is severe enough to postponse a release. label Mar 8, 2016
@NickDraper
Copy link
Contributor Author

Archiving

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Extra Attention Testers and Gate keepers should pay extra attention as this affects core aspects. Framework Issues and pull requests related to components in the Framework
Projects
None yet
Development

No branches or pull requests

1 participant