-
Notifications
You must be signed in to change notification settings - Fork 90
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
[DISCUSSION] Using DrWatson for Non-Simulation Based Projects #375
Labels
Comments
why not make a Am I misunderstanding something? Because from what I understood the issue here is about what directories to use and naming things, right? Or it isn't? |
@TheCedarPrince can you provide an update here please? I am not sure if I have understood your problem/difficulty correctly. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi folks,
I am a huge fan of DrWatson and have used it for many of my projects. I am currently embarking on one of my most in-depth projects using DrWatson and its conventions. What I am struggling with right now is that I am not sure I am using DrWatson "correctly".
My work deals not so much in simulation but rather data analysis, data munging, and analysis reviews. I have automated much of my analyses already wherein I create notebooks that get placed inside of the
notebooks
directory, reports and papers into thepapers
directory, and temporary data in the_research/tmp
directory (per documentation). What I am running into, is that for my reports, I do need to manually go through each report and add additional summaries and reviews to each one based on the automated analyses I ran. In a DrWatson workflow, I am struggling about where to save these summaries as they will remain the same until data changes (I am using DVC for data provisioning here).In a sense, they are "results" but they do not seem to align with the DrWatson workflow so I am unsure of where to put this data. Any thoughts or suggestions?
Thanks!
~ tcp 🌳
The text was updated successfully, but these errors were encountered: