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
detailed_results_folder
Version: 0.8.0 (in development)
If I provide a detailed_results_folder, the items in that folder have very long names. That seem to follow the format:
<synthesizer_name>_<dataset_name>_<iteration_num>_<run_id>_data.gz <synthesizer_name>_<dataset_name>_<iteration_num>_<run_id>_scores.csv
Example:
results_folder/ |-- GaussianCopulaSynthesizer_alarm_1_181232_data.gz |-- GaussianCopulaSynthesizer_alarm_1_181232_scores.csv
But due to the changes we are making, iteration_num and run_id are not really needed. Especially if we enforce that synthesizers are unique (see #190)
iteration_num
run_id
Remove the iteration_num and run_id information from the file names. The resulting file names should be shorter & simpler.
results_folder/ |-- GaussianCopulaSynthesizer_alarm_data.gz |-- GaussianCopulaSynthesizer_alarm_scores.csv
The text was updated successfully, but these errors were encountered:
katxiao
Successfully merging a pull request may close this issue.
Version: 0.8.0 (in development)
Problem Description
If I provide a
detailed_results_folder
, the items in that folder have very long names. That seem to follow the format:Example:
But due to the changes we are making,
iteration_num
andrun_id
are not really needed. Especially if we enforce that synthesizers are unique (see #190)Expected behavior
Remove the
iteration_num
andrun_id
information from the file names. The resulting file names should be shorter & simpler.The text was updated successfully, but these errors were encountered: