- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It seems like every time I make a change to a schematic, the .cysch.cyvis file gets a raft of meaningless tweaks to component locations at the same time for no reason:
These clutter up the git history and make it hard to find the actual meaningful changes. Can this behavior be fixed?
(I don't understand why these are even saved as floats when the wires and components are always snapped to a grid.)
Solved! Go to Solution.
- Labels:
-
PSoC Creator & Designer Software
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @JoBr_1593366 ,
Thank you for pointing this out. Even though the schematic is the same, the way the floats are being calculated is causing this and since it has upto 4 decimals of accuracy (a good thing and a bad thing), the number calculaṭed seems to be minorly different each time. I have passed this on to the software team for evaluation.
Regards,
Dheeraj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
JoBr,
It makes sense that the TopDesign.cysch gets updated when a schematic change occurs. There is no way to avoid even minute changes like you mention.
The .cyvis file you mention: I don't see it in any of my designs. Where do you find it in yours?
If it is not necessary in a design, you can ignore/exclude it from the git archive.
"Engineering is an Art. The Art of Compromise."
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
These files are generated when you turn on "Generate Description Files" for the project. They allow you to see what has changed in the git history (since diffs of binary cysch files are useless for this).
There's no reason why the locations and widths of every component should change by small fractions just because, for instance, I renamed one of them, or disabled one of them, without changing the position of anything, but that's what it does. Seems like a flaw in the way the schematic is stored?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
JoBr,
I guess I never needed to "Generate Description Files".
Small changes in the locations and widths on a minor schematic change: Is it a bug or a feature(?) Don't know.
"Engineering is an Art. The Art of Compromise."
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
where that "Generate Description Files" option is located? I can't find it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Right-click the project name in Workspace Explorer, go to Properties..., then Generate Description Files to True
It generates plain text versions of the schematic's visual (.cysch.cyvis) and functional (.cysch.cysem) layout. I use them to see changes in git or to do diffs between different schematics, etc. but it doesn't work great because of problems like this. It also randomly reorders things, which adds noise to diffs for no change.
I'm not sure if it's possible to convert the plain text files back into a binary schematic file.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you for info. In which folder should I look for the output file? - Can't find it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You have to modify the schematic and save it to generate the first one. You can then undo the modification and save it again. (Another quirk of these files that I don't like.) Then they will be in the same folder as the .cysch.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @JoBr_1593366 ,
Thank you for pointing this out. Even though the schematic is the same, the way the floats are being calculated is causing this and since it has upto 4 decimals of accuracy (a good thing and a bad thing), the number calculaṭed seems to be minorly different each time. I have passed this on to the software team for evaluation.
Regards,
Dheeraj