Release of FFT Fixed point (bit accurate) model to pypi #53
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Owner
|
@mschiller-nrao Sorry for only getting to this now - are you able to patch the Python errors that prevent all the FFT tests from passing? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I need to use the Fixed point FFT model in a higher level model. The most straightforward way to do that was to clean up the fixed point python model I wrote a year ago so it could be released to pypi as casper-r2sdf-fft
This has a ripple effect on our own testbenches, as we need to pip install it, as well as I split out VUNIT related stuff from the "raw" bit-accurate model.
This also includes some changes to xpm_vhdl that I made to make Sigasi happier...