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

Combination of QxQz maps #12672

Closed
NickDraper opened this issue May 26, 2015 · 5 comments
Closed

Combination of QxQz maps #12672

NickDraper opened this issue May 26, 2015 · 5 comments
Labels
Awaiting User Response Waiting on input or testing from a third party ISIS Team: LSS Issue and pull requests managed by the LSS subteam at ISIS Reflectometry Issues and pull requests related to reflectometry Stale This label is automatically applied to issues that are automatically closed by the stale bot

Comments

@NickDraper
Copy link
Contributor

This issue was originally TRAC 11834

QxQz maps can be created using ConvertToReflectomtryQ.

This ticket is two allow two or more maps to be combined.

Speak to Tim Charlton to work out how they want them combined.


Keywords: reflOther

@NickDraper NickDraper added the Reflectometry Issues and pull requests related to reflectometry label Jun 3, 2015
@NickDraper NickDraper added this to the Release 3.5 milestone Jun 3, 2015
@NickDraper NickDraper modified the milestones: Release 3.5, Release 3.6 Sep 14, 2015
@NickDraper NickDraper modified the milestone: Release 3.6 Jan 22, 2016
@raquelalvarezbanos
Copy link
Contributor

Asked Tim about this:

The end goal is a user callable function similar to Stitch1DMany which could take a lift of 2D workspaces and a specification for the output grid. Combining full q-maps is tricky for two reasons, a) the relative scaling and b) the variation in bin size across the qx-qz surface. The output would be a seamless qx-qz-Intensity surface which could be used to extract 1D cuts along the primary coordinate axes. I believe that there are some tool which preform a similar task for diffraction data.

@raquelalvarezbanos
Copy link
Contributor

Marking this up against Release 3.8 as it was marked as Low priority. The estimated time to complete this task was initially 2-3 weeks.

@raquelalvarezbanos
Copy link
Contributor

In a meeting with Jos and Max today, we agreed that they will ask Tim about this, as they are not 100% sure it is the best way to combine the data.

@raquelalvarezbanos raquelalvarezbanos removed this from the Release 3.8 milestone Sep 16, 2016
@NickDraper NickDraper modified the milestones: Release 3.9, Temporary Holding Oct 12, 2016
@raquelalvarezbanos
Copy link
Contributor

I think this is no longer a requirement, at least scientists haven't mentioned this recently. I am leaving this open but we should ask them at some point if they still need this.

@NickDraper NickDraper removed this from the Temporary Holding milestone Oct 3, 2017
@gemmaguest gemmaguest added the ISIS Team: LSS Issue and pull requests managed by the LSS subteam at ISIS label Jul 24, 2019
@gemmaguest gemmaguest removed their assignment Jul 25, 2019
@gemmaguest gemmaguest added Awaiting User Response Waiting on input or testing from a third party Stale This label is automatically applied to issues that are automatically closed by the stale bot labels Jul 31, 2020
@gemmaguest
Copy link
Member

Closing as Stale because the scientists are not sure how this would be done anyway.

ISIS Large Scale Structures automation moved this from Backlog to Done Aug 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting User Response Waiting on input or testing from a third party ISIS Team: LSS Issue and pull requests managed by the LSS subteam at ISIS Reflectometry Issues and pull requests related to reflectometry Stale This label is automatically applied to issues that are automatically closed by the stale bot
Projects
Status: Stale
Development

No branches or pull requests

4 participants