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
{{ message }}
This repository has been archived by the owner on Sep 1, 2024. It is now read-only.
As I am on macOS I cannot use the metavision library to work with evt3 files, and so I am using expelliarmus. So first thank you for this package !
Here is the context of my issue. I use expelliarmus to convert an evt3 file into a numpy array, and then I split the numpy array into sub-arrays, and then I save the sub-arrays into evt3 raw files using Wizard.save(). However, the timestamps of the raw saved sub-arrays are not the same as the ones of the numpy sub-arrays.
Any advice to correct this issue ?
Moreover, when I open the saved raw files with a text editor, I observe that the date appearing in the header is not the good one (year 1970 instead of 2023). I guess this is related to my issue.
Best,
Anthony
PS : I have already seen the issue #19 about timestamps problems, but I think that here it is a different issue.
The text was updated successfully, but these errors were encountered:
Hi,
As I am on macOS I cannot use the metavision library to work with evt3 files, and so I am using expelliarmus. So first thank you for this package !
Here is the context of my issue. I use expelliarmus to convert an evt3 file into a numpy array, and then I split the numpy array into sub-arrays, and then I save the sub-arrays into evt3 raw files using Wizard.save(). However, the timestamps of the raw saved sub-arrays are not the same as the ones of the numpy sub-arrays.
Any advice to correct this issue ?
Moreover, when I open the saved raw files with a text editor, I observe that the date appearing in the header is not the good one (year 1970 instead of 2023). I guess this is related to my issue.
Best,
Anthony
PS : I have already seen the issue #19 about timestamps problems, but I think that here it is a different issue.
The text was updated successfully, but these errors were encountered: