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
{{ message }}
This repository has been archived by the owner on Oct 31, 2023. It is now read-only.
The degeneracy check in generate_questions.py is applied only when there is a "raw" relate node in the template. This effectively means that it is only applied to question families defined in templates/single_and.json. Was this also the case when the original dataset was generated?
On a related note, when I generate new questions, many degenerate questions are not detected because of the object uniqueness check. Is often the case that the output of intersection refers to several objects, and yet all of them have the same value for the queried attributed. Is that by design?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The degeneracy check in
generate_questions.py
is applied only when there is a "raw"relate
node in the template. This effectively means that it is only applied to question families defined intemplates/single_and.json
. Was this also the case when the original dataset was generated?On a related note, when I generate new questions, many degenerate questions are not detected because of the object uniqueness check. Is often the case that the output of
intersection
refers to several objects, and yet all of them have the same value for the queried attributed. Is that by design?The text was updated successfully, but these errors were encountered: