WEKO3
アイテム
Comparing Execution Traces of Jupyter Notebook for Checking Correctness of Refactoring
http://hdl.handle.net/10061/0002000092
http://hdl.handle.net/10061/000200009243b8c4e7-8433-4bd4-97fd-cd65f077741a
| 名前 / ファイル | ライセンス | アクション |
|---|---|---|
fulltext (798 KB)
|
|
| アイテムタイプ | 会議発表論文 / Conference Paper(1) | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| 公開日 | 2024-01-09 | |||||||||
| タイトル | ||||||||||
| タイトル | Comparing Execution Traces of Jupyter Notebook for Checking Correctness of Refactoring | |||||||||
| 言語 | ||||||||||
| 言語 | eng | |||||||||
| キーワード | ||||||||||
| 主題Scheme | Other | |||||||||
| 主題 | Jupyter Notebook | |||||||||
| キーワード | ||||||||||
| 主題Scheme | Other | |||||||||
| 主題 | Extract Function Refactoring | |||||||||
| キーワード | ||||||||||
| 主題Scheme | Other | |||||||||
| 主題 | Python | |||||||||
| キーワード | ||||||||||
| 主題Scheme | Other | |||||||||
| 主題 | Execution Trace | |||||||||
| キーワード | ||||||||||
| 主題Scheme | Other | |||||||||
| 主題 | IPython | |||||||||
| キーワード | ||||||||||
| 主題Scheme | Other | |||||||||
| 主題 | Code Clone | |||||||||
| 資源タイプ | ||||||||||
| 資源タイプ | conference paper | |||||||||
| 著者 |
Sato, Fumiya
× Sato, Fumiya
× Ikegami, Ayano
× 石尾, 隆× 嶋利, 一真× 松本, 健一 |
|||||||||
| 抄録 | ||||||||||
| 内容記述タイプ | Abstract | |||||||||
| 内容記述 | Jupyter Notebook is a popular tool for writing data analysis programs. Prior work showed that Jupyter Notebook users often duplicate their python code to try their hypothesis quickly. While such code clones can be removed by Extract Function refactoring later, users have to check that the output of a notebook is unaffected by the refactoring. However, users may not be able to compare execution results of a notebook before and after refactoring because non-textual output in Jupyter Notebook are fragile; for example, each of executions produce non-identical graphical images even though they look the same. To address this issue, we propose a method to automatically compare API calls to execute a Jupyter Notebook in addition to the textual output, while ignoring non-textual output. Our key assumption is that the same API calls with the same parameters produce the same results even if their details are non-identical. To demonstrate the effectiveness of the approach, we implemented an automatic tool for Jupyter Notebook that extracts a function from code clones and automatically checks the correctness. Using the tool, we have extracted functions from 3,995 cells in 520 Jupyter Notebook files. 142 out of 520 Notebook files are executable. Our tool compared API calls to check the correctness for 88 Notebook files, while a simple textual comparison could check 22 Notebook files. | |||||||||
| 書誌情報 |
en : 2022 IEEE 16th International Workshop on Software Clones (IWSC) p. 62-68, 発行日 2022-12-14 |
|||||||||
| 会議情報 | ||||||||||
| 会議名 | 2022 IEEE 16th International Workshop on Software Clones (IWSC) | |||||||||
| 開始年 | 2022 | |||||||||
| 開始月 | 10 | |||||||||
| 開始日 | 2 | |||||||||
| 終了年 | 2022 | |||||||||
| 終了月 | 10 | |||||||||
| 終了日 | 2 | |||||||||
| 開催地 | Limassol | |||||||||
| 開催国 | CYP | |||||||||
| 出版者 | ||||||||||
| 出版者 | IEEE | |||||||||
| ISSN | ||||||||||
| 収録物識別子タイプ | EISSN | |||||||||
| 収録物識別子 | 2572-6587 | |||||||||
| 出版者版DOI | ||||||||||
| 関連タイプ | isVersionOf | |||||||||
| 識別子タイプ | DOI | |||||||||
| 関連識別子 | https://doi.org/10.1109/IWSC55060.2022.00019 | |||||||||
| 出版者版URI | ||||||||||
| 関連タイプ | isVersionOf | |||||||||
| 識別子タイプ | URI | |||||||||
| 関連識別子 | https://ieeexplore.ieee.org/document/9978248 | |||||||||
| 権利 | ||||||||||
| 権利情報 | $00A92022 IEEE. Personal use of this material is permitted. Permission from IEEE must be obtained for all other uses, in any current or future media, including reprinting/republishing this material for advertising or promotional purposes, creating new collective works, for resale or redistribution to servers or lists, or reuse of any copyrighted component of this work in other works. 出版社許諾条件により、本文は2024年12月14日以降に公開 | |||||||||
| 著者版フラグ | ||||||||||
| 出版タイプ | AM | |||||||||
