The meta.json is not always coherent. We need to define
When do we want to generate it (I think everytime we want to write something in the output directory, but then again we might write from certain stages at one time and then update it at another time)
This is problematic because we write the creation date into the meta.json. Maybe we should have just one file for the MATSim data and another one of the CSV data.
Second point is that rewriting the meta.json is not triggered by changing the commit in git. Because the commit ID is just obtained inside the stage, but a changed commit does not devalidate the stage. We should add the testing for the current commit into the validate function. We could just check whether there already is the target file and verify if we have the same output or not.
The
meta.jsonis not always coherent. We need to defineThis is problematic because we write the creation date into the meta.json. Maybe we should have just one file for the MATSim data and another one of the CSV data.
Second point is that rewriting the
meta.jsonis not triggered by changing the commit in git. Because the commit ID is just obtained inside the stage, but a changed commit does not devalidate the stage. We should add the testing for the current commit into thevalidatefunction. We could just check whether there already is the target file and verify if we have the same output or not.