facebookresearch / torchbeast
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
cc
txt
clang-format
toml
proto
gitmodules
  • 13 extensions are included in analyses: py, cc, md, h, txt, gitignore, clang-format, toml, sh, proto, json, gitmodules, yaml
  • 4 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (4 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.

main2943 LOC (63%) 21 files
test1480 LOC (31%) 16 files
generated0 LOC (0%) 0 files
build and deployment0 LOC (0%) 0 files
other240 LOC (5%) 4 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
cc
proto
toml
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 21 files match defined criteria (2,943 lines of code, 100.0% vs. main code):
    • 12 *.py files (1,758 lines of code)
    • 4 *.cc files (726 lines of code)
    • 3 *.h files (408 lines of code)
    • 1 *.proto files (41 lines of code)
    • 1 *.toml files (10 lines of code)
  • " *.py" is biggest, containing 59.73% of code.
  • " *.toml" is smallest, containing 0.34% of code.


*.py1758 LOC (59%) 12 files
*.cc726 LOC (24%) 4 files
*.h408 LOC (13%) 3 files
*.proto41 LOC (1%) 1 files
*.toml10 LOC (<1%) 1 files
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
cc
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*/[Tt]ests/.*".
    • files with paths like ".*_test[.].*".
  • 16 files match defined criteria (1,480 lines of code, 50.3% vs. main code):
    • 13 *.py files (1,197 lines of code)
    • 2 *.cc files (260 lines of code)
    • 1 *.sh files (23 lines of code)
  • " *.py" is biggest, containing 80.88% of code.
  • " *.sh" is smallest, containing 1.55% of code.


*.py1197 LOC (80%) 13 files
*.cc260 LOC (17%) 2 files
*.sh23 LOC (1%) 1 files
Other Code
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]md".
    • files with paths like ".*[.]txt".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*/[.]gitignore".
  • 4 files match defined criteria (240 lines of code, 8.2% vs. main code). All matches are in *.md files.


*.md240 LOC (100%) 4 files
Analyzers
Info about analyzers used for source code examinations.
  • *.py files are analyzed with PythonAnalyzer:
    • 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
    • Basic heuristic dependency analysis
  • *.cc files are analyzed with CppAnalyzer:
    • 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
  • *.h files are analyzed with CppAnalyzer:
    • 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
  • *.proto 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
  • *.toml 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-25 19:45