Renaming data column names in posterior files about posteriordb HOT 3 CLOSED

Yes. But it increases the complexity so I think we skip it for now and maybe it is a natural extension later on.

from posteriordb.

I had an idea for how to make this more general. I don't think this is high priority but I wanted to write this down in case it might be useful at some point.

One way to achive this would be to have slots data_transformation and data_transformation_arguments.

So we might have

{
  "model": "linreg",
  "data": "sales",
  "data_transformation": "rename",
  "data_transformation_arguments": {
    "advertising_spend": "x",
    "sales": "y"
  }
}

Then essentially the python and R packages would map rename to some function and call some_function(data, data_transformation_arguments) during get_data(po).

Essentially we would have a finite set of allowed data_transformation values and each of these would be mapped to some function in the posteriordb library.

Again, I don't think this is necessary at the moment but something to keep in mind.

from posteriordb.

Currently, this is solved in the design choices where we state that the data is static. So I close this one for now.

from posteriordb.