I am trying to use the MeasurementsExporter as per the example here
One issue we have been faced with is when exporting counts of different CellObject classes as a result from a multiplex analysis like the one shown here:
Because the MeasurementExporter only exports measurements which exist, this causes different column numbers and orders when exporting results from different projects, in the case that some categories do not exist.
For example, we are trying to classify cells into 3 classes: A, B and C
Each cell could be A, B, AB, AC, BC or ABC
Suppose that for one project with some settings , we get all classes represented, but for a second project other classes are missing (which is an interesting phenotype)
Now the results tables have a different number of columns, which makes concatenation of these difficult.
Would it be possible to make it so that if the column name is specified explicitely by the user (using
includeOnlyColumns), then it must appear in the results table, even if it does not exist? This would make downstream processing easier.
Otherwise, what workaround could we use to define this statistic and ensure it is always present for export?
I know we could try to put everything into a single project but this is not convenient when running a new analysis with new data. However it would be nice to be able to directly compare the results without having to resort to table manipulation in another software.
Thanks for any insight