metroid120

I agree that this is where the implementation lives. It looks to me like OpenVAF uses an RC network for the implementation, which explains the attenuation. The challenge is that...

[Dockerfile.txt](https://github.com/pascalkuthe/OpenVAF/files/13713224/Dockerfile.txt) Hi, unfortunately, the documentation is very outdated. Nobody is actively working on the project right now - unfortunately. Still, the code works well, let me give you some guidance....

Right now nobody is working on further development, unfortunately.

I can confirm this issue, it likely is a bug that OpenVAF requires at least 1 model parameter, even if that is not required.

At the moment it is not clear when (and if) work will start again.

This is a very good question. After Googling a bit, it seems that there is no general legal consensus. GCC, which is in a similar situation has put the [GCC...

OpenVAF can only be built with llvm-15, this is known and stated in the Readme. For building, use the Docker container.

I did some investigations today. The line of code ` SP_S_delta1 = 1.0 / SP_S_delta0; \` in the PSP model seems to be critical somehow for the observed behavior.

Ok I now know where this comes from. There is a code structure that is repeated three times in the PSP code: ``` SP_S_delta0 = exp(SP_S_x0); \ SP_S_delta1 = 1.0...

Ok I leave it here, since above mentioned solution is a feasible workaround. Fundamentally the issue must be related to the derivative generation algorithm in OpenVAF. My guess is that...