Closed johp1029 closed 7 years ago
It could be textual conversion function testRangeTableConv bug or in the write3 function. Coud you please do after open file ?: mdfreaderInstance.getChannelData(channelName) to have a look at the array and check if it is already ['V', ..., 'u']
I have found the bug in write3. The numberOfBits considered was not correct in case of string array. Give a try to latest commit
Ok, the latest commit solves our problem. Thank you!
Hi,
a co-worker of mine is using this library to open a MDF3 file, change some values and write it back to a file. He noticed, that textual conversions get lost after writing the file. Steps to reproduce:
The output looks like this:
Before writing, the channel contains a textual conversion and the data array contains numerical values.
After writing and reopening the file the conversion is lost and the data array contains only the first letter of the String representation.
Debugging showed that data is correct until this line is executed (in mdf3reader.py):
fid.write(pack('<' + dataTypeList * nRecords, *records)) # dumps data vector from numpy
Regards, Johannes