One still has often to manually adjust the automatic fits in the case of very weak peak (if at all) in the scan. pyzebra tends to fit such case to a hugely negative f0_intercept along with a huge positive f1_amplitude, or opposite, negative f1_amplitude, and positive f0_intercept. This averages out to a roughly even line -(
We can avoid such cases fixing f0_intercept > 0 (as f0_slope is fixed to zero this must be always the case), and f1_amplitude > 0
In the present comm format two empty spaces in the h k l should be eliminated:
Presently
1 -1 1 2 107.01 4.30 20.65 10.33 132.63 -144.74
Future
1 -1 1 2 102.05 3.71 20.65 10.33 132.63 -144.74
*Created by: zaharko*
1. One still has often to manually adjust the automatic fits in the case of very weak peak (if at all) in the scan. pyzebra tends to fit such case to a hugely negative f0_intercept along with a huge positive f1_amplitude, or opposite, negative f1_amplitude, and positive f0_intercept. This averages out to a roughly even line -(
We can avoid such cases fixing f0_intercept > 0 (as f0_slope is fixed to zero this must be always the case), and f1_amplitude > 0
2. In the present comm format two empty spaces in the h k l should be eliminated:
Presently
1 -1 1 2 107.01 4.30 20.65 10.33 132.63 -144.74
Future
1 -1 1 2 102.05 3.71 20.65 10.33 132.63 -144.74
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Created by: zaharko
We can avoid such cases fixing f0_intercept > 0 (as f0_slope is fixed to zero this must be always the case), and f1_amplitude > 0
Presently
1 -1 1 2 107.01 4.30 20.65 10.33 132.63 -144.74
Future
1 -1 1 2 102.05 3.71 20.65 10.33 132.63 -144.74