Register
Login
Resources
Docs Blog Datasets Glossary Case Studies Tutorials & Webinars
Product
Data Engine LLMs Platform Enterprise
Pricing Explore
Connect to our Discord channel
Integration:  git github
Hlib 3dfd3537b9
Remove more from gdrive and at the end (#189)
3 years ago
06413c0379
Upgrade/bohr 0.4.4 (#172)
3 years ago
21143620e2
remove ironspeed remote from dvc config
3 years ago
3dfd3537b9
Remove more from gdrive and at the end (#189)
3 years ago
64a4060e7a
Add transformer (#148)
3 years ago
bin
f71b6f3631
upgrade to bohr 0.4.7 (#185)
3 years ago
f71b6f3631
upgrade to bohr 0.4.7 (#185)
3 years ago
ba2412cbf0
Upgrade/bohr 0.4.3 (#169)
3 years ago
dc6ddec90f
Fix smells pre-processing script (#93)
3 years ago
76c09e2408
upgrade bohr to 0.3.9 (#162)
3 years ago
doc
ca4ad4c06f
doc images and gifs
3 years ago
4ff89d92d1
update outdated hashsum of smell-madeyski.csv.dvc after it is shown as chnaged (not sure why?)
3 years ago
eea4739bdb
update to bohr 0.4.5: specify keywords in the heuristic decorators (#176)
3 years ago
f71b6f3631
upgrade to bohr 0.4.7 (#185)
3 years ago
f71b6f3631
upgrade to bohr 0.4.7 (#185)
3 years ago
f71b6f3631
upgrade to bohr 0.4.7 (#185)
3 years ago
c4d5fe473d
freeze transformer stages
3 years ago
eea4739bdb
update to bohr 0.4.5: specify keywords in the heuristic decorators (#176)
3 years ago
64a4060e7a
Add transformer (#148)
3 years ago
cd001e03fe
add setup-bohr script
3 years ago
f2b487f68f
WIP #76: restructure the repo into framework and other (#90)
3 years ago
3dfd3537b9
Remove more from gdrive and at the end (#189)
3 years ago
4cc932160e
add dvc pre-commit hooks
3 years ago
8dd7c80d2e
Pylint - black compatibility (#80)
3 years ago
5cbb8ede96
Fix reproduce action (#113)
3 years ago
7f11f72192
use setup-bohr script for travis build
3 years ago
b28a1b48f2
add license (#118)
3 years ago
4d929c5d7a
Update README.rst
3 years ago
f71b6f3631
upgrade to bohr 0.4.7 (#185)
3 years ago
f71b6f3631
upgrade to bohr 0.4.7 (#185)
3 years ago
3dfd3537b9
Remove more from gdrive and at the end (#189)
3 years ago
f71b6f3631
upgrade to bohr 0.4.7 (#185)
3 years ago
f71b6f3631
upgrade to bohr 0.4.7 (#185)
3 years ago
1c13682e5a
Add renovate.json
3 years ago
f0a84ba0d2
Add pylint and fix some warnings (#78)
3 years ago
64a4060e7a
Add transformer (#148)
3 years ago
Storage Buckets
Data Pipeline
Legend
DVC Managed File
Git Managed File
Metric
Stage File
External File

README.rst

You have to be logged in to leave a comment. Sign In
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
  1. BOHR (Big Old Heuristic Repository)
  2. ----------------------------------
  3. BOHR is a **repository of heuristics** for categorization of software engineering artifacts, e.g. commits, bug reports, etc.
  4. Categorization of artifacts is often required to create ground-truth datasets to train machine learning models on. For example, to train a model that classifies commits as "feature", "bugfix", or "refactoring", one needs to have a dataset of commits with these labels assigned.
  5. Since creating a large dataset manually is expensive, the alternative is to come up with "heuristics", short programs that can assign noisy labels to artifacts automatically. Implementing **a large number of such heuristics** and **combining their outputs** "smartly" is the idea behind `snorkel <https://www.snorkel.org/>`_, the state-of-the-art `weak supervision <http://ai.stanford.edu/blog/weak-supervision/>`_ tool.
  6. BOHR is a wrapper around snorkel which:
  7. * **Simplifies** the process of **adding new heuristics** and **evaluating their effectiveness**;
  8. * **Labels the datasets** registered with BOHR and **automatically updates the labels** once heuristics are added;
  9. * Keeps track of heursitics used for each version of generated datasets and models, and, in general, makes sure they are **reproducible** and **easily accessable** by using `DVC <https://dvc.org>`_.
  10. .. contents:: **Contents**
  11. :backlinks: none
  12. How do heuristics look like?
  13. ===================================
  14. .. code-block:: python
  15. # other imports
  16. ...
  17. from bohr.core import Heuristic
  18. from bohr.collection.artifacts import Commit
  19. from bohr.labels import CommitLabel
  20. @Heuristic(Commit)
  21. def bugless_if_many_files_changes(commit: Commit) -> Optional[Labels]:
  22. if len(commit.files) > 6:
  23. return CommitLabel.NonBugFix
  24. else:
  25. return None
  26. Important things to note:
  27. #. A heuristics is marked with the ``Heuristic`` decorator, and the artifact type to which it is applied is passed to it as a parameter;
  28. #. The artifact instance is exposed to the heuristic as a function parameter; the properties of the artifact object can be used to implement the logic;
  29. #. For the label to be assigned to the artifact, it has to be returned from the function; the heuristic must assign one of the labels defined in the BOHR label hierarchy or ``None`` if it abstains on the data point.
  30. BOHR usage scenarios
  31. ===================================
  32. 1. Only using existing heuristics
  33. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  34. Heuristics already implemented in BOHR are used to train label models, which are continuosly improved as more heuristics are added. The label models are used then to label the datasets that been added to BOHR. These datasets can be easily accesed and used as tehy are. Moreover, you can use the label models to label your own datasets.
  35. 2. Implementing new heuristics for existing tasks
  36. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  37. If you want to work on already defined tasks, you can add more heuristics to improve the label model and the datasets further. Once new heuristics are implemented, they can be submitted as a pull request to BOHR, which will automatically re-run the pipiline - re-train the label model, re-label the datasets, and calculate new metrics. The pull request will be accepted if the metrics are improved.
  38. 3. Implementing heuristics for new tasks and artifacts
  39. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  40. BOHR is designed to be extensible. You can esily define new artifact classes and tasks, and start implementing heuristics for those tasks. Note that some heuristics already added for other tasks might be reused for a new task. Please refer to the documentation for more details.
  41. Overview of BOHR abstractions
  42. ================================
  43. .. raw:: html
  44. <img src="doc/bohr_abstractions.png" width="600px">
  45. Quick Start
  46. ============
  47. Installation
  48. ~~~~~~~~~~~~~
  49. Python >= 3.8 is required, use of virtual environment is strongly recommended.
  50. #. Run ``git clone https://github.com/giganticode/bohr && cd bohr``
  51. #. Install BOHR framework library: ``bin/setup-bohr.sh``. This will install `bohr-framework <https://github.com/giganticode/bohr-framework>`_, dependencies and tools to run heursistics.
  52. Important commands
  53. ~~~~~~~~~~~~~~~~~~~
  54. +-----------------------------------+-------------------------------------------------------------------+
  55. | | Command |
  56. +===================================+===================================================================+
  57. | Pull existing labeled dataset | | ``$ bohr pull bugginess 200k-commits`` |
  58. +-----------------------------------+-------------------------------------------------------------------+
  59. | Label your dataset | | ``$ bohr dataset add ~/new_commit_dataset.csv -t commit`` |
  60. | | | ``$ bohr task add-dataset bugginess new_commit_dataset --repro``|
  61. +-----------------------------------+-------------------------------------------------------------------+
  62. | Add heuristic(s), re-train | | ``$ vi heuristics/commit_files.py`` |
  63. | label model, and update labels | | ``$ bohr repro bugginess`` |
  64. +-----------------------------------+-------------------------------------------------------------------+
  65. | Add a new task | | ``$ bohr task add tangled-commits \`` |
  66. | | | ``... -l TangledCommit.NonTangled,TangledCommit.Tangled \`` |
  67. | | | ``... --repro`` |
  68. | | | |
  69. +-----------------------------------+-------------------------------------------------------------------+
  70. Contribute to the framework
  71. =============================
  72. To contribute to the framework, please refer to the documentation in the the `bohr-framework <https://github.com/giganticode/bohr-framework>`_ repo.
  73. Pre-prints and publications
  74. =============================
  75. .. code-block::
  76. @misc{babii2021mining,
  77. title={Mining Software Repositories with a Collaborative Heuristic Repository},
  78. author={Hlib Babii and Julian Aron Prenner and Laurin Stricker and Anjan Karmakar and Andrea Janes and Romain Robbes},
  79. year={2021},
  80. eprint={2103.01722},
  81. archivePrefix={arXiv},
  82. primaryClass={cs.SE}
  83. }
Tip!

Press p or to see the previous file or, n or to see the next file

About

Big Old Heuristic Repository

Collaborators 1

Comments

Loading...