Update vamas.py for floating coordinate in MAP file

[StephaneGuilet]

Some MAP VAMAS file in XPS give coordinate in a floating format (example: -2.156) when you read the file you get a string like '-2.156\n' which cause a fault when using int() I propose to use int(float('-2.156\n')) to get the int value of the coordinate

[matkrin]

Thanks for reporting this. Unfortunately, I could never test MAP files.
Do you know if there are cases in which the value is closer to the next higher integer?
E.g. int(float(2.9) would give a value of 2. Is that the bahavior we want or does 3 make more sense?

[StephaneGuilet]

Thanks for reporting this. Unfortunately, I could never test MAP files. Do you know if there are cases in which the value is closer to the next higher integer? E.g. int(float(2.9) would give a value of 2. Is that the behavior we want or does 3 make more sense?

Sorry, didn't see you question. Back to use this library, I don't know exactly what to answer. My case was a user with a MAP file with only one spectra. Maybe I should ask for an image to test the result of the data extraction on real MAP file.

[matkrin]

In general, it would be nice if we would have a bit more files, ideally from different machines of which we know the parameters that were set. Then we could write more tests to catch edge cases like this one. Personally, I just have access to one AES and one XPS.
Let me know if you want to share some files (can be meaningless data, as it gets added to this repo) or even write some tests. It would help a lot.