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
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ We also put a pre-processed set of the used clinical trials in `./datasets/trial
35
35
36
36
The first step of TrialGPT is to generate the criterion-level predictions, which include (1) the explanation of patient-criterion relevance, (2) locations of relevant sentences, and (3) the eligibility predictions.
37
37
38
-
Run the following code to get the GPT-4-based TrialGPT results for the three cohorts:
38
+
Run the following code to get the GPT-4-based TrialGPT results for the three cohorts (depending on the API response rate, matching a patient and a clinical trial normally takes less than 30s):
The second step of TrialGPT is to aggregate the criterion-level predictions to get trial-level scores, including one score for relevance and one score for eligibility.
49
49
50
-
Please make sure that the step 1 results are ready before running the step 2 code (depending on the API response rate, matching a patient and a clinical trial normally takes less than 30s):
50
+
Please make sure that the step 1 results are ready before running the step 2 code (depending on the API response rate, aggregating a patient-trial pair normally takes less than 20s):
The third step is to compute the performance of different linear features, LLM features, and the combined features.
61
61
62
-
Please make sure that the step 1 and step 2 results are ready before running the step 3 code (depending on the API response rate, aggregating a patient-trial pair normally takes less than 20s):
62
+
Please make sure that the step 1 and step 2 results are ready before running the step 3 code:
63
63
```bash
64
64
# first convert the results of each split into a csv file
0 commit comments