# How to Post a Custom Conflict

If you are using automatic matching, you can generate conflicts automatically with Paper Matching Setup. Sometimes Program Chairs additionally want to create custom conflicts between certain users and certain papers. This can be done by posting an edge to the conflict edge invitation for your venue. 

1. If you have not done so, you will need to [install and instantiate the openreview-py client](/getting-started/using-the-api/installing-and-instantiating-the-python-client.md).
2. Determine the conflict invitation you will be using. If you are creating a custom conflict edge for a reviewer, it would be `<your_venue_id>/Reviewers/-/Conflict`. If it is for an Area Chair, it would be `<your_venue_id>/Area_Chairs/-/Conflict`.

```python
venue_group = client_v2.get_group(venue_id)
invitation = venue_group.content['reviewers_conflict_id']['value]
# For ACs: venue_group.content['area_chairs_conflict_id']['value]
# For SACs: venue_group.content['senior_area_chairs_conflict_id']['value]
```

3. Set a variable '`tail`' to the user you are generating the conflict for. Set a variable '`head`' to the ID of the submission you want to create the conflict for. For example:

```python
tail = "~User_One1"
head = "ggVj9Mmq2-a"
```

4. Set the readers of this conflict. In general, this should include the `tail` of the edge and anyone who might be making assignments for this group, such as Area Chairs or Senior Area Chairs.

{% hint style="warning" %}
Confirm who the readers should be by going to: `openreview.net/invitation/edit?id=<conflict_invitation>` and checking the readers.
{% endhint %}

```python
readers = [
    "~User_One1", 
    "your_venue_id",
    "<your_venue_id>/Area_Chairs"
]
```

5. Optionally set a label for your custom conflicts. This can help you query and retrieve them later.&#x20;

```python
label = "Custom Conflict"
```

6. Finally, create and post an edge with a weight of `-1` between the user and the paper. This will make the conflict a hard constraint.&#x20;

```python
client_v2.post_edge(openreview.api.Edge(
   invitation = invitation,
   label = label, 
   weight = -1, 
   head = head, 
   tail = tail,
   signatures = [
    "<your_venue_id>"
   ],
   readers = [
    "<your_venue_id>"
   ],
   writers = [
    "<your_venue_id>"
]))
```

7. If you're posting a lot of conflicts, you can build a list of Edges and post them all at once with `post_bulk_edges`.

```
openreview.tools.post_bulk_edges(client=client_v2, edges=[list of conflict Edges])
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.openreview.net/how-to-guides/paper-matching-and-assignment/how-to-post-a-custom-conflict.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.