Add multi component parsing to support XY-datasets #31
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #30
This pull request adds the two components to the parsing of a channel. This way XY-datasets can be parsed and xdata and ydata is properly set.
It utilizes the unused
imc_object.hpp
to cast every metadata key into a proper object. This may create a slight overhead because all parameters are parsed, but improves the readability IMO. It also implements the 6byte unsigned long datatype. Finally the buffer-size is exposed to the python interface to enable calculation of the file timespan without parsing the buffer.There is a naming inconsistency in
xoffset
because this variable name was used for the x0 parameter in normal datasets before but is applicable to the offset value of the x component as well. I renamed the x0 parameter variabel toxstart
but kept the namexoffset
in the python interface (get_info()
)