As mentioned in April’s Monthly sync, I believe it’d be beneficial to have some form of custom measurement integration for BDF. In the consumer electronics industry, we are very concerned about swelling and thickness growth over time. Especially as new chemistries (silicon anode) present new swelling concerns, it would be good to have a way to incorporate this type of data alongside the electrochemical time-series data.
I wouldn’t want to limit this just thickness measurements as each industry and chemistry have their own challenges and metrics that they would like to track.
Initial thoughts on this implementation would likely require the JSON sidecar style metadata for a measurement type. The optional measurement that you would include would be defined in the JSON file to identify the “variableMeasured” with a “name” (that would align with the BDF column header) and “unitText” (which would also align with the BDF column header). Additional options would be to include description of the measurement.
These measurements may not be continuous throughout the testing, so the column would likely have a substantial amount of Null values.
For example, a common test in the consumer electronics industry is 1000 cycles at 100% depth of discharge. Every 100 cycles, the thickness of the pouch cell is measured with a parallel plate height gauge at 100% state of charge. The column in BDF would be “Thickness / mm” and the JSON sidecar for this custom measurement would likely include:
“variableMeasured”:
{
"@type": "PropertyValue", "name": "Thickness", "unitText": "mm", "description": "parallel plate height gauge at max state of charge", }
Thoughts? Would love to get outside perspective on this approach.