Open amr-atsec opened 1 month ago
We can do that. For now, submit with 512 and send me an email with the EID so we can update it manually.
Thank you for the solution.
When I set the narrowest width to 512 bits, I get another error about the number of output bits of the conditioning component being smaller than the narrowest width.
In addition to setting the narrowest width to 512 bits, is it permissible to set the n_out and h_out to temporary (incorrect) values just so that the submission is possible? I can include the correct values of these parameters in the email so that you can update them manually.
I don't think nw
is allowed to be less than nOut
. Otherwise how would nOut
be smaller than the narrowest point of the conditioning component? It would be the narrowest width of the conditioning component.
Apologies, I mistyped. I meant to say that I get an error about the number of output bits of the conditioning component being greater than 512 bits. To bypass that error, I could set nOut to be 512. However, now hOut would be greater than nOut, so hOut would have to be adjusted to be less than or equal to nOut.
The ESV server limits the narrowest internal width of non-vetted conditioning components to 512 bits. When performing a demo register operation for a non-vetted component whose width is greater than 512 bits, this error is returned: "IntegerValueOutOfRangeError: nw is not between 1 and 512."
May you please lift the restriction on the narrowest internal width of non-vetted conditioning components?