#author("2018-09-14T06:31:51+09:00","","")
#author("2018-11-03T11:47:56+09:00","","")
[[論文英語単語帳/表現集/結果章]]
***リンク [#f20ebad6]
#ls2(論文英語単語帳/)
*** 表現集[#s089e92b]
#ls2(論文英語単語帳/表現集/)


*キャプション [#sdbf249c]
*分布 [#lf1d8e09]
**手法 [#ia5cec45]
***概要 [#heae9d52]
-Overview of our approach to study the differences in characteristics of security, performance and other bugs
**結果 [#q9e008f9]
***分布 [#lf1d8e09]
-Number of changes to ASCAT configurations.
-Distributions of the number of comments for Firefox OS by day of the week.
-Distribution of the number of comments for Firefox depending on the day of the week.
-Distribution of top 15 languages in our dataset
-Distribution of project sizes
*割合 [#o81387e2]
***割合 [#o81387e2]
-Percentage of base image types across top 25 images
-Percentage of usage of 15 most commonly used base images
-Percentage of checks activated at least once.
*時系列の遷移 [#y5315453]
***時系列の遷移 [#y5315453]
-Evolution of the number of comments for Firefox. Vertical gray lines represent major Firefox releases.
*ワードクラウド [#b5e1ff41]
***ワードクラウド [#b5e1ff41]
- Comparison wordcloud of comments posted during weekends and weekdays. Words on the bottom, in orange, have a higher probability to appear in comments during weekends than words on the top, in green, which have a higher probability to appear in comments during weekdays.

*汎用[#eaa82614]
**からわかるように [#d1bd410b]
*説明[#eaa82614]
**汎用 [#h85929d2]
***からわかるように [#d1bd410b]
-As seen in the figure
- As can be seen from the chart, finding the repair for the mobile friendly problems (phase 3) was the most time consuming, taking up almost 60% of the total time. 
- From Figure 5, we can see that build script fix generated by our approach takes minimum 2 minutes, maximum 305 minutes and median value of 44 minutes.
**から〜にかけて [#pd644a4f]
***から〜にかけて [#pd644a4f]
-From ~to~,
--From 2010 to 2014, each year two Perl versions were released, so we
investigated the evolution of failure in period of six months.
**では, [#ffb3b712]
***では, [#ffb3b712]
-From
--From the figure, we can see that for fixed build failures, the patch list has minimum size of 68 and maximum size of 2,245, while median is 486. For non-fixed build failures, patch list minimum, median and maximum are 8, 223 and 1,266 respectively, which are lower than fixable build failure’s patch list.
-For
--For 54.16% of evaluated build failures, our approach cannot generate build fix.
**すべての分布において [#e008db34]
***すべての分布において [#e008db34]
--Figure 4 shows the distribution of the number of builds, OSes, and environments across all dists.


*結果の例を示す [#u6f568ee]
**結果の例を示す [#u6f568ee]
-illustrate
--Shown as Figure 6, we illustrate the quality of the repairs generated by SketchFix using an example.
--Figure 2 illustrates the distribution of the median number of builds and the number of versions across all CPAN dists in our full data set (the number of dists within each quadrant is shown as well). 
-show
--Fig. 1 shows that comments are not evenly distributed over the days of the week. 

*棒グラフ [#a0fc30af]
**棒グラフでx軸ごとに違いを比較 [#sea12bd7]
**棒グラフ [#a0fc30af]
***棒グラフでx軸ごとに違いを比較 [#sea12bd7]
-Figure 3 shows the results of comparing the before and after median mobile friendliness scores for each subject. 
**棒グラフに引かれている横線を説明 [#r40fd33f]
***棒グラフに引かれている横線を説明 [#r40fd33f]
-The black horizontal line drawn at 80 indicates the value above which the GMFT considers a page to have passed the test and to be mobile friendly
**黒い線は [#eaaae328]
***黒い線は [#eaaae328]
-Black lines show the lower and upper thresholds that we determined for the median number of builds and number of versions for each dist.
**分布の違い [#d0b7d1a9]
***分布の違い [#d0b7d1a9]
-Figure 5 shows the differences between these distributions, leading to the following key observations
**プロポーション [#sf7e9798]
***プロポーション [#sf7e9798]
- For both systems we computed the proportion of daily comments made during the night, and the proportion of comments made during a weekend day compared to a weekday. 

**ログスケール [#ee73a776]
***ログスケール [#ee73a776]
-logarithmic scale
--especially when taking into account the logarithmic scale used in the figure.

*ヒートマップ [#rd0bac16]
**色のこさ [#i447b321]
**ヒートマップ [#rd0bac16]
***色のこさ [#i447b321]
-In Figure 5, the shade of a box indicates the performance value, where blue shades indicate strong performance, red shades indicate weak performance, and the palest (white) shade indicates the performance that a random guessing model would achieve (on average).

トップ   編集 差分 履歴 添付 複製 名前変更 リロード   新規 一覧 検索 最終更新   ヘルプ   最終更新のRSS