| ID: | 3912 |
| From: | ge...@igor2.repo.hu |
| Date: | Sat, 4 Apr 2020 06:31:46 +0200 (CEST) |
| Subject: | [pcb-rnd] drc_query news and plans |
| replies: | 3913 from Britton Kerin <br...@gmail.com> |
Hi all, (if you ever run the DRC, this definitely affects you) new features since the last announcement: - you can run any drc rule individually, by hand, by clicking on the run button either on the drc rule list dialog (accessible from preferences drc via a button) or from the rule edit dialog (accessible from the rule list via the edit button) - you can edit any rule and interactively test how it performs and save the result. Note: like with some parts of the preferences dialog, if you use the GUI to save rules in your config, it will need to make a copy of the whole drc rule list; i.e. if you edit and save a drc rule in your design (board file), all drc rules will be saved in your board file. This is a GUI limitation. You can always edit your config (even within your board file) to make your drc rules inserted without having to copy the whole list. - after each drc_query rule execution, we save statistics; this includes the time spent on the last execution of the rule (floating point, in seconds) and total time spent on the rule in the current pcb-rnd session (so this is not reset by loading a new board!) - last execution time is listed as column 4 in the rule list, so opening the rule list after a drc run will give you a picture where time was spent - by now, I have the initial rewrite of all old drc rules as new drc_query scripts, so in theory disabling the old drc won't make you miss anything (except a large number of duplicate reports) Plans for the transition: - I ask everyone to test the new drc as much as possible; trunk is considered stable now; I am still working heavily on the new drc code, but the core, the important part is there and should be stable - I will disable the new drc in the default config before the release, so our next release will have the old drc enabled by default and the user will be able to enable the new drc (and disable the old). Rationale: we did not yet have enough time to test the new drc - I will swap that in trunk right after the release: I will disable the old drc and enable the new drc; I will probably mark the whole old drc plugin disabled, which means you will be able to test it only if you explicitly request it be compiled ./configure time; this gives our production users a final fallback but also helps us transitioning to the new drc_query plugin - later this year I will remove the old drc plugin (drc_orig) from the code base Best regards, Igor2
Reply subtree:
3912 [pcb-rnd] drc_query news and plans from ge...@igor2.repo.hu
3913 Re: [pcb-rnd] drc_query news and plans from Britton Kerin <br...@gmail.com>
3914 Re: [pcb-rnd] drc_query news and plans from ge...@igor2.repo.hu