Improve Results Directory Structure for Better Organization and Context #34
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Initially, the result storage system generated only a single folder within the results directory, identified solely by the date and time (timestamp) of when the tests were performed. Although functional, this approach proved impractical as the number of tests increased, making the organization and retrieval of specific attacks confusing and inefficient.
To address this limitation, we implemented a small adaptation in the directory generation process. Now, for each test execution, a folder is created and hierarchically organized by model, with its name including not only the timestamp but also the type of attack and the language used.
The new format follows this structure: results/model_name/attacktype__timestamp
This improvement allows for much more intuitive and faster navigation, and ensures that the results are stored in a contextualized manner, facilitating both individual analysis and comparison across different models.