This question was raised during the review of #12.
Throughout xml_files.py - all potential floating point data is regarded and cast to np.float32. The issues this presents are two-fold:
1) It adds a dependency of numpy to the class where it may not actually be necessary.
2) It requires np.float32 be cast back into a float for the purposes of serializing the data into json.
The question is - do the reasons for using np.float32 outweigh the issues laid out above?
1 - How much larger do MFFs and JSON that mffpy exports get if we use float in place of np.float32?
2 - What floating point precision do NetStation MFFs utilize?
This question was raised during the review of #12.
Throughout
xml_files.py
- all potential floating point data is regarded and cast tonp.float32
. The issues this presents are two-fold: 1) It adds a dependency ofnumpy
to the class where it may not actually be necessary. 2) It requiresnp.float32
be cast back into afloat
for the purposes of serializing the data intojson
.The question is - do the reasons for using
np.float32
outweigh the issues laid out above?