Skip to content

Commit

Permalink
Fixing formatting error that was messing up render with new kramdown …
Browse files Browse the repository at this point in the history
…markdown
  • Loading branch information
dapryor committed Feb 6, 2016
1 parent 47ebb0e commit 5c5f26d
Show file tree
Hide file tree
Showing 191 changed files with 13,083 additions and 13,092 deletions.
2 changes: 1 addition & 1 deletion _config.yml
@@ -1,4 +1,4 @@
# Site metadata
Site metadata
name: "OpenScience"
description: "Open Science for SE"

Expand Down
141 changes: 70 additions & 71 deletions repo/about/index.md
@@ -1,71 +1,70 @@
---
title: About
layout: repo-content
---

# About Us

**Steering Committee**

Who |Where |From |Contributors |Member since
------------|-----------------|---------|-----------------------------|---------------
Olga Baysal |Univ. of Montreal| Canada |Yaxin Cao |Dec. 14
Ayse Benar |Ryerson Univ. | Canada |Bora Çağlayan |Sept. 14
Tim Menzies |N.C. State | USA |Carter Pape, Mitch Rees-Jones|Sept. 15
Burak Turhan|Univ. of Oulu | Finland |Burak Turhan |Sept. 14

Membership of the PROMISE repo is by _invitation_ from the current committee.
Membership "costs" one grad student who can devote some time per month on maintenance to the current site.

**Volunteers**

The Open Science tera-PROMISE repository has been made possible and is maintained by the combined efforts of many people. Acknowledgements are due to the people listed below. See more on the [people page](/repo/people).

Current Curators | Previous Curators | Data Finders
-----------------|--------------------------|------------------
Tim Menzies | Mike Chapman (v0) | Behjat Slt
David Pryor | Justin DiStefano (v0) | George Mathew
| Jelber Sayyad (v1) | Amal Boukhdhir
| Tim Menzies (v2, v3, v4) | Ben Province
| Bora Caglayan (v3) | Wei Fu
| Zhimin He (v3) | Rahul Krishna
| Ekrem Kocaguneli (v3) | Davide Fucci
| Joe Krall (v3) | Shirin Akbari
| Fayola Peters (v3) | Vivek Nair
| Burak Turhan (v3) | Josh Rees-Jones
| Corbin Steele (v4) |
| Carter Pape (v4) |
| Mitch Rees-Jones (v4) |

This repository is an update to the older PROMISE repository of SE data.

Our goal is to be a long term storage facility for SE data.

Many researchers take the time to carefully host their data on their own web sites. But as people move through their career, those web sites can fade away and take away their data. Hopefully, using this repo, we can make conclusions in SE repeatable, and repeatable for a longer time.

This site has size restrctions (1TB, total) and we are chasing funds to change that (coming soon: peta-Promise?). That said, we are making progress. For example, this site can hold 500 times the data of the last version.

## History

This is version four of the Promise repository:

* **Version 0:** Initially, in 2002, NASA ran the Metrics Data Program (MDP) for static code measures collected from NASA projects.
* **Version 1:** In 2004, samples from MDP became the PROMISE v1.0 repository hosted at ottawa.ca. Founded by Tim Menzies and Jelber Sayyad, this repo was one of the first widely-used repositories of software engineering project data (mostly, static code attributes linked to defect and effort information). A key feature of the repository was that it was linked to an annual conference. Activity and contributions to the repository became linked to paper publication (both at the conference and at the seven journal special issues where the authors of best conference papers were invited to submit extended versions of their conference papers).
* **Version 2:** That site grew and in 2006 was moved to a web-site supported by a home-brew macro system at promisedata.org.
* **Version 3:** In 2008, after numerous security hacks, that site was moved to a more maintainable site at promisedata.googlecode.com. This third version was restricted in size to under 10GBs. Submissions to this repository and associated PROMISE conference grew to 2010. The PROMISE conference received (10,16,34,53) submissions in (2007,2008,2009,2010) which was an annual growth of (160,212,156). As of 2010, the repository was in widespread use (e.g. one study spent two hours on IEEE Explorer and found 73 papers that used the repository).
* **Version 4:** In 2014, with support from N.C. State, that site was upgraded to terabyte size. At the same time, a support discussion forum was created at [http://openscience.us/ssj](http://openscience.us/ssj).

### Credits

_Founders_: Tim Menzies, Jelber Sayyad

#### _Curators_:

(If we missed your name, please [email us](mailto:openscience.content@gmail.com) to add you in.)

+ _Version 0_ : Mike Chapman, Justin DiStefano
+ _Version 1_ : Jelber Sayyad
+ _Version 2_ : Tim Menzies
+ _Version 3_ : Bora Caglayan, Zhimin He, Ekrem Kocaguneli, Joe Krall, Tim Menzies, Fayola Peters, Burak Turhan
+ _Version 4_: Tim Menzies, Carter Pape, Corbin Steele, Mitch Rees-Jones, David Pryor

---
title: About
layout: repo-content
---

# About Us

**Steering Committee**

Who |Where |From |Contributors |Member since
------------|-----------------|---------|-----------------------------|---------------
Olga Baysal |Univ. of Montreal| Canada |Yaxin Cao |Dec. 14
Ayse Benar |Ryerson Univ. | Canada |Bora Çağlayan |Sept. 14
Tim Menzies |N.C. State | USA |Carter Pape, Mitch Rees-Jones|Sept. 15
Burak Turhan|Univ. of Oulu | Finland |Burak Turhan |Sept. 14

Membership of the PROMISE repo is by _invitation_ from the current committee.
Membership "costs" one grad student who can devote some time per month on maintenance to the current site.

**Volunteers**

The Open Science tera-PROMISE repository has been made possible and is maintained by the combined efforts of many people. Acknowledgements are due to the people listed below. See more on the [people page](/repo/people).

Current Curators | Previous Curators | Data Finders
-----------------|--------------------------|------------------
Tim Menzies | Mike Chapman (v0) | Behjat Slt
David Pryor | Justin DiStefano (v0) | George Mathew
| Jelber Sayyad (v1) | Amal Boukhdhir
| Tim Menzies (v2, v3, v4) | Ben Province
| Bora Caglayan (v3) | Wei Fu
| Zhimin He (v3) | Rahul Krishna
| Ekrem Kocaguneli (v3) | Davide Fucci
| Joe Krall (v3) | Shirin Akbari
| Fayola Peters (v3) | Vivek Nair
| Burak Turhan (v3) | Josh Rees-Jones
| Corbin Steele (v4) |
| Carter Pape (v4) |
| Mitch Rees-Jones (v4) |

This repository is an update to the older PROMISE repository of SE data.

Our goal is to be a long term storage facility for SE data.

Many researchers take the time to carefully host their data on their own web sites. But as people move through their career, those web sites can fade away and take away their data. Hopefully, using this repo, we can make conclusions in SE repeatable, and repeatable for a longer time.

This site has size restrctions (1TB, total) and we are chasing funds to change that (coming soon: peta-Promise?). That said, we are making progress. For example, this site can hold 500 times the data of the last version.

## History

This is version four of the Promise repository:

* **Version 0:** Initially, in 2002, NASA ran the Metrics Data Program (MDP) for static code measures collected from NASA projects.
* **Version 1:** In 2004, samples from MDP became the PROMISE v1.0 repository hosted at ottawa.ca. Founded by Tim Menzies and Jelber Sayyad, this repo was one of the first widely-used repositories of software engineering project data (mostly, static code attributes linked to defect and effort information). A key feature of the repository was that it was linked to an annual conference. Activity and contributions to the repository became linked to paper publication (both at the conference and at the seven journal special issues where the authors of best conference papers were invited to submit extended versions of their conference papers).
* **Version 2:** That site grew and in 2006 was moved to a web-site supported by a home-brew macro system at promisedata.org.
* **Version 3:** In 2008, after numerous security hacks, that site was moved to a more maintainable site at promisedata.googlecode.com. This third version was restricted in size to under 10GBs. Submissions to this repository and associated PROMISE conference grew to 2010. The PROMISE conference received (10,16,34,53) submissions in (2007,2008,2009,2010) which was an annual growth of (160,212,156). As of 2010, the repository was in widespread use (e.g. one study spent two hours on IEEE Explorer and found 73 papers that used the repository).
* **Version 4:** In 2014, with support from N.C. State, that site was upgraded to terabyte size. At the same time, a support discussion forum was created at [http://openscience.us/ssj](http://openscience.us/ssj).

### Credits

_Founders_: Tim Menzies, Jelber Sayyad

#### _Curators_:

(If we missed your name, please [email us](mailto:openscience.content@gmail.com) to add you in.)

+ _Version 0_ : Mike Chapman, Justin DiStefano
+ _Version 1_ : Jelber Sayyad
+ _Version 2_ : Tim Menzies
+ _Version 3_ : Bora Caglayan, Zhimin He, Ekrem Kocaguneli, Joe Krall, Tim Menzies, Fayola Peters, Burak Turhan
+ _Version 4_: Tim Menzies, Carter Pape, Corbin Steele, Mitch Rees-Jones, David Pryor
104 changes: 52 additions & 52 deletions repo/code-analysis/_posts/2015-04-09-apienergymining.md
@@ -1,52 +1,52 @@
---
title: Energy Mining
excerpt: "Mining energy-greedy API usage patterns in Android apps: an empirical study"
layout: repo-dataset
authors: "Mario Linares-Vásquez; Gabriele Bavota; Carlos Bernal-Cárdenas; Rocco Oliveto; Massimiliano Di Penta; Denys Poshyvanyk"
version: 4
---

#URL

* [Data in Terapromise](https://terapromise.csc.ncsu.edu:8443/!/#repo/view/head/code-analysis/apienergymining)
* [Paper in ACM Digital Library](http://dl.acm.org/citation.cfm?id=2597085)

#Change Log

When | What
---- | ----
April 9th, 2015 | Donated by [Mario Linares-Vásquez](/repo/people/data-donors/promise4.html)

#Reference

Studies who have been using the data (in any form) are required to include the following reference:

```
@inproceedings{Linares-Vasquez:2014:MEA:2597073.2597085,
author = {Linares-V\'{a}squez, Mario and Bavota, Gabriele and Bernal-C\'{a}rdenas, Carlos and Oliveto, Rocco and Di Penta, Massimiliano and Poshyvanyk, Denys},
title = {Mining Energy-greedy API Usage Patterns in Android Apps: An Empirical Study},
booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
series = {MSR 2014},
year = {2014},
isbn = {978-1-4503-2863-0},
location = {Hyderabad, India},
pages = {2--11},
numpages = {10},
url = {http://doi.acm.org/10.1145/2597073.2597085},
doi = {10.1145/2597073.2597085},
acmid = {2597085},
publisher = {ACM},
address = {New York, NY, USA},
keywords = {Empirical Study, Energy consumption, Mobile applications},
}
```

#About the Data

##Overview of Data

Excessive energy consumption in mobile apps can be a consequence of energy greedy hardware, bad programming practices, or particular API usage patterns. We present the largest to date quantitative and qualitative empirical investigation into the categories of API calls and usage patterns that—in the context of the Android development framework—exhibit particularly high energy consumption profiles. By using a hardware power monitor, we measure energy consumption of method calls when executing typical usage scenarios in 55 mobile apps from different domains. Based on the collected data, we mine and analyze energy-greedy APIs and usage patterns. We zoom in and discuss the cases where either the anomalous energy consumption is unavoidable or where it is due to suboptimal usage or choice of APIs. Finally, we synthesize our findings into actionable knowledge and recipes for developers on how to reduce energy consumption while using certain categories of Android APIs and patterns

## Abstract

Energy consumption of mobile applications is nowadays a hot topic, given the widespread use of mobile devices. The high demand for features and improved user experience, given the available powerful hardware, tend to increase the apps’ energy consumption. However, excessive energy consumption in mobile apps could also be a consequence of energy greedy hardware, bad programming practices, or particular API usage patterns. We present the largest to date quantitative and qualitative empirical investigation into the categories of API calls and usage patterns that—in the context of the Android development framework—exhibit particularly high energy consumption profiles. By using a hardware power monitor, we measure energy consumption of method calls when executing typical usage scenarios in 55 mobile apps from different domains. Based on the collected data, we mine and analyze energy-greedy APIs and usage patterns. We zoom in and discuss the cases where either the anomalous energy consumption is unavoidable or where it is due to suboptimal usage or choice of APIs. Finally, we synthesize our findings into actionable knowledge and recipes for developers on how to reduce energy consumption while using certain categories of Android APIs and patterns.
---
title: Energy Mining
excerpt: "Mining energy-greedy API usage patterns in Android apps: an empirical study"
layout: repo-dataset
authors: "Mario Linares-Vásquez; Gabriele Bavota; Carlos Bernal-Cárdenas; Rocco Oliveto; Massimiliano Di Penta; Denys Poshyvanyk"
version: 4
---

# URL

* [Data in Terapromise](https://terapromise.csc.ncsu.edu:8443/!/#repo/view/head/code-analysis/apienergymining)
* [Paper in ACM Digital Library](http://dl.acm.org/citation.cfm?id=2597085)

# Change Log

When | What
---- | ----
April 9th, 2015 | Donated by [Mario Linares-Vásquez](/repo/people/data-donors/promise4.html)

# Reference

Studies who have been using the data (in any form) are required to include the following reference:

```
@inproceedings{Linares-Vasquez:2014:MEA:2597073.2597085,
author = {Linares-V\'{a}squez, Mario and Bavota, Gabriele and Bernal-C\'{a}rdenas, Carlos and Oliveto, Rocco and Di Penta, Massimiliano and Poshyvanyk, Denys},
title = {Mining Energy-greedy API Usage Patterns in Android Apps: An Empirical Study},
booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
series = {MSR 2014},
year = {2014},
isbn = {978-1-4503-2863-0},
location = {Hyderabad, India},
pages = {2--11},
numpages = {10},
url = {http://doi.acm.org/10.1145/2597073.2597085},
doi = {10.1145/2597073.2597085},
acmid = {2597085},
publisher = {ACM},
address = {New York, NY, USA},
keywords = {Empirical Study, Energy consumption, Mobile applications},
}
```

# About the Data

## Overview of Data

Excessive energy consumption in mobile apps can be a consequence of energy greedy hardware, bad programming practices, or particular API usage patterns. We present the largest to date quantitative and qualitative empirical investigation into the categories of API calls and usage patterns that—in the context of the Android development framework—exhibit particularly high energy consumption profiles. By using a hardware power monitor, we measure energy consumption of method calls when executing typical usage scenarios in 55 mobile apps from different domains. Based on the collected data, we mine and analyze energy-greedy APIs and usage patterns. We zoom in and discuss the cases where either the anomalous energy consumption is unavoidable or where it is due to suboptimal usage or choice of APIs. Finally, we synthesize our findings into actionable knowledge and recipes for developers on how to reduce energy consumption while using certain categories of Android APIs and patterns

## Abstract

Energy consumption of mobile applications is nowadays a hot topic, given the widespread use of mobile devices. The high demand for features and improved user experience, given the available powerful hardware, tend to increase the apps’ energy consumption. However, excessive energy consumption in mobile apps could also be a consequence of energy greedy hardware, bad programming practices, or particular API usage patterns. We present the largest to date quantitative and qualitative empirical investigation into the categories of API calls and usage patterns that—in the context of the Android development framework—exhibit particularly high energy consumption profiles. By using a hardware power monitor, we measure energy consumption of method calls when executing typical usage scenarios in 55 mobile apps from different domains. Based on the collected data, we mine and analyze energy-greedy APIs and usage patterns. We zoom in and discuss the cases where either the anomalous energy consumption is unavoidable or where it is due to suboptimal usage or choice of APIs. Finally, we synthesize our findings into actionable knowledge and recipes for developers on how to reduce energy consumption while using certain categories of Android APIs and patterns.

0 comments on commit 5c5f26d

Please sign in to comment.