You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is often useful to have the data storage structure reflect the structure of the notebooks. However, as notebooks get renamed and moved around the paths needs to be updated. I propose using dot (.) to indicate that data should be saved in the path equivalent to the currently running notebook. Runnning:
%vault store data in .
in a notebook located in analyses/main_analysis.ipynb would save the data in analyses/main_analysis path of the vault, i.e. be equivalent of running:
%vault store data in analyses/main_analysis
an alternative syntax would use double underscores, e.g.:
%vault store data in __here__
The dot syntax is more akin to the import syntax of Python (from . import x), thus slightly preferred.
The dot syntax could allow further path specification:
%vault store data_clean_1 in ./processed
%vault store data_clean_2 in ./processed
%vault store data_raw_1 in ./raw
%vault store data_raw_2 in ./raw
Support for .. could be considered too, but is outside of scope of this proposal.
The text was updated successfully, but these errors were encountered:
It is often useful to have the data storage structure reflect the structure of the notebooks. However, as notebooks get renamed and moved around the paths needs to be updated. I propose using dot (
.
) to indicate that data should be saved in the path equivalent to the currently running notebook. Runnning:in a notebook located in
analyses/main_analysis.ipynb
would save the data inanalyses/main_analysis
path of the vault, i.e. be equivalent of running:an alternative syntax would use double underscores, e.g.:
The dot syntax is more akin to the import syntax of Python (
from . import x
), thus slightly preferred.The dot syntax could allow further path specification:
Support for
..
could be considered too, but is outside of scope of this proposal.The text was updated successfully, but these errors were encountered: