You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When I tried to import the windows in timsControl, it shows an error of "slices with different gradients are not supported by Bruker VistaScan. "
To Reproduce
Steps to reproduce the behavior:
use the following windows.
vista,0.64, 69.1, 100.3, 1.42, 1285.9
vista,0.64, 100.3, 131.6, 1.42, 1317.2
vista,0.64, 131.6, 162.8, 1.42, 1348.4
vista,0.64, 162.8, 194.1, 1.42, 1379.7
See the error in timsControl.
Additional context
I contacted Bruker support and got the following feedback.
"The cause of the error message was that the second and fourth diagonal-PASEF scan had a slightly different slope (m=1560.1282051282 instead of m=1560) compared to the first and third diagonal-PASEF scan.
Change the windows slightly as the following:
vista,0.64,69.1,100.3,1.42,1285.9
vista,0.64,100.3,131.6,1.42,1317.1
vista,0.64,131.6,162.8,1.42,1348.4
vista,0.64,162.8,194.1,1.42,1379.6
solve this issue."
The text was updated successfully, but these errors were encountered:
Describe the bug
When I tried to import the windows in timsControl, it shows an error of "slices with different gradients are not supported by Bruker VistaScan. "
To Reproduce
Steps to reproduce the behavior:
vista,0.64, 69.1, 100.3, 1.42, 1285.9
vista,0.64, 100.3, 131.6, 1.42, 1317.2
vista,0.64, 131.6, 162.8, 1.42, 1348.4
vista,0.64, 162.8, 194.1, 1.42, 1379.7
Additional context
I contacted Bruker support and got the following feedback.
"The cause of the error message was that the second and fourth diagonal-PASEF scan had a slightly different slope (m=1560.1282051282 instead of m=1560) compared to the first and third diagonal-PASEF scan.
Change the windows slightly as the following:
vista,0.64,69.1,100.3,1.42,1285.9
vista,0.64,100.3,131.6,1.42,1317.1
vista,0.64,131.6,162.8,1.42,1348.4
vista,0.64,162.8,194.1,1.42,1379.6
solve this issue."
The text was updated successfully, but these errors were encountered: