![[PukiWiki]](image/wadanyan.png "[PukiWiki]")
#author("2018-09-14T06:22:06+09:00","","") #author("2019-01-21T19:15:22+09:00","","") [[論文英語単語帳/表現集]] ***リンク [#f20ebad6] #ls2(論文英語単語帳/) *** 表現集[#s089e92b] #ls2(論文英語単語帳/表現集/) *今からすることの説明 [#s6711721] **評価する [#cd19ed21] **結果を示す [#o13cab4a] ***suggest [#k4e2e932] -Our empirical evaluation suggests that our approach can learn useful API usage models which can provide recommendations with higher levels of accuracy than the baseline n-gram model. ***present [#a0587cb6] -In this section we present 8 findings of our empirical study, grouped by their relevance to research questions raised in Section 1. ***evaluate [#zaca4e41] -We evaluate SketchFix on the Defects4J benchmark [20], which consists of 357 real defects from 5 open source Java applications. -To evaluate our approach, we designed experiments to determine its effectiveness, running time, and the visual appeal of its solutions. **比較する [#y31a83b7] ***compare [#k98f06eb] - In Section4.2, we compare SketchFix’s repair efficacy and favored defect types with other automated repair techniques. -We compare Firefox work pattern with another Mozilla project: Firefox OS. **調査する [#f20550e8] ***investigate [#h7634a31] - In Section 4.3, we investigate if the on-demand candidate generation could effectively reduce the search space of repair candidates. -To investigate app crashes, we group their exception traces into three different categories according to their exception signalers. **計算する [#tdb45e38] ***compute [#l4fc803c] - First we computed the number of comments related to attached files for each day. ***conduct a survey [#ke0d2bb1] -To address RQ3, we conducted a user-based survey to evaluate the aesthetics and visual appeal of the repaired page. **分析する [#y3eadcc3] ***analyze [#v266d5ce] -In the first phase of this study we analyze a total of 64,445 merge scenarios from 422 Java projects from GitHub using Travis CI and Maven. **リサーチクエスチョンに取り組む [#d37cc5bd] ***address [#y93868a8] -We address the following research questions in this section: ***are [#fc41f047] -The specific research questions we considered were: ***seek to answer [#sb7b102e] -In our research experiment, we seek to answer following research questions ***特殊 [#wcc320d3] -Under our research questions that ask how the activity of joiners differs from that of non-joiners over the same time period, we construct a logistic regression with the aforementioned explanatory variables. **リサーチクエスチョンに回答する [#f04fad75] ***answer [#z1800b42] -In this section, we answer the first research question by comparing SketchFix’s repair efficacy with other repair techniques— Astor [35], Nopol [7], ACS [58] and HDRepair [25]. **この意図は [#g347fbff] ***intent [#cc0dee69] -The main intent of the study was to evaluate the effectiveness of the layout distortion metric, L (Section 3.3), in minimizing layout disruptions and producing attractive pages. *値の説明 [#v941ec69] **であることを示している [#v9dffdad] ***indicate [#wbbe7921] -This might indicate that developers tend to be more direct and focus on what’s the most important when working outside the regular work pattern. ***inform [#edfa66c1] -Despite being a fairly expected phenomenon, it informs us that software obfuscation at this point is still not a general interest to mobile development. ***show [#pcbade00] -These results show that our approach was effective in identifying patches that could reduce the amount of distortion in a solution that was able to pass the mobile friendly test. ***imply [#ic7ad5cd] -This implies little opportunity to vary placement outside of our convention, similar to our motivating example in Figure 1a. **であった [#ff29a5f8] ***found [#s21149aa] -We found that in contrast to the distribution of all apps in App Store regarding their categories, the distribution of obfuscated apps has a vastly different pattern. This pattern varies further when the impact of third-party libraries is considered. -Based on our analysis, we found two dominant reasons that applied to all of the nine subjects. ***is [#ufb11eeb] -In our data, the maximum number of possible correct locations across all 31 fixing patches for resource/memory leaks is 3, while the average is 1.7. ***see [#p73fe62d] -We can see that for the fixable build failures, HireBuild fixed them with time comparable to manual fixes. **発生している/があった [#e093711b] -occur [#i585120f] --Resource leaks often occur when a function returns prematurely due to an error [6, 59]. -there are [#z6d606fe] --Moreover, there are 282 merge scenarios containing EditSameMC instances associated with conflicts. -be observed [#q73e4d6b] --A measure, readability of the repaired version was observed to be 62% of the time better than the original version. -yields --Not every environment yields equally reliable build results. **改善した [#c455955f] ***improve [#v7626b73] -On average, MFix improved the mobile friendliness score of a subject by 33% Overall, these results show that our approach was able to consistently improve a subject’s mobile friendliness score. -On average, the readability rating of the repaired pages showed a 17% improvement over original versions (original = 5.97, repaired = 6.98). ***improvement[#ua8e234c] -improvement is --Figures 5a and 5c show that the AUC improvement gained by adding the most recent three-month period to the long-period models of both studied systems is -1–2 percentage points. -observe improvements --We observe improvements in the predictive power of our QT models when they are tested in both the three-month and six-month settings. ***higer [#v911ba22] -In fact, overall, our repaired versions were rated slightly higher than original versions for attractiveness (avg. original = 6.50, avg. repaired = 6.67 and median original = 6.02, median repaired = 7.12). **と説明できる（考えられる） [#l0114655] -be explained by --Overall, the steady drop in build failure ratio can (at least partially) be explained by a strong increase in number of builds per release, -identify with --Build inflation seems to correspond to differences/similarities in OSes/environments, which can identify clusters of Perl versions/OSes with different failure ratio and value. **傾向がある [#o5126e56] -have a trend --However, as the regression line in Figure 3 shows, the overall build failure ratio has a strong decreasing trend between 2011 and 2016, especially when taking into account the logarithmic scale used in the figure. **のケースと一致する [#cc97af2c] -case -- These correspond to cases where an API is removed from a Perl version before being added again, or where the implementation of a given API changed behavior. **では， [#v184e30b] ***for [#x83bc79d] -For null dereferences, checks may plausibly be placed anywhere between the point at which an object becomes null and its dereference. **低い [#kbbc1322] -low [#e5309d31] --The percentage of agreement for joy in the pilot study was the lowest, with 30.25±5% of the comments containing disagreement. -less [#w6936933] --However, all other emotions and cases had less disagreement than 19.25±5% (sadness in pilot study). --The jagged trend of the black line (percentage of builds) is surprising, suggesting that odd releases see substantially less builds than even ones. **下落 [#r144690c] -drop --Overall, the steady drop in build failure ratio can (at least partially) be explained by a strong increase in number of builds per release, i.e., strong increases in the number of builds and the number of releases per CPAN dist. **あがったりさがったり [#rffc8ad8] -jagged trend --The jagged trend of the black line (percentage of builds) is surprising, suggesting that odd releases see substantially less builds than even ones. **と異なり [#j414a409] -apart from --Unfortunately, apart from these lump numbers, not much more is known about the build failure ratio of projects, for example about how this ratio evolves over time. **と同様に [#rdb6f892] **結果をみると [#y5a8e82a] -moving on [#yb12d2d1] --Moving on with the analysis, we cross information about merge scenarios containing predictors associated with merge, build, and test conflicts. -based from [#v217f738] --Based from these observations, we identified the period from 8 am to 7 pm as the day and from 8 pm to 7 am as the night. -looking at --First of all, by looking at the data distribution, we filtered out CPAN dists with less than 10 build results and less than 5 versions. -look into --We looked into the correlations between size, -confirm --Having confirmed that the OO metrics, size metric and number of faults are all significantly correlated, and that some of these OO metrics can explain (to varying degrees of accuracy) variability in the number of faults, we turn our attention to investigate whether size plays a mediating role in the relationships between the OO metrics and the number of faults. -turn out our attention to --Having confirmed that the OO metrics, size metric and number of faults are all significantly correlated, and that some of these OO metrics can explain (to varying degrees of accuracy) variability in the number of faults, we turn our attention to investigate whether size plays a mediating role in the relationships between the OO metrics and the number of faults. -gauge --When gauging indirect effects, bootstrapping-based techniques have several advantages over other methods, including the casual- steps and Sobel tests. **〜では [#kdf31d64] -For --For an insignificant p-value, it indicates that there is no significant relationship between the OO metric and number of faults. There were instances when the overall interaction effect was significant but none of the conditional effects were significant. **そのうち [#ya67a784] -, with --A median of 13.5% of OS build vectors fails inconsistently, with a median of 71% of those having only a minority of OSes failing. Windows (30%) and to some extent Linux/Solaris (7%) figure the most amongst the failing OS minority. **説明できない [#l8ef4e98] -not be explained While an increasing number of releases is typical for today’s release engineering strategies [25], the increasing number of builds cannot be explained intuitively. -with no evidence of --Fan-out shows similar results, with no evidence of a mediation effect of size in the following systems: jEdit, Log4j, Lucene (2.2), Prop and Tomcat. *さらに詳細に分析 [#xcb2db51] **さらに理解するために [#zc9c1716] -To better understand these cases --To better understand these cases, we counted the number of trailing zeroes in this vector as a measure of the time (in terms of number of Perl versions) builds have been broken for a given OS. **なぜか [#w1183b6e] -We investigated the results to understand why two subjects did not pass the GMFT. The patched version of the first subject, gsmhosting, contained a content sizing problem. **原因 [#zce0ee6d] -This caused a cascading effect with any change introduced in the page, such as increasing font sizes or decreasing width to fit the viewport. **統計的に分析 [#o987aac3] -But during result analysis, we performed statistical analysis to find out the sizes of build-fix patches, and the difference in size between the patches our approach can correctly generate and the patches our approach cannot. **目視で確認 [#ncc4797e] we performed manual analysis to find out why our approach fails. We check whether the reason is related to generation of version numbers, dependency names, etc. *推測 [#n01b7d06] **と推測している [#o3b7ce3a] ***infer [#q4071c52] -We may infer that although developers working on security-sensitive business sectors do view malicious reverse engineering as a nonneglectable threat, the obfuscation applied to their works is mostly for protecting the information encapsulated in the apps rather than the design and implementation of the software. **たとえ〜でも，〜だろう [#facc5a2a] ***Even if [#w0250bcb] -Even if we find dependency based on misscompiled classes, that may not match with actual fixing. Example 10 shows such a dependency update where our approach failed to generate the dependency name. *まとめ [#g3db4af5] **リサーチクエスチョンのまとめ [#oee0c47e] -While some emotions obtain higher agreement than others, only love, joy and sadness obtained at least fair agreement. Although comments clearly contain emotions, raters agree the most on the absence of an emotion. Using more than two raters does not significantly change the results in terms of degree of agreement on emotions. -The 20 projects use seven ASCATs, and in 11 cases each project use one ASCAT only. ASCATs cause up to 6% of broken builds, and up to 97% of warned builds. **結果全体のまとめ [#gc8910de] ***であった [#k1e828bb] -Overall, these results indicate that MFix was very effective in generating repaired pages that (1) users preferred over the original version, (2) considered to be more readable, and (3) that did not suffer in terms of visual aesthetics. -Our inspection based on Infer’s bug reports revealed that the number of locations ranges from 1 to 30, which poses more variability for placement. -In summary, by the end of this study first phase, we select a total 45 projects containing at least one build or test conflict. ***うまく働いた [#xdc2e755] -Therefore, our approach mainly works in the cases where the number of statement changes is small (1 or 2), which is similar to other automatic repair tools. *その他 [#gd669818] **ソースコード例 [#ea18dd0b] -Figure 6 shows a snippet of the code in question. **紙面の制約で [#l9324eb7] -Due to limited space, we only list categories with significant relevance to the discussions in Finding A.2. It may cause confusion that a small number of apps or libraries do not employ symbol renaming. **Future works [#o267e03e] -These results motivate future work in techniques that can better handle these types of pages. **付録にまとめる [#j7dd2e6a] -For further information on our sample, we provide a complete subject list on our online appendix [1].
