|
2 | 2 | # Visit https://bit.ly/cffinit to generate yours today!
|
3 | 3 |
|
4 | 4 | cff-version: 1.2.0
|
5 |
| -title: >- |
6 |
| - Improving the Learnability of Machine Learning APIs |
7 |
| - by Semi-Automated API Wrapping |
8 |
| -message: Please cite this software using these metadata. |
9 |
| -type: conference-paper |
10 |
| -authors: |
11 |
| - - given-names: Lars |
12 |
| - family-names: Reimann |
13 |
| - |
14 |
| - affiliation: >- |
15 |
| - Institute for Computer Science III, University |
16 |
| - of Bonn, Germany |
17 |
| - orcid: 'https://orcid.org/0000-0002-5129-3902' |
18 |
| - - affiliation: >- |
19 |
| - Institute for Computer Science III, University |
20 |
| - of Bonn, Germany |
21 |
| - given-names: Günter |
22 |
| - family-names: Kniesel-Wünsche |
23 |
| -identifiers: |
24 |
| - - type: doi |
25 |
| - value: 10.1109/ICSE-NIER55298.2022.9793507 |
26 |
| - description: IEEE Xplore |
27 |
| - - type: doi |
28 |
| - value: 10.48550/arXiv.2203.15491 |
29 |
| - description: arXiv (preprint) |
30 |
| -repository-code: 'https://github.com/lars-reimann/api-editor' |
31 |
| -abstract: >- |
32 |
| - A major hurdle for students and professional |
33 |
| - software developers who want to enter the world of |
34 |
| - machine learning (ML), is mastering not just the |
35 |
| - scientific background but also the available ML |
36 |
| - APIs, Therefore, we address the challenge of |
37 |
| - creating APIs that are easy to learn and use, |
38 |
| - especially by novices. However, it is not clear how |
39 |
| - this can be achieved without compromising |
40 |
| - expressiveness. We investigate this problem for |
41 |
| - scikit-learn, a widely used ML API. In this paper, |
42 |
| - we analyze its use by the Kaggle community, |
43 |
| - identifying unused and apparently useless parts of |
44 |
| - the API that can be eliminated without affecting |
45 |
| - client programs. In addition, we discuss usability |
46 |
| - issues in the remaining parts, propose related |
47 |
| - design improvements and show how they can be |
48 |
| - implemented by semi-automated wrapping of the |
49 |
| - existing third-party API. |
50 |
| -keywords: |
51 |
| - - >- |
52 |
| - APIs , libraries , usability , learnability , |
53 |
| - machine learning |
| 5 | +message: >- |
| 6 | + Please cite this software using the metadata from |
| 7 | + 'preferred-citation'. |
| 8 | +type: software |
| 9 | +title: API-Editor |
| 10 | +repository-code: https://github.com/lars-reimann/api-editor |
| 11 | +preferred-citation: |
| 12 | + type: conference-paper |
| 13 | + title: >- |
| 14 | + Improving the Learnability of Machine Learning APIs |
| 15 | + by Semi-Automated API Wrapping |
| 16 | + authors: |
| 17 | + - given-names: Lars |
| 18 | + family-names: Reimann |
| 19 | + |
| 20 | + affiliation: >- |
| 21 | + Institute for Computer Science III, University |
| 22 | + of Bonn, Germany |
| 23 | + orcid: 'https://orcid.org/0000-0002-5129-3902' |
| 24 | + - affiliation: >- |
| 25 | + Institute for Computer Science III, University |
| 26 | + of Bonn, Germany |
| 27 | + given-names: Günter |
| 28 | + family-names: Kniesel-Wünsche |
| 29 | + identifiers: |
| 30 | + - type: doi |
| 31 | + value: 10.1109/ICSE-NIER55298.2022.9793507 |
| 32 | + description: IEEE Xplore |
| 33 | + - type: doi |
| 34 | + value: 10.48550/arXiv.2203.15491 |
| 35 | + description: arXiv (preprint) |
| 36 | + abstract: >- |
| 37 | + A major hurdle for students and professional |
| 38 | + software developers who want to enter the world of |
| 39 | + machine learning (ML), is mastering not just the |
| 40 | + scientific background but also the available ML |
| 41 | + APIs, Therefore, we address the challenge of |
| 42 | + creating APIs that are easy to learn and use, |
| 43 | + especially by novices. However, it is not clear how |
| 44 | + this can be achieved without compromising |
| 45 | + expressiveness. We investigate this problem for |
| 46 | + scikit-learn, a widely used ML API. In this paper, |
| 47 | + we analyze its use by the Kaggle community, |
| 48 | + identifying unused and apparently useless parts of |
| 49 | + the API that can be eliminated without affecting |
| 50 | + client programs. In addition, we discuss usability |
| 51 | + issues in the remaining parts, propose related |
| 52 | + design improvements and show how they can be |
| 53 | + implemented by semi-automated wrapping of the |
| 54 | + existing third-party API. |
| 55 | + keywords: |
| 56 | + - >- |
| 57 | + APIs , libraries , usability , learnability , |
| 58 | + machine learning |
0 commit comments