Hi,
I'd like to ask a question about the names, especially the suffixes, of config files contained in the BSEC 2.0.6.1 Generic Release ZIP file.
The integration guide that is part of the ZIP file mentions two different solutions, IAQ and SELECTIVITY.
The older BSEC 1 provides only the IAQ solution; config files there are named bsec_serialized_configurations_iaq.c /.h
In BSEC2, which supports IAQ and SELECTIVITY, I would expect config files with the suffix _iaq, and files with suffix _selectivity.
To my surprise, within ./config I can only find files with the latter suffix, for instance:
./config/generic_18v_3s_4d/bsec_serialized_configurations_selectivity.c
Shouldn't this file, and the contained array, be named
./config/generic_18v_3s_4d/bsec_serialized_configurations_iaq.c instead?
This assumption seems to be supported by the fact that the BSEC2 ZIP file also contains these files:
- ./examples/bsec2/src/bsec_serialized_configurations_selectivity.c <- (equals config/bsec_sel_iaq_18v_4d)
- ./examples/bsec2/src/bsec_serialized_configurations_iaq.c <- (equals mostly config/generic_18v_3s_4d/*_selectivity.c)
The first matches exactly config/bsec_sel_iaq_18v_4d/bsec_serialized_configurations_selectivity.c,
while the second contains exactly the same array as ./config/generic_18v_3s_4d/bsec_serialized_configurations_selectivity.c,
just named _selectivity, not _iaq.
So I suppose generic_ config files in BSEC 2.0.6.1 are just named *_selectivity.c/.h by mistake?
