You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,14 +21,15 @@ Ideally, changes are made according to the following process:
21
21
* Ensure that xrf tests succeed (run via `devtools::test()`)
22
22
* Submit a pull request (this can be done via github UI)
23
23
* Maintainers will provide a code review. Every substantive comment must be addressed before the PR is accepted.
24
-
* Any follow-on commits to the fork will be reflected in the PR
25
24
* Please bump version numbers (`major.minor.patch`) in `DESCRIPTION` according to the final change made
26
25
* major number for any substantial API or backwards incompatible changes
27
-
* minor number for any standard change not touching API or compatiility
26
+
* minor number for any standard change not touching API or compatibility
28
27
* patch number for any bug fixes
29
28
30
-
### Code style suggestions
31
-
No strict style at current, but please attempt to follow suit with the rest of the project. If in doubt, defer to [Wickham](http://r-pkgs.had.co.nz/r.html#style).
29
+
### Code style
30
+
31
+
We are informally using the tidy code style the [air](https://posit-dev.github.io/air/formatter.html) formatter.
32
+
Please [install](https://posit-dev.github.io/air/cli.html)`air` and run with `air format .` after making changes.
32
33
33
34
### Help with R package development
34
35
If you're new to R package development but want to develop on xrf, both of the following are great resources:
Copy file name to clipboardExpand all lines: README.md
+1-4Lines changed: 1 addition & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,15 +39,13 @@ The general algorithm follows:
39
39
* For a description of this algorithm, see [this document](https://github.com/holub008/snippets/blob/master/overlapped_hyperrectangles/overlapped_hyperrectangles.pdf)
40
40
41
41
### Comparison to alternatives
42
-
Several implementations of RuleFit are available for R: [pre](https://CRAN.R-project.org/package=pre), [horserule](https://CRAN.R-project.org/package=horserule), and [rulefit](https://github.com/gravesee/rulefit). xrf improves on some aspects of these by:
42
+
Several implementations of RuleFit are available for R: [pre](https://CRAN.R-project.org/package=pre), (once upon a time) [horserule](https://CRAN.R-project.org/package=horserule), and [rulefit](https://github.com/gravesee/rulefit). xrf improves on some aspects of these by:
43
43
* Usually building more accurate models at fixed number of parameters
44
44
* Usually building models faster
45
45
* Building models that predict for new factor-levels
46
46
* Providing a more concise and limited interface
47
47
* Tested & actively maintained for fewer bugs
48
48
49
-
On the last point, as of April 2019, the 'pre' and 'rulefit' packages fail to build a model on the census income example below due to bugs.
50
-
51
49
## Example
52
50
53
51
Here we predict whether an individual's income is greater than $50,000 using census data.
@@ -232,4 +230,3 @@ How slick is that! We have:
232
230
Effects are immediately available by doing a lookup in the exclusive rules. This is a great win for interpretability.
233
231
234
232
As mentioned above, this example is contrived in that it uses `depth=1` trees (i.e. conjunctions of size 1). As depth increases, interpretability can suffer regardless de-overlapping if the final ruleset is non-sparse. However, for certain problems, particularly small depth or sparse effects, de-overlapping can be a boon for interpretability.
0 commit comments