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

Loaded log disagree with what shown in nxdir #7689

Closed
wdzhou opened this issue Apr 8, 2013 · 3 comments
Closed

Loaded log disagree with what shown in nxdir #7689

wdzhou opened this issue Apr 8, 2013 · 3 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. Stale This label is automatically applied to issues that are automatically closed by the stale bot

Comments

@wdzhou
Copy link
Collaborator

wdzhou commented Apr 8, 2013

This issue was originally TRAC 6843

It is so far only observed on log "Special1_0" in Vulcan run 20006. By nxdir, the first entry has time as 0.. The values from fist entry look like, 2, 3, 2, 3. Load the nexus file to MantidPlot. In sample log, it is found that the first entry of time is back to year 1710. And the values from first entry is 2, 2, 3, 2, ...

@wdzhou
Copy link
Collaborator Author

wdzhou commented Feb 14, 2014

@NickDraper (2013-04-29T09:49:28):
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:54):
Bulk move to assigned at the introduction of the triage step

@wdzhou wdzhou 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
@wdzhou wdzhou self-assigned this 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 High Priority An issue or pull request that if not addressed is severe enough to postponse a release. 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

1 participant