options and type_options are not propagated from covergroups/coverpoints

[BanuAdrian]

I have found that PyVSC currently does not provide a method for querying overall coverage across all covergroups, which is essential for automation. When attempting to implement an external solution, I realized that the correct calculation for overall coverage depends critically on covergroup/coverpoint options such as weight and per_instance, as well as whether they are set via options or type_options.

The documentation states that some options (like weight or per_instance) are not respected or might be ignored at the covergroup level, but it is unclear which options are actually used at run-time and how they propagate to coverage models and type models for coverpoints and covergroups.

Questions:

1. What is the current implementation status of options and type_options for covergroups and coverpoints? When are you going to implement these?
2. Which options (weight, per_instance, at_least, etc.) are respected at both instance and type levels during coverage calculation and reporting?

Justification:

• I need to correctly calculate overall coverage, and automate stopping tests on 100% coverage. For this, options like weight and per_instance are critical, but current behavior is ambiguous.

Thank you!

[mballance]

Thanks for raising this, since it had slipped my mind a bit that this was an outstanding gap in the implementation. I had a look, and it does appear that these options are currently ignored.
From the note above, it appears that supporting options and type_options on covergroups are sufficient to meet your needs. If not, please describe what support your application requires for coverpoint-level options.

It sounds like you're using the get_coverage/get_inst_coverage methods to check coverage on-the-fly, so we can focus on those for now.

I'll do some investigation and get back with an update

Thanks!