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

[visualization] Issues related to metrics visualization #13

Closed
inishchith opened this issue Jun 24, 2019 · 1 comment
Closed

[visualization] Issues related to metrics visualization #13

inishchith opened this issue Jun 24, 2019 · 1 comment
Labels
coding-period-two task completed during coding period #2

Comments

@inishchith
Copy link
Owner

Context:

Our initial idea of implementing metrics(total lines of code and others) was to create a bucket of items containing analysis data of all the files available at a point of time, pick the latest change (in a file) and perform some sort of an aggregation.
For example, CoCom backend executed at a file level would produce results (ccn, loc, blanks, and others) for files affected in a commit, we decided to insert an item per file in the enrich index.
But it wouldn't be possible to visualize as bucketing would become complex and even in TimeLion(split) I couldn't find enough references fo our use case. This led us to think of the repository analysis (as a category for analyzer).

We could perform some metrics visualization with the help of the repository level analysis
(Ref.#11) except for evolution related.

The issue with repository-level analysis in case of implementing evolution metrics is that,
So for example, I have 129 files in my repository (today) and X commits were made today. This leads to the creation of 129 * X items in for a given time and this may lead to problems. such as

  1. Information related to files affected in a commit are lost and hence a change cannot be tracked down to a file.
  2. Memory issues.
@inishchith
Copy link
Owner Author

The issue is addressed in Coding Period 2 and is being looked after in extension with #12

@inishchith inishchith added this to the 📈 Second Evaluation milestone Jul 17, 2019
@inishchith inishchith added the coding-period-two task completed during coding period #2 label Jul 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
coding-period-two task completed during coding period #2
Projects
None yet
Development

No branches or pull requests

1 participant