-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Track pygmt/tests/data
using dvc?
#1775
Comments
I had a similar idea at #1695 (comment) with the For this track.txt file, since it is plain-text, I think we can store it in git history as long as it isn't too long (maybe 10-20 lines). But I think it's worth discussing whether we should look into storing certain binary files using |
Sounds good, thanks for the input. I will track that file with git and will leave this issue open for now. |
The grdtrack tests modified in #1762 require a new .csv file for input. Rather than adding more files to the GMT cache or generating a .csv file within those tests, I am wondering if we can start tracking the folder
pygmt/tests/data
using dvc? In this case, we could easily add a new filetrack.txt
that contains the necessary points without including it in the git history. This path forward may require some modifications to the dvc-diff workflow and adding these files to the release assets (xref #1317).The text was updated successfully, but these errors were encountered: