lievenlemiengre on views
Validated & fixed definitions w… (compare)
Paebbels on views
Added view implementations for … (compare)
Paebbels on views
Added a view implementation for… (compare)
Paebbels on views
Renamed package files to `*.pkg… (compare)
Paebbels on views
Added first implementation of l… (compare)
Paebbels on range-arithmetic
Added range arithmetic packages… (compare)
Paebbels on generic-list
Committed pending changes. (compare)
tmeissner on tbv2_associative_array
Add tests for dict with strings… (compare)
LarsAsplund on tbv7-event-object
Added more test cases (compare)
LarsAsplund on tbv7-event-object
Cleaning up Added more test cases (compare)
tmeissner on tbv2_associative_array
Some fixes to make generic dict… (compare)
Paebbels on master
Updated URL (compare)
Paebbels on math
Based math test cases on Python… Made stimuli generation adapt t… Merge pull request #3 from Lars… (compare)
February 1, 2020 10:31 PM
Maybe we need an "awesome-cosim" list ;)
@cmarqu, unfortunately, there seems to be (not) awesome duplication in this area too:
I believe there is not so much content to justify having so many different projects. VHDL would be a good neutral place to gather all of them, however, it might seem that SystemVerilog or cosim libs might not fit, because of the name. @Paebbels, what do you think? Can we rename awesome-vhdl to awesome-hdl, and let it be a more general index? Since each awesome list is a markdown file, we can have multiple lists in a single repo, instead of having everything mixed. Alternatively, we can let each project be a separate markdown file with a brief description and some tags. Then, we can build lists from those tags.
So the remaining question in my point of view is:
How to handle tools that touch multiple languages like VUnit?
Normally, such tools are then listed in multiple awesome lists.
My points are:
I don't want VHDL tools and libs be drowning between Verilog and System Verilog entries in a list
I understand this, and because VHDL is the main language in the repo (and the best :heart: otherwise), I think that the README should correspond to VHDL-only projects. Nonetheless, common tools, and resources for other languages can be kept in other files and referenced from the README.
I'm specifically thinking about yosys, nextpnr and formal verification ATM (ping @tmeissner). By looking at search engines, one would believe that synthesis and formal verification with open source tools needs to be done with SV; there are many more resources about it. However, in the last few months, GHDL allowed to use VHDL too. I believe that this content should have some place in an awesome-vhdl repo, even if is not production-ready yet. These are times of rapid evolution and we should try to let curious people find interesting prototypes to work on.
ghdl:
vhdl:
- simulator
- synthesizer
repo: https://github.com/ghdl/ghdl/
text: GHDL is a free VHDL simulator supporting VHDL-1987 to VHDL-2008.
vhdl:
- synthesizer:
- pure
- mixed
- simulator:
Now that we agree on having multiple lists. This is a prototype I did yesterday:
Precisely, each tool/project is describe in a separate file (https://github.com/eine/awesome-vhdl/tree/hdl/content/items). The frontmatter (YAML/TOML) can contain any number of custom fields of any type. It is possible to build multiple taxonomies. By default, "tags" and "categories" are enabled.
Now that we agree on having multiple lists. This is a prototype I did yesterday:
Precisely, each tool/project is describe in a separate file (https://github.com/eine/awesome-vhdl/tree/hdl/content/items). The frontmatter (YAML/TOML) can contain any number of custom fields of any type. It is possible to build multiple taxonomies. By default, "tags" and "categories" are enabled.
looks like a nice starte, we should have 10 more items to see how it looks and how navigation feels when lists become longer
https://github.com/HDL
for our new awesome list.
Maybe it should become some dynamic thing with a visualization like http://everynoise.com/, and you would define some "attraction factor" between projects. Like VUnit to VHDL: 8/10, VUnit to SV: 2/10. But I don't know - I never use such lists "awesome" directly. Maybe indirectly because search engines derive correlations from it.
@cmarqu, honestly, I would not know how to set those metrics, should I need to do it manually. For example, I understand why you said VUnit to SV 2/10, but I think that 5/10 or 7/10 would also be acceptable. It depends on what you pay attention to. The point with everynoise is that it is created algorithmically. I believe it would be interesting to do some data mining with the list of projects. GitHub's, GitLab's and Bitbucket's APIs provide quite a lot of data points, on top of git itself. It would be a matter of gathering all the data, creating a nice matrix, normalising and finding correlations. PCA/SVD can be used to find the proximity. Moreover, it'd be interesting to see how do clustering algorithms behave. Anyway, I believe that this is out of scope for now. First, we need a "database" that can be read programmatically (the proposed new awesome list format) and we need to fill it.
hdl
was now transfered to our control. We can now implement our awesome list at:
The GitHub organisation name
hdl
was now transfered to our control. We can now implement our awesome list at:
A very first version was uploaded. Any feedback is welcome. The categories, which fields to define for each resource, the layout of the site... anything is open for discussion.
pyVHDLModel
and can be grabbed directly from PyPI. It's a split from pyVHDLParser.