Skip to content

Commit 7a3c05c

Browse files
committed
may 2024 update
1 parent 49d8ada commit 7a3c05c

File tree

25 files changed

+248
-32
lines changed

25 files changed

+248
-32
lines changed

.DS_Store

0 Bytes
Binary file not shown.

_data/alumni.yml

Lines changed: 20 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,15 @@
1-
# Postdoctoral and PhD Graduates:
1+
# Postdoctoral Graduates:
2+
- name: Dr. Ali Ghanbari
3+
status: Postdoctoral Fellow
4+
email: alig@iastate.edu
5+
site: https://ali-ghanbari.github.io/
6+
img: ali.jpg
7+
8+
- name: Dr. Breno Dantas Cruz
9+
status: Postdoctoral Fellow
10+
email: bdantasc@iastate.edu
11+
site: https://www.cs.iastate.edu/people/breno-dantas-cruz
12+
img: breno.jpg
213

314
- name: Dr. Hoan A. Nguyen
415
status: Postdoctoral Fellow
@@ -12,6 +23,14 @@
1223
site: http://design.cs.iastate.edu
1324
img: zyu.jpeg
1425

26+
# PhD Graduates:
27+
28+
- name: Dr. Mohammad Wardat
29+
status: PhD Summer'23
30+
email: wardat@iastate.edu
31+
site: https://www.cs.iastate.edu/people/mohammad-wardat
32+
img: wardat.jpg
33+
1534
- name: Dr. Sumon Biswas
1635
status: PhD Spring'22, MS Spring'21
1736
email: sumon@iastate.edu

_data/members.yml

Lines changed: 1 addition & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -11,18 +11,6 @@
1111

1212
# Postdocs:
1313

14-
- name: Breno Dantas Cruz
15-
status: Postdoctoral Fellow
16-
email: bdantasc@iastate.edu
17-
site: https://www.cs.iastate.edu/people/breno-dantas-cruz
18-
img: breno.jpg
19-
20-
- name: Ali Ghanbari
21-
status: Postdoctoral Fellow
22-
email: alig@iastate.edu
23-
site: https://ali-ghanbari.github.io/
24-
img: ali.jpg
25-
2614
# PhD Candidates:
2715

2816
- name: Shibbir Ahmed
@@ -36,13 +24,7 @@
3624
email: fraol@iastate.edu
3725
site: https://fraolbatole.github.io/
3826
img: fraol.jpg
39-
40-
- name: Usman Gohar
41-
status: PhD
42-
email: ugohar@iastate.edu
43-
site: https://www.cs.iastate.edu/ugohar
44-
img: usman.jpg
45-
27+
4628
- name: Sayem Imtiaz
4729
status: PhD
4830
email: sayem@iastate.edu
@@ -79,12 +61,6 @@
7961
site: https://deepakgthomas.github.io/
8062
img: deepak.jpg
8163

82-
- name: Mohammad Wardat
83-
status: PhD
84-
email: wardat@iastate.edu
85-
site: https://www.cs.iastate.edu/people/mohammad-wardat
86-
img: wardat.jpg
87-
8864
# Master's Students:
8965

9066
# Bachelor's Students:

_papers/.DS_Store

0 Bytes
Binary file not shown.

_papers/ASE-23/ase23.pdf

611 KB
Binary file not shown.

_papers/ASE-23/index.md

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
---
2+
key: ASE-23
3+
permalink: /papers/ASE-23/
4+
short_name: ASE '23
5+
title: Mutation-based Fault Localization of Deep Neural Networks
6+
bib: |
7+
@inproceedings{ghanbari2023deepmufl,
8+
author = {Ghanbari, Ali and Thomas, Deepak-George and Arshad, Muhammad Arbab and Rajan, Hridesh},
9+
title = {Mutation-based Fault Localization of Deep Neural Networks},
10+
booktitle = {ASE'2023: 38th IEEE/ACM International Conference on Automated Software Engineering},
11+
location = {Kirchberg, Luxembourg},
12+
month = {September 11--15},
13+
year = {2023},
14+
entrysubtype = {conference},
15+
abstract = {
16+
Deep neural networks (DNNs) are susceptible to bugs, just like other types of software systems. A significant uptick in using DNN, and its applications in wide-ranging areas, including safety-critical systems, warrant extensive research on software engineering tools for improving the reliability of DNN-based systems. One such tool that has gained significant attention in the recent years is DNN fault localization. This paper revisits mutation-based fault localization in the context of DNN models and proposes a novel technique, named deepmufl, applicable to a wide range of DNN models. We have implemented deepmufl and have evaluated its effectiveness using 109 bugs obtained from StackOverflow. Our results show that deepmufl detects 53/109 of the bugs by ranking the buggy layer in top-1 position, outperforming state-of-the-art static and dynamic DNN fault localization systems that are also designed to target the class of bugs supported by deepmufl. Moreover, we observed that we can halve the fault localization time for a pre-trained model using mutation selection, yet losing only 7.55% of the bugs localized in top-1 position.
17+
}
18+
}
19+
kind: conference
20+
download_link: ase23.pdf
21+
publication_year: 2023
22+
tags:
23+
- boa
24+
---

_papers/EMSE-23/emseMLContract.pdf

1.19 MB
Binary file not shown.

_papers/EMSE-23/index.md

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
---
2+
key: EMSE-23
3+
permalink: /papers/EMSE-23/
4+
short_name: EMSE '23
5+
title: "What Kinds of Contracts Do ML APIs Need?"
6+
bib: |
7+
@article{Khairunnesa2023,
8+
author = {Samantha Syeda Khairunnesa and Shibbir Ahmed and Sayem Mohammad Imtiaz and Hridesh Rajan and Gary T. Leavens},
9+
title = {What Kinds of Contracts Do ML APIs Need?},
10+
journal = {Empirical Software Engineering},
11+
volume = {1},
12+
number = {1},
13+
article = {1},
14+
month = {March},
15+
year = {2023},
16+
publisher = {Springer},
17+
address = {Hanover, Pennsylvania, USA},
18+
abstract = {Recent work has shown that Machine Learning (ML) programs are error-prone and called for contracts for ML code. Contracts, as in the design by contract methodology, help document APIs and aid API users in writing correct code. The question is: what kinds of contracts would provide the most help to API users? We are especially interested in what kinds of contracts help API users catch errors at earlier stages in the ML pipeline. We describe an empirical study of posts on Stack Overflow of the four most often-discussed ML libraries: TensorFlow , Scikit-learn, Keras, and PyTorch. For these libraries, our study extracted 413 informal (English) API specifications. We used these specifications to understand the following questions. What are the root causes and effects behind ML contract violations? Are there common patterns of ML contract violations? When does understanding ML contracts require an advanced level of ML software expertise? Could checking contracts at the API level help detect the violations in early ML pipeline stages? Our key findings are that the most commonly needed contracts for ML APIs are either checking constraints on single arguments of an API or on the order of API calls. The software engineering community could employ existing contract mining approaches to mine these contracts to promote an increased understanding of ML APIs. We also noted a need to combine behavioral and temporal contract mining approaches. We report on categories of required ML contracts, which may help designers of contract languages.},
19+
doi={10.1145/nnnnnn},
20+
}
21+
kind: journal
22+
download_link: emseMLContract.pdf
23+
publication_year: 2023
24+
tags:
25+
- mdl
26+
---

_papers/ESEC-FSE-19/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,5 +45,5 @@ extra_download_links:
4545
- { link: dataset.zip , title: Dataset}
4646
publication_year: 2019
4747
tags:
48-
- boa
48+
- d4
4949
---

_papers/ESEC-FSE-20a/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,5 +41,5 @@ kind: conference
4141
download_link: ml-fairness.pdf
4242
publication_year: 2020
4343
tags:
44-
- boa
44+
- d4
4545
---

0 commit comments

Comments
 (0)