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
Copy file name to clipboardExpand all lines: docs/src/project.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -99,7 +99,7 @@ datadir() * "/foo/test.bson" # not recommended
99
99
100
100
## Reproducibility
101
101
The project setup approach that DrWatson suggests is designed to work flawlessly with Julia standards, to be easy to share and to be fully reproducible. There are three reasons that **true** reproducibility is possible:
102
-
1. The project's used packages are embedded in the project because of `Manifest.toml`
102
+
1. The project's used packages are embedded in the project because of `Manifest.toml`.
103
103
2. The navigation around the folders of the project uses local directories.
104
104
3. The project is a Git repository, which means that it has a detailed (and re-traceable) history of all changes and additions.
105
105
@@ -112,5 +112,5 @@ pkg> instantiate
112
112
to use your project (*assuming of course that you are both using the same Julia installation and version*).
113
113
All required packages and dependencies will be installed and then any script that was running in your computer will also be running in their computer **in the same way!**
114
114
115
-
In addition, with DrWatson you have the possibility of "tagging" each simulation created with the commit id, see the discussion around [`current_commit`](@ref) and [`tag!`](@ref).
115
+
In addition, with DrWatson you have the possibility of "tagging" each simulation created with the commit id, see the discussion around [`gitdescribe`](@ref) and [`tag!`](@ref).
116
116
This way, any data result obtained at any moment can be truly reproduced simply by resetting the Git tree to the appropriate commit and running the code.
0 commit comments