Error when running `D = OpenTIMS(path)` in python.

[LipidAnalysis]

I meet the following error when running D = OpenTIMS(path) in python.
"RuntimeError: dlopen(/root/anaconda3/envs/python367/lib/python3.6/site-packages/opentims_bruker_bridge/win64/timsdata.dll) failed, reason: /root/anaconda3/envs/python367/lib/python3.6/site-packages/opentims_bruker_bridge/win64/timsdata.dll: invalid ELF header"
What could be the possible reason?

[michalsta]

Hi,

It seems that for some reason your Anaconda setup couldn't find/load the .so file containing conversion functions, and, sadly, the error reporting in this situation is completely misleading.
Basically we distribute a linux, win32 and win64 version of the library, and the function just tries loading them until one succeeds. The nasty thing is it reports only last error, which, well, of course a win64 dll isn't going to load on Linux. However, why did the .so fail? Well, that remains to be seen.

Long story short, would you mind checking out the devel branch of opentims, installing opentimspy from there, and reporting what happens? Hopefully it'll at least be a more enlightening error message ;)

[LipidAnalysis]

Thank you for your response!
I met the error when I used a jupyter-lab on a web-server. As you said I forgort to download the '.so' or '.dll' first. Currently, I can read the '.d' file.
Unfortunately, I meet another problem that I cannot get a proper "inv_ion_mobility" value, the values changes even when I change to columns to query. For example, when I use columns ["frame", "inv_ion_mobility"], I will get mobility values around 1.5, but when I add "scan" in columns, I will get values from 1e-5 to 1e5. Does it occur on your data?
P.S. My data is collected from TIMS but not TIMS pro, does it matter?

[MatteoLacki]

Hi,

It might matter: if you could, please share the data with us to inspect it.

Best,

[LipidAnalysis]

Hi, MatteoLacki!
I have sent you an email, and my email address is "zhangdh17@mails.tsinghua.edu.cn", Please check it out.
Thank you!

[michalsta]

Okay, I have reproduced this, now I'm investigating

[michalsta]

Okay, it does seem to be a case of different file format. We'll have to confirm this with Bruker people, and either add support, or at least cleanly fail (throw an appropriate exception) when we detect something like this. We hope to have some more info by the end of the week.

[LipidAnalysis]

Thank you for your reply and look forward to a good result!

[LipidAnalysis]

Is there any progress in this field?

[MatteoLacki]

Hi, Sorry, but it is a bit of a vacation time. Indeed, we confirm that reading the data produces humbug. We need some help from Bruker and I have contacted them. We wait for the answer. Best wishes, *Mateusz Krzysztof Łącki* *German tel. +49 159 01681376* Polish tel. +48 579 647 311 Skype: mathewin GitHub: MatteoLacki <https://github.com/MatteoLacki>

…

On Fri, Jul 30, 2021 at 8:14 AM LOA_Release B ***@***.***> wrote: Is there any progress in this field? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA6H2AEKZJN66F5RBAQNORLT2I7LLANCNFSM47LEQW2A> .

[MatteoLacki]

Hi,

Currently we do not support this data. This is, unfortunately, an older inefficient scheme that Bruker does no longer use.
We are still in touch with Bruker on the case and if it is not too difficult to implement eventually do it, but they are pretty busy there and I would not bet money on that getting to be done quickly, sorry.

Best,

[LipidAnalysis]

Thank you for your response!
It seems impossible for me to collect CCS information now. But good news is the instrument in my Lab will be upgraded soon, and data can be analyzed much easier.
Thanks again for your help!