Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] Perform Data Analytics on Output Generated JSON #8

Open
gahan9 opened this issue Apr 13, 2023 · 1 comment
Open

[FEATURE] Perform Data Analytics on Output Generated JSON #8

gahan9 opened this issue Apr 13, 2023 · 1 comment
Labels
easy Considerably Easy task to perform enhancement New feature or request good first issue Good for newcomers hackathon Open.Intel hackathon hacktoberfest Participation in Hacktoberfest Event help wanted Extra attention is needed question Further information is requested

Comments

@gahan9
Copy link
Contributor

gahan9 commented Apr 13, 2023

Is your feature request related to a problem? Please describe.
Implement Analysis data based on the output JSON file to calculate i.e., Free space, Compression Ratio, comparing any two or more JSON file data to show difference

Describe the solution you'd like
Any kind of Dashboard view is sufficient enough which gives easy idea to perform firmware binary analysis.

@gahan9 gahan9 added enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed question Further information is requested hackathon Open.Intel hackathon labels Apr 13, 2023
@gahan9
Copy link
Contributor Author

gahan9 commented Apr 24, 2023

Queries -

  1. Free space of the firmware volume/FFS/Flash space is expected here ?
    • Yes (for Firmware Volume and FFS), So to be precise Free-space can be categorized as:
      1. Free Space within uncompressed section
      2. Free Space within compressed section [Compressed section have GUID defined in PI Specification] --- this section needs to be differed because free space before compression v/s after compression would not be the same.
    • According to Specification, the free space can be under FV, FFS or Section. However, FFS would be part of FV only so that is kind of contributes to overall Free Space to FV
  2. Compression ratio for each FV inside the FFS is expected here ?
    • Yes, it would be of data where amount of size data which is compressed and the GUID of compression algorithm
  3. comparing 2 or more JSON files to show the difference between FVs, Free space, compression ratio, etc. ? What more is expected here ?
    • Comparison could be on parameters described below (4).
  4. Firmware binary analysis should be on what parameters ?
    • That is up to implementation effort to bring possibilities for assessment, there can be any possibility for comparing number of sections, drivers, classifying available driver types, analyzing space consumption of space by type, etc...

shubhamk-intel added a commit to shubhamk-intel/xml-cli that referenced this issue Apr 27, 2023
Analysing JSON data from 2 different ROM images in the form of Pie chart and bar graph view of various parameters.

This implementation allows us to see comparative analysis of 2 binary files. With the help of pie chart and bar graphs, we can analyze various components of section types and file types.

Implementation for intel#8

Signed-off-by: Kumar, Shubham <shubham.k@intel.com>
@gahan9 gahan9 added hacktoberfest Participation in Hacktoberfest Event easy Considerably Easy task to perform labels Sep 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
easy Considerably Easy task to perform enhancement New feature or request good first issue Good for newcomers hackathon Open.Intel hackathon hacktoberfest Participation in Hacktoberfest Event help wanted Extra attention is needed question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant