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

Make sample and log loading more transparent in LoadISISNexus #9541

Closed
Anders-Markvardsen opened this issue Jan 13, 2014 · 1 comment
Closed
Assignees
Labels
Framework Issues and pull requests related to components in the Framework Maintenance Unassigned issues to be addressed in the next maintenance period.

Comments

@Anders-Markvardsen
Copy link
Member

This issue was originally TRAC 8697

Loading of sample and log are done in two places. Post to fixing http://trac.mantidproject.org/mantid/ticket/8608 this is: (prior to http://trac.mantidproject.org/mantid/ticket/8608 this was done indirectly through loadExperimentInfoNexus)

  // Load logs and sample information
  m_cppFile->openPath(entry.path());      
  local_workspace->loadSampleAndLogInfoNexus(m_cppFile);

  // Load logs and sample information further information... See mainteance ticket #
  loadSampleData(local_workspace, entry);
  m_progress->report("Loading logs");
  loadLogs(local_workspace, entry);

Keywords: Maintenance

@Anders-Markvardsen
Copy link
Member Author

@NickDraper (2014-02-02T15:34:53):
Moved to backlog at the end of Release 3.1


@NickDraper (2014-02-14T11:07:55):
bulk move to assigned at the into of the triage step

@Anders-Markvardsen Anders-Markvardsen added Framework Issues and pull requests related to components in the Framework Maintenance Unassigned issues to be addressed in the next maintenance period. labels Jun 3, 2015
@Anders-Markvardsen Anders-Markvardsen self-assigned this Jun 3, 2015
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 Maintenance Unassigned issues to be addressed in the next maintenance period.
Projects
None yet
Development

No branches or pull requests

1 participant