Open tjsego opened 2 months ago
I am fine with a csv scheme update. Imho the json format should also be adapted accordingly (com1/2 can be arrays of arrays).
Discussion outcome: format supports additional data beyond column 4. Headers will not be included. Otherwise, proposed format as noted here is how we will proceed.
@tjsego just to clarify: what do you mean with "headers will not be included" - just that we don't specify the required header in the schema, right? Because I currently still assume the csv to have some header, I just don't use the column names internally.
@tjsego just to clarify: what do you mean with "headers will not be included" - just that we don't specify the required header in the schema, right? Because I currently still assume the csv to have some header, I just don't use the column names internally.
I was originally envisioning starting the data with something like the following:
time,id,com_1,com_2,other_data_entry
...
Each column label would correspond to an entry in our data schema and "other_data_entry" would be optional additional data (e.g., cell area).
comparison
module updated in https://github.com/tjsego/PersistentCell/commit/c7b943df7da8eb79460cabbcb7b6a0de689cb094.
CC3D implementation updated in https://github.com/tjsego/PersistentCell/commit/e5d3bfa957492322ac79b1ec829970c298974b44.
Tissue Forge implementation updated in https://github.com/tjsego/PersistentCell/commit/77524ae0892ff3c05d4a9326907bef364e9aff2d.
@ingewortel proposed the following csv format:
I proposed adding a header following the labels in the data schema, with appropriate additions.