Closed hyerinshelly closed 1 year ago
The issue is with the SEAL library version. The configuration file used in the tutorials is for SEAL version 3.3.2, but now E3 uses SEAL 3.7 as the default option. We have been slowly updating the tutorials to work with the newer version. I suppose a quick fix is to simply replace the encoder in the cgt file from 'integer' to 'batch' since SEAL 3.7 does not support the former encoder.
In any case, I see you are interested in the benchmarks used in ICCAD. The ones currently available in the public repository are not the ones used for ICCAD's paper. I will prepare a readme and upload those to the public repository in the following days. They have been tested with SEAL 3.7.
Alright. Please, check e3/benchmarks/bridging for the benchmarks used in ICCAD's paper.
I really appreciate for your quick response! I took a look at the benchmark directory and again tried running with.
Sorry to say this, it reproduces exactly same error (regarding to 'for_each_n'), even though I checked the cgt file having 'batch' option instead of 'integer'.
Then what the problem could be? (I guess the version of SEAL is not the one..) Thanks, again!
Hello,
I'm interested in the experiment shown in your paper, but struggling with tutorial.
I've tried on the commit 9fb718f which is mentioned in your ICCAD '22 paper, but bridging bench is not working due to the error related to SEAL. I already went through and saw the issue(#14) with building SEAL. This is why I tried on the commit of paper version. However, I couldn't still run the bridging example on the tutorial. The error message indicates that the number of arguments of
std::streamoff seal::Ciphertext::load
does not coincidence (The full error message at below). Would this be also related with the same issue which seems you are working on currently?Additionally, yesterday I found that you made some update on files related with SEAL a few days ago, so I made a pull and tried again. I'm attaching my new error message when running again the bridging tutorial with pulled version, since the content of message is changed from the previous(#14). It looks like that you are still working on the SEAL problem, but just in case, I wanted to let you know the updated error.
Any comments would be helpful for me!