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.

Sign up for GitHub

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

Jump to bottom

Make a decision on merging or keeping separate Nexus/DataHandling #4007

Closed
martyngigg opened this issue Jun 9, 2011 · 1 comment
Closed

Make a decision on merging or keeping separate Nexus/DataHandling #4007

martyngigg opened this issue Jun 9, 2011 · 1 comment
Assignees
@stuartcampbell
Milestone
Iteration 29

Comments

@martyngigg
Copy link
Member

Recently a change to DataHandling/LoadRaw/isisraw2 caused a strange failure on the intel compiler. It was if the code had not been put in. This was down to the fact that there was a separate copy of the isisraw structures in the NeXus package used by SaveISISNeXus and they were not updated.

We should make decision on whether we keep DataHandling and Nexus separate of not. If we are merging them then we only need to keep one copy but if we are not we should put isisraw2.cpp/h somewhere accessible to both so that this does not happen again.
@martyngigg
Copy link
Member Author

This issue was originally trac ticket 3160

@martyngigg martyngigg added this to the Iteration 29 milestone Jun 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@stuartcampbell stuartcampbell

Labels
None yet
Projects
None yet
Milestone
Iteration 29
Development

No branches or pull requests
2 participants
@stuartcampbell @martyngigg