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

Association Tree Planning #55

Open
rahlk opened this issue Feb 27, 2019 · 0 comments
Open

Association Tree Planning #55

rahlk opened this issue Feb 27, 2019 · 0 comments

Comments

@rahlk
Copy link
Contributor

rahlk commented Feb 27, 2019

Generating Plans with Assoc. Rule + XTREE + Random Walk

Reviewers comment on causality

The majority of the reviewers do not agree with the key underlying assumption that there is a causal relationship between metrics and defects. In defect prediction we always rely on correlations and pretty much never claim causality (the majority of reviewers stand fairly strong grounds on this point).

Newer XTREE

Goal: Use previous changes to guide search

  1. Mine association rule using FP-Growth
  2. Build XTREE (as usual)
  3. Perform a random walk on the tree to (a) maximize overlap of change, and (b) minimize defects

image

Ant

ant_v1
ant_v2
image

Camel

camel_v1
camel_v2

Ivy

ivy_v1

Jedit

jedit_v1
jedit_v2
jedit_v3

Log4j

log4j_v1

Lucene

lucene_v1

Poi

poi_v1
poi_v2

Velocity

velocity_v1

Xalan

xalan_v1
xalan_v2

Xerces

xerces_v1
xerces_v2

General Review Comments

Reviewers also point out some other issues that require attention, which I hope would be useful for future revisions of this paper:

  1. The paper needs to be positioned as a new planning approach (R2).

  2. A discussion on why the proposed approach is better as compared to existing approach is needed (R2).

  3. A more clear justification on why we are going back to product metrics is needed (R2), especially in the context of recent related work.

  4. The description of the approach lacks details (R1).

  5. The small-scale study needs to be justified (R1).

  6. The dataset used could be potentially biased (see R1, R3).

  7. Better Evaluation Metric (R2)

  8. Correlation (not causation).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant