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
Add a metadata file (text file) that describes the environment and settings used for the benchmark run.
As there is information that can only be gathered in the container
In-Container Information
This information is only available in the container and we need a script for each combination of (benchmark program, tool).
Number of operations (additions, multiplications, relinearizations)
this and this could be helpful functions for Cingulata
System / EC2 VM Information
This is information that is not available in the docker container but must be gathered on the EC2 VM.
The script collecting this information is usable for all benchmark programs.
@AlexanderViand What do you think about adding the git commit SHA to the S3 folder name? Would this break something related to the visualization website?
Note to myself - this would require the following change to L43@benchmark.yml:
The text was updated successfully, but these errors were encountered:
pjattke
changed the title
Generate metadata file as output in Cardio SEAL-BFV
Generate metadata file as output in Cardio SEAL-BFV & Cingulata
Aug 6, 2020
Add a metadata file (text file) that describes the environment and settings used for the benchmark run.
As there is information that can only be gathered in the container
In-Container Information
This information is only available in the container and we need a script for each combination of (benchmark program, tool).
print_parameters(...)
inexamples.h
System / EC2 VM Information
This is information that is not available in the docker container but must be gathered on the EC2 VM.
The script collecting this information is usable for all benchmark programs.
git rev-parse HEAD
@AlexanderViand What do you think about adding the git commit SHA to the S3 folder name? Would this break something related to the visualization website?
Note to myself - this would require the following change to L43@
benchmark.yml
:The text was updated successfully, but these errors were encountered: