How to Compute Conflicts Between Users
In general, conflicts can and should be computed using Paper Matching Setup. However, there may be cases where you do not want to re-compute conflicts for all reviewers and submissions or you want to use your own conflict policy to compute conflicts between users and submissions. You can use the python client to manually check for conflicts between the reviewers and authors like so:
Compute conflicts between reviewers and authors of a single submission
If you have not done so, you will need to install and instantiate the openreview-py client.
Get the note that you are interested in computing conflicts for.
3. Get profiles for the submission authors and the reviewers. The reviewer group id should be something like your conference id/Submission#/Reviewers, for example if your submission of interest is submission 99:
4. Compute the conflicts. If no conflicts are found, get_conflicts
will return an empty list. Otherwise, the list will contain the shared groups that put them in conflict with each other.
The last step is posting the conflict Edges. You can follow this guide to post custom conflicts, and keep the label as 'Conflict'.
Compute conflicts between reviewers and authors of all submissions
Get all submissions, authorids of all submissions, and the author and reviewer Profiles. If you're using a custom policy that does not need the author's publications, you can exclude
with_publications=True
Get conflicts for each reviewer.
The last step is posting the conflict Edges. You can follow this guide to post custom conflicts, and keep the label as 'Conflict'.
Last updated