Does Kedro natively support parameters versioning?...
# questions
m
Does Kedro natively support parameters versioning? I’d like to know which parameters were used in a run for reproducibility
d
Have you checked out the Experiment Tracking workflow?
m
Hi, yes I have. From what I understand parameters versioning is made possible because the git info in Kedro Viz maps to the config specified in the source code when pipeline ran. However, say I override one of the parameters through CLI, is there any way to recover the resulting config? I was expecting "Run Command" in Kedro Viz to be updated accordingly but my testing showed it isn't (is this an issue on my end?).
d
The run command is persisted

https://docs.kedro.org/en/stable/_images/experiment-tracking-runs-list.png

m
indeed, but do we expect CLI args to appear in here as well? On my end, running
kedro run --params=some_param:2.5
still yields
kedro run
in Kedro Viz
d
let me check if that’s expected
so this is apparently a known issue - https://github.com/kedro-org/kedro-viz/issues/1020
the data is available in the session store sqlite db if you want to poke around there, but it’s not done today.
What I would say is that if you want to save your CLI parameters you could write your own hook the same way we do
kedro-telemetry
https://github.com/kedro-org/kedro-plugins/blob/main/kedro-telemetry/kedro_telemetry/plugin.py
m
Amazing 👍 thanks a lot I've exposed the extra params by tweaking the kedro viz code I think this should be enough for my use case for now. CLI param overrides can be reproduced by rerunning the pipeline with same git commit, and with the same CLI params
🥳 1
K 1
🎉 1
d
Super clever!
t
@Maxime Steinmetz that great! would you want to open a PR in the Kedro-Viz repo for that change? i think it would be very useful to other users
m
@Tynan I'd be very happy to! I'll get started on this 🙂
d
❤️
t
thank you!