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: README.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,15 +21,17 @@ You can edit it there.
21
21
22
22
Note that the links-to-existing-GitHub-issues in the table are also defined in this script.
23
23
24
+
## I want to see the HTML generated by a PR!
25
+
26
+
The latest workflow run across all PRs will be published to https://turinglang.org/ADTests/pr.
27
+
28
+
This is a bit messy, but works for now on the assumption that there aren't many PRs being worked on simultaneously.
29
+
24
30
## What's going on?
25
31
26
32
The workflow is the most complicated part of this repository.
27
33
This section attempts to explain it from the 'bottom up'; if you prefer a 'top down' approach start by looking at the GitHub Action workflow, `.github/workflows/test.yml`.
28
34
29
-
Firstly, there is library code for running the benchmarks.
30
-
This is in `lib.jl`; it should (in the near future) be put directly into DynamicPPL.jl.
31
-
Until then, it has to live here.
32
-
33
35
Under the hood, the main thing that actually runs the AD tests / benchmarks is `main.jl`.
34
36
You can run `julia --project=. main.jl` and it will print some usage information.
35
37
However, it is the Python script `ad.py` that controls how this Julia script is called.
0 commit comments