fbsamples / oculus-networked-physics-sample
Source Code Overview

Analysis scope, overview of main, test, generated, deployment, build, and other code.

Source Code Analysis Scope
Files includes and excluded from analyses
meta
mat
shader
asset
prefab
aspx
plist
ini
txt
cginc
csproj
gitattributes
obj
  • 19 extensions are included in analyses: meta, cs, xml, mat, shader, asset, prefab, unity, aspx, plist, ini, txt, json, cginc, csproj, gitattributes, md, gitignore, obj
  • 4 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (2 files).
    • exclude files with path like ".*/git[-]history[.]txt" (Git history) (1 file).
    • exclude files with path like ".*/git[-][a-zA-Z0-9_]+[.]txt" (Git data exports for sokrates analyses) (0 files).
    • exclude files with path like ".*[.]txt" (Text files) (2 files).
Overview of Analyzed Files
Basic stats on analyzed files
Intro
For analysis purposes we separate files in scope into several categories: main, test, generated, deployment and build, and other.

  • The main category contains all manually created source code files that are being used in the production.
  • Files in the main category are used as input for other analyses: logical decomposition, concerns, duplication, file size, unit size, and conditional complexity.
  • Test source code files are used only for testing of the product. These files are normally not deployed to production.
  • Build and deployment source code files are used to configure or support build and deployment process.
  • Generated source code files are automatically generated files that have not been manually changed after generation.
  • While a source code folder may contain a number of files, we are primarily interested in the source code files that are being written and maintained by developers.
  • Files containing binaries, documentation, or third-party libraries, for instance, are excluded from analysis. The exception are third-party libraries that have been changed by developers.

main100481 LOC (28%) 222 files
test0 LOC (0%) 0 files
generated15255 LOC (4%) 435 files
build and deployment0 LOC (0%) 0 files
other237035 LOC (67%) 153 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
aspx
mat
prefab
shader
obj
cginc
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 222 files match defined criteria (100,481 lines of code, 100.0% vs. main code):
    • 5 *.unity files (57,377 lines of code)
    • 167 *.cs files (28,867 lines of code)
    • 6 *.aspx files (9,351 lines of code)
    • 20 *.mat files (1,900 lines of code)
    • 5 *.prefab files (1,664 lines of code)
    • 16 *.shader files (1,029 lines of code)
    • 1 *.obj files (158 lines of code)
    • 2 *.cginc files (135 lines of code)
  • " *.unity" is biggest, containing 57.1% of code.
  • " *.cginc" is smallest, containing 0.13% of code.


*.unity57377 LOC (57%) 5 files
*.cs28867 LOC (28%) 167 files
*.aspx9351 LOC (9%) 6 files
*.mat1900 LOC (1%) 20 files
*.prefab1664 LOC (1%) 5 files
*.shader1029 LOC (1%) 16 files
*.obj158 LOC (<1%) 1 files
*.cginc135 LOC (<1%) 2 files
Generated Code
Automatically generated files, not manually changed after generation.
meta
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]meta" AND any line of content like ".*fileFormatVersion[:] .*".
  • 435 files match defined criteria (15,255 lines of code, 15.2% vs. main code). All matches are in *.meta files.


*.meta15255 LOC (100%) 435 files
Other Code
ini
plist
meta
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]md".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]json".
    • files with paths like ".*[.]txt".
    • files with paths like ".*[.]ini".
    • files with paths like ".*[.]plist".
    • files with paths like ".*/LICENSE[.][a-z0-9]+".
    • files with paths like ".*[.](xml|xsd|robot|sql|pgsql|dashboard|profile|ipynb|raml|avsc|al)".
  • 153 files match defined criteria (237,035 lines of code, 235.9% vs. main code):
    • 142 *.xml files (196,286 lines of code)
    • 3 *.ini files (40,545 lines of code)
    • 5 *.plist files (170 lines of code)
    • 1 *.md files (22 lines of code)
    • 1 *.meta files (8 lines of code)
    • 1 *.json files (4 lines of code)
  • " *.xml" is biggest, containing 82.81% of code.
  • " *.json" is smallest, containing 0% of code.


*.xml196286 LOC (82%) 142 files
*.ini40545 LOC (17%) 3 files
*.plist170 LOC (<1%) 5 files
*.md22 LOC (<1%) 1 files
*.meta8 LOC (<1%) 1 files
*.json4 LOC (<1%) 1 files
Analyzers
Info about analyzers used for source code examinations.
  • *.unity files are analyzed with DefaultLanguageAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Basic code cleaning (empty lines removed for LOC calculations and duplication calculations)
    • No unit size analysis
    • No conditional complexity analysis
    • No dependency analysis
  • *.cs files are analyzed with CSharpAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • Unit size analysis
    • Conditional complexity analysis
    • Advanced heuristic dependency analysis (based on namespace heuristics)
  • *.aspx files are analyzed with HtmlAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • Unit size analysis
    • Conditional complexity analysis
    • Advanced heuristic dependency analysis
  • *.mat files are analyzed with DefaultLanguageAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Basic code cleaning (empty lines removed for LOC calculations and duplication calculations)
    • No unit size analysis
    • No conditional complexity analysis
    • No dependency analysis
  • *.prefab files are analyzed with DefaultLanguageAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Basic code cleaning (empty lines removed for LOC calculations and duplication calculations)
    • No unit size analysis
    • No conditional complexity analysis
    • No dependency analysis
  • *.shader files are analyzed with DefaultLanguageAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Basic code cleaning (empty lines removed for LOC calculations and duplication calculations)
    • No unit size analysis
    • No conditional complexity analysis
    • No dependency analysis
  • *.obj files are analyzed with DefaultLanguageAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Basic code cleaning (empty lines removed for LOC calculations and duplication calculations)
    • No unit size analysis
    • No conditional complexity analysis
    • No dependency analysis
  • *.cginc files are analyzed with DefaultLanguageAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Basic code cleaning (empty lines removed for LOC calculations and duplication calculations)
    • No unit size analysis
    • No conditional complexity analysis
    • No dependency analysis

2022-01-26 09:35