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

Write PeakShape #196

Merged
merged 14 commits into from Feb 10, 2015
Merged

Write PeakShape #196

merged 14 commits into from Feb 10, 2015

Conversation

OwenArnold
Copy link
Contributor

see #10904

IntegratePeaksMD v1 and v2 write out integrated peak info in the form of PeakShape

PeakShapeSpherical adapted to write out background outer radius and background inner radius as well as the peak radius. Factories also updated for this, unit tests added to and updated for this.

I got a little worried that someone may change the integer values agaist the enum entries of SpecialCoordinateSystem. So I put in place a unit test to sanity check those.
Since we have put PeakShape in Geometry, SpecialCoordinateSystem must be moved to the Kernel package out of API.
Also fix GCC and Windows warnings
@martyngigg martyngigg added this to the Release 3.4 milestone Feb 10, 2015
@martyngigg martyngigg self-assigned this Feb 10, 2015
@martyngigg martyngigg added Single Crystal Issues and pull requests related to single crystal Vates labels Feb 10, 2015
@martyngigg
Copy link
Member

The script from the ticket works as expected and so do all of the methods on the new PeakShape class. I can see that most of the changes are due to the move of the SpecialCoordinateSystem.

@martyngigg martyngigg merged commit 35142ef into master Feb 10, 2015
@martyngigg martyngigg deleted the feature/10904_apply_peak_shape branch February 10, 2015 16:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Single Crystal Issues and pull requests related to single crystal Vates
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants