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

Lost detector pixels with LoadInstrument #6323

Closed
VickieLynch opened this issue Jun 16, 2012 · 3 comments
Closed

Lost detector pixels with LoadInstrument #6323

VickieLynch opened this issue Jun 16, 2012 · 3 comments
Assignees
Labels
Framework Issues and pull requests related to components in the Framework Stale This label is automatically applied to issues that are automatically closed by the stale bot

Comments

@VickieLynch
Copy link
Contributor

This issue was originally TRAC 5477

With the NOMAD geometry, if I LoadInstument with RewriteSpectrMap=True, the first 2 workspace indices are monitors and the last 2 detector pixels are not in workspace. You can compare "Show Detectors" before and after LoadInstrument to see the problem. Here are the commands to test:

#!python
LoadEventNexus(Filename='NOM_3778_event.nxs',OutputWorkspace='NOM_3778',ChunkNumber='1',TotalChunks='20',MonitorsAsEvents='1')
LoadInstrument(Workspace='NOM_3778',Filename=r'NOMAD_Definition_20120701-20120731.xml',RewriteSpectraMap='1')
@VickieLynch
Copy link
Contributor Author

@NickDraper (2012-06-21T12:44:10):
Martyn, can you help diagnose this?


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


@NickDraper (2012-10-28T11:39:01):
Moved to milestone 2.4


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


@martyngigg (2013-07-15T08:46:44):
Batch move to 2.7


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

@VickieLynch VickieLynch added the Framework Issues and pull requests related to components in the Framework label Jun 3, 2015
@stale
Copy link

stale bot commented Feb 24, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. If you feel this is incorrect please comment to keep it alive, with a reason why.

To prevent closure, e.g. for long-term planning issues, add the "Never Stale" label.

@stale stale bot added the Stale This label is automatically applied to issues that are automatically closed by the stale bot label Feb 24, 2021
@stale
Copy link

stale bot commented Mar 3, 2021

This issue has been closed automatically. If this still affects you please re-open this issue with a comment so we can look into resolving it.

@stale stale bot closed this as completed Mar 3, 2021
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 Stale This label is automatically applied to issues that are automatically closed by the stale bot
Projects
None yet
Development

No branches or pull requests

2 participants