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
+28-9Lines changed: 28 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,23 +56,42 @@ For more information on how to use the Causal Testing Framework, please refer to
56
56
>[!NOTE]
57
57
>We recommend you use a 64 bit OS (standard in most modern machines) as we have had reports of the installation crashing on some 32 bit Debian installations.
58
58
59
+
## Usage
60
+
>[!NOTE]
61
+
> Example usage can be found in the `examples` directory.
62
+
63
+
1. To run the causal testing framework, you need some runtime data from your system, some causal test cases, and a causal DAG that specifies the expected causal relationships between the variables in your runtime data (and any other relevant variables that are _not_ recorded in the data but are known to be relevant).
64
+
65
+
2. If you do not already have causal test cases, you can convert your causal DAG to causal tests by running the following command.
The results will be saved for inspection in a JSON file located at `$OUTPUT`.
76
+
In the future, we hope to add a visualisation tool to assist with this.
77
+
59
78
## How to Cite
60
79
If you use our framework in your work, please cite the following:
61
80
62
-
``This research has used version X.Y.Z (software citation) of the
81
+
``This research has used version X.Y.Z (software citation) of the
63
82
Causal Testing Framework (paper citation).``
64
83
65
-
The paper citation should be the Causal Testing Framework [paper](https://dl.acm.org/doi/10.1145/3607184),
84
+
The paper citation should be the Causal Testing Framework [paper](https://dl.acm.org/doi/10.1145/3607184),
66
85
and the software citation should contain the specific Figshare [DOI](https://orda.shef.ac.uk/articles/software/CITCOM_Software_Release/24427516) of the version used in your work.
67
86
68
87
69
88
70
89
<details>
71
90
<summary><b>BibTeX Citations</b></summary>
72
-
91
+
73
92
<details>
74
93
<summary>Paper</summary>
75
-
94
+
76
95
```
77
96
@ARTICLE{Clark_etal_2023,
78
97
author = {Clark, Andrew G. and Foster, Michael and Prifling, Benedikt and Walkinshaw, Neil and Hierons, Robert M.
@@ -89,10 +108,10 @@ and the software citation should contain the specific Figshare [DOI](https://ord
89
108
```
90
109
91
110
</details>
92
-
111
+
93
112
<details>
94
113
<summary>Software (example)</summary>
95
-
114
+
96
115
```
97
116
@ARTICLE{Wild2023,
98
117
author = {Foster, Michael and Clark, Andrew G. and Somers, Richard and Wild, Christopher and Allian, Farhad and Hierons, Robert M. and Wagg, David and Walkinshaw, Neil},
@@ -114,15 +133,15 @@ To contribute to our work, please ensure the following:
114
133
1.[Fork the repository](https://help.github.com/articles/fork-a-repo/) into your own GitHub account, and [clone](https://docs.github.com/en/repositories/creating-and-managing-repositories/cloning-a-repository) it to your local machine.
115
134
2.[Create a new branch](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository) in your forked repository. Give this branch an appropriate name, and create commits that describe the changes.
116
135
3.[Push your changes](https://docs.github.com/en/get-started/using-git/pushing-commits-to-a-remote-repository) to your new branch in your remote fork, compare with `CausalTestingFramework/main`, and ensure any conflicts are resolved.
117
-
4. Create a draft [pull request](https://docs.github.com/en/get-started/quickstart/hello-world#opening-a-pull-request) from your branch, and ensure you have [linked](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls) it to any relevant issues in your description.
136
+
4. Create a draft [pull request](https://docs.github.com/en/get-started/quickstart/hello-world#opening-a-pull-request) from your branch, and ensure you have [linked](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls) it to any relevant issues in your description.
118
137
119
138
We use the [unittest]() module to develop our tests and the [pytest](https://pytest.org/en/latest/) framework as our test discovery, [pylint](https://pypi.org/project/pylint/) for our code analyser, and [black](https://pypi.org/project/black/) for our code formatting.
120
139
To find the other (optional) developer dependencies, please check `pyproject.toml`.
121
140
122
141
123
142
124
-
## Acknowledgements
143
+
## Acknowledgements
125
144
126
145
The Causal Testing Framework is supported by the UK's Engineering and Physical Sciences Research Council (EPSRC),
127
-
with the project name [CITCOM](https://gow.epsrc.ukri.org/NGBOViewGrant.aspx?GrantRef=EP/T030526/1) - "_Causal Inference for Testing of Computational Models_"
146
+
with the project name [CITCOM](https://gow.epsrc.ukri.org/NGBOViewGrant.aspx?GrantRef=EP/T030526/1) - "_Causal Inference for Testing of Computational Models_"
0 commit comments