This PR aims at making the TrackMateImporter more robust against non pure integer frame numbers.
I received a MaMuT file from a collaborator that contained frame numbers, such as FRAME=0.0, FRAME=1.0, etc.
While the decimal digit does not make any sense, it seems to be the case that some MaMuT version are storing them, cf. this snippet from a MaMuT file:
This lead to an exception while importing the MaMuT file into Mastodon:
This PR aims at making the TrackMateImporter more robust against non pure integer frame numbers.
I received a MaMuT file from a collaborator that contained frame numbers, such as![grafik](https://github.com/mastodon-sc/mastodon/assets/10515534/da911f4e-2ee8-4de9-89d1-9191bf2fbe01)
FRAME=0.0
,FRAME=1.0
, etc. While the decimal digit does not make any sense, it seems to be the case that some MaMuT version are storing them, cf. this snippet from a MaMuT file:This lead to an exception while importing the MaMuT file into Mastodon:![grafik](https://github.com/mastodon-sc/mastodon/assets/10515534/85d464b3-9f96-4d56-9428-ccaf4d0ba8d2)
This PR provides a workaround for this situation.