CSSPLICE.github.io/SIGCSE25.html at master · CSSPLICE/CSSPLICE.github.io · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
<!DOCTYPE html>
<html>
  <meta charset="UTF-8">
  <head>
    <title>Eleventh SPLICE Workshop</title>
    <link href="cssplice.css" rel="stylesheet" type="text/css">
  </head>
  <body>
    <div id="content">
      <h1>SPLICE'25: CS Education Research Technology<br/>
        and Data Infrastructure Community Meeting</h1>

      <h2>Eleventh SPLICE Workshop Call for Participation</h2>

      <p>All information on this page is currently tentative!</p>

      <p>CS educators and CS Ed researchers and developers are invited
        to the 11th annual SPLICE meeting, focused on creating new
        Technology and Data Infrastructure for CS Education
        Research.</p>

      <p>The mission of the SPLICE project is to develop Technology and Data
        Infrastructure for CS Education Research.</p>

      <p><b>Registration:</b> If think that you are likely to attend,
        please fill out
        the <a href="https://forms.gle/2rE8wkaRiFpSCLQh9">Registration
          Form</a>.</p>

      <p><bWhere/When:</b> Wednesday, February 26, 2025, Pittsburgh, PA
        (An Affiliated Event with SIGCSE’25)</p>

      <p><b>Who should attend?</b> We encourage you to attend if:</p>
        <ul>
          <li>You have CS learner data (e.g., from a tool or study)
            and want to analyze or share it.</li>
          <li>You are looking for datasets from CS courses to do
            analysis (e.g., understand student behavior, train a
            model).</li>
          <li>You create systems/tools to support CS learning that you
            want to be useful in other classrooms. Especially if you
            want your tool to integrate with other tools.</li>
          <li>You teach CS and want to use high-quality learning
            content and tools (like these examples) made by others.</li>
          </ul>

<p><b>What will you do at the workshop?</b> You will:</p>
<ul>
  <li>Learn about existing tools, data and research infrastructure
    that can help you improve your CS teaching and research, and share
    your content with others.</li>
  <li>Opportunity to get feedback on your own research or teaching
    project, with support from like-minded peers, and SPLICE experts who
    can connect you to datasets, tools, and infrastructure that can help
    you accomplish your goals.</li>
  <li>Help shape the next generation of CS research infrastructure.</li>
</ul>

<p><b>How much does it cost?</b>
  <ul>
    <li>Attendance is free. However, you are expected to register
      for SIGCSE’25.</li>
      </ul>

<p>To participate in the workshop: If think that you are likely to
  attend, please fill out
  the <a href="https://forms.gle/2rE8wkaRiFpSCLQh9">Registration
    Form</a>.</p>

See the <a href="https://docs.google.com/document/d/1eWHayBreIWFACrvTGqh_fFPF25aY3rcN87cyvWicLRU/edit?usp=sharing">Community Contributions Page</a>.


<h2>Workshop Hosts</h2>

<p>
Cliff Shaffer, Virginia Tech<br/>
Peter Brusilovsky, University of Pittsburgh<br/>
Ken Koedinger, Carnegie Mellon University<br/>
Thomas Price, North Carolina State University<br/>
Tiffany Barnes, North Carolina State University<br/>


<h2>Workshop Agenda (Tentative)</h2>

<b>Please use the notes documents in <a href="https://drive.google.com/drive/folders/1DcvQuw8stDsS1oB2y0Sa-NMXfr78bfh9">this folder</a>!</b>

<p>9:00 Introduction Plenary Session
  <ul>
    <li>Introduction and orientation (Peter)
    <li>A brief presentation on the SPLICE website and the SPLICE
      catalog to seed the discussion groups (Cliff)
    <li>Brief presentation of DataShop and LearnSphere support for CER (Ken)
    <li>Breakout session attendance planning (Cliff)
</ul>
</p>

<p>9:30 Discussion Breakout 1: What can SPLICE infrastructure provide to you?
  (Round table discussion topics derived from survey)
  <ul>
    <li>LLM use in education #1: How students use LLMs (Bita)
    <li>Data Logging and Analysis; Using data to evaluate interventions
      (Thomas, Samiha, Ken)
    <li>Community needs regarding the SPLICE Portal/Website and Catalog (Peter)
    <li>Community needs regarding interoperability of smart learning tools (Cliff)
    <li>Demo table with discussion: Smart content authoring (Kamil)
  </ul>
</p>

<p>10:30 Break
</p>

<p>11:00 Working Groups I Breakout:
  <ul>
    <li>SPLICE Website/Portal & Catalog WG (Cliff)
    <li>SLC Bundling and Curriculum Packaging WG (Peter, Cory)
    <li>LLM WG #1 (Juho, Ken/Christina)
    <li>Packaging Interventions WG (Thomas)
  </ul>
</p>

<p>12:00 Lunch</p>

<p>1:00 Plenary: Announcements, report-outs from morning sessions</p>

<p>1:15 Discussion Breakout 2: Topics gathered from the registration survey
  forms
  <ul>
    <li>LLM use in education #2: How instructors use LLMs (Juho, Bita)
    <li>Content Bundling and SLC Authoring (Tiffany)
    <li>Next 10 years of CS Education research (and how SPLICE can contribute) (Thomas, Ken)
    <li>Course-related Data Dashboards for Instructors (Peter)
  </ul>
</p>

<p>2:15 Break</p>

<p>3:00 Working Groups II Breakout:
  <ul>
    <li>SPLICE Protocols: Iframe protocol, PEML/Parsons WG (Cliff)
    <li> ProgSnap WG (Thomas)
    <li>LLM Working Group #2 (Tiffany, Ken/Christina)
    <li>Reusable Code Examples WG (Peter)
  </ul>
</p>

<p>4:00 Report-outs from afternoon sessions</p>

<p>4:30 Discussion and wrap-up</p>

    <div id="footer">
      <p class="footertext">
        Last updated:
        <script type="text/javascript">
          document.write(document.lastModified);
        </script>
      </p>
    </div>

  </body>
</html>