We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently we can convert from legacy format to json, but not the other way around.
This leads to creating new configurations in the legacy format for everything where we need to benchmark agains algorithms that use the legacy format.
Adding the option to convert to legacy format could reduce the amount of new configurations in legacy format.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently we can convert from legacy format to json, but not the other way around.
This leads to creating new configurations in the legacy format for everything where we need to benchmark agains algorithms that use the legacy format.
Adding the option to convert to legacy format could reduce the amount of new configurations in legacy format.
The text was updated successfully, but these errors were encountered: