-
Notifications
You must be signed in to change notification settings - Fork 20
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
Laue case in SRW sroptcryst.h file #118
Comments
Definition of |
In the case that the definition of bee would be 1/(1+(nh)/(nk0)) is needed to define the asymmetry variable for a symmetric Laue case as pi/2 and not 0. It should work and I think I have an old version from 2016 that was able to reproduce Laue in this way. |
The more important part of this issue it is not the definition of bee, but the inclusion of the Zachariasen equations for Laue geometry that are still not in sroptcryst.h. |
@Angelrf86, I didn't find sroptcryst.h in the WPG repository. Here it is in O Chubar's SRW repository: |
At the moment the sroptcryst.h is only defined for Bragg: char m_uc; // crystal use case: 1- Bragg Reflection, 2- Bragg Transmission (Laue cases to be added) We could add the Laue cases as 3.- Laue Reflection and 4.- Laue Transmission. In line 133 should be changed the range m_uc from m_uc > 2 to m_uc > 4
In line 138 should be changed that also m_uc == 4 is a transmitted case.
I would add a variable that defines if is Laue or Bragg Geometry, which depends of m_uc:
Below in line 894 of the code is needed to introduce the Laue case equations:
|
We have been looking to the file to try to include the Laue geometry in the
sroptcryst.h
and we think that the definition of the variablebee
is not general. Thebee
variable definition only agrees with Zachariasen in the case of symmetric Bragg. In order to be used both in Laue and Bragg case, it's sensible to definebee
asgamma_0/gamma_h
.We also think that it will be interesting to define how the asymmetry parameter is define in python script. tbc
The text was updated successfully, but these errors were encountered: