ASU-VDA-Lab / 2024_ICCAD_Contest_Gate_Sizing_Benchmark

10 stars 4 forks source link

Benchmark reference sizing results difference #5

Open Akilax0 opened 1 week ago

Akilax0 commented 1 week ago

Currently using the provided evaluation.py to test the given .size output files of the benchmark. However, I keep getting different values than the provided benchmark results at /design/README.md

For example running

image

would give the output as, image

while the provided outputs are image

bingyuew commented 1 week ago

Please confirm you are using the updated benchmark.

Akilax0 commented 1 week ago

Pulled again just now. Still the same results.

bingyuew commented 1 week ago

Please provide us with the benchmark you are using to reproduce the issue, including all necessary scripts.

Akilax0 commented 1 week ago

I have direct cloned the repository. https://github.com/ASU-VDA-Lab/2024_ICCAD_Contest_Gate_Sizing_Benchmark/tree/main

unzipped benchmark using the given script as unzip.sh

The script is unchanged : evaluation.py

for file_path : ../../design/NV_NVDLA_partition_m/NV_NVDLA_partition_m.size for design_name : NV_NVDLA_partition_m

(as in the first screenshot )

bingyuew commented 1 week ago

Please provide the files you are currently using so we can reproduce the issue.

Akilax0 commented 1 week ago

ICCAD_issue.zip

README.md has the instructions to reproduce

bingyuew commented 1 week ago

I cannot reproduce your issue. Please rebuild the OpenROAD binary and confirm that you are using the most up-to-date version of OpenROAD.

Akilax0 commented 1 week ago

I have rebuild and tested the same files on two separate machines. I keep getting the same output as above.

The outputs you got for the provided files , are they the same as the given results at /design/README.md ?

bingyuew commented 1 week ago

Yes, I am getting the same result as in the README file. Please make sure you have updated the submodules.

vickychen928 commented 1 week ago

@Akilax0 I encountered the same error as well. Have you managed to resolve it? image

bingyuew commented 1 week ago

@vickychen928 @Akilax0 Could both of you share the message from your cmake and the process of building the openroad binary?

vickychen928 commented 1 week ago

Here is the cmake and the process of building the openroad binary: cmake_log.txt make_log.txt

Akilax0 commented 6 days ago

Yeah, I get the same values still. I also tried with the docker file same result. Here are my cmake and make outputs.

make_log.txt cmake_log.txt

bingyuew commented 2 days ago

Hi @Akilax0 and @vickychen928 , please try using this Dockerfile.txt and let me know if the problem is fixed.

pipiofzl commented 1 day ago

I encountered the same issue when running the provided example with OpenROAD_example.py. The output.size file generated was then used in the evaluation script evaluation.py, which produced the results. image Similarly, when I used the design/NV_NVDLA_partition_m/NV_NVDLA_partition_m.size file with the evaluation.py script, the results did not match the Statistics provided on the GitHub page for NV_NVDLA_partition_m. image I would like to ask which programs were used to generate the Benchmark Statistics and the Reference Sizing Result Statistics provided on GitHub.

Thank you.

bingyuew commented 1 day ago

@pipiofzl Can you also share the message from your cmake and the process of building the openroad binary?

vickychen928 commented 1 day ago

@bingyuew I would like to ask if I need to make changes because the version specified in docker.txt is Ubuntu 22.04, but the computing platform I am using is Ubuntu 20.04?

pipiofzl commented 1 day ago

Here is the cmake and the process of building the openroad binary: cmake .. instruction: cmake.log make j 6 instruction: make_j_6.log make install instruction: make_install.log

Thank you.

Akilax0 commented 16 hours ago

@bingyuew I got the same results as @pipiofzl when using the Dockerfile image

Akilax0 commented 16 hours ago

@vickychen928 Shouldn't be an issue. Any reason why you asked this?

vickychen928 commented 10 hours ago

@Akilax0 There's no particular reason, just concerned whether specifying a different version from the platform might cause errors.