Polyspace 2017b new features over 2016a

Hello Team,

Could you please share exact updates between in polyspace 2016a and 2017b .

In POlyspace 2017b both the code prover and bug finder has been combined

one more question what are the pre- requests for the polyspace 2017b

in Report geneartion how to export the results of the codeprover to excel for analysis

as we see only 3 options are available

Thank you for the support and answers

[Walter Roberson]

BugFinder https://www.mathworks.com/help/bugfinder/release-notes.html?rntext=&startrelease=R2016b&endrelease=R2017b&groupby=release&sortby=descending&searchHighlight=

Code Prover

https://www.mathworks.com/help/codeprover/release-notes.html?rntext=&startrelease=R2016b&endrelease=R2017b&groupby=release&sortby=descending&searchHighlight=

[Geetha S]

Hello Walter thanks for the response.

how can we genearate the report of excel from code prover results

[Walter Roberson]

https://www.mathworks.com/help/releases/R2016b/codeprover/ug/export-results-to-text-file.html

Excel level code to generate a useful / pleasant report is outside the scope of Answers.

[Alexandre De Barros]

The generation of excel file is no longer available.

As suggested by Walter Roberson, it is now recommanded to export the results.

The export format is tsv (tab separated value), and can then easily imported into Excel.

Best regards,

Alexandre

[Geetha S]

if it is exported to tsv the line number and cloumn number is not exported