-
Notifications
You must be signed in to change notification settings - Fork 2
/
index.html
956 lines (856 loc) · 72 KB
/
index.html
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
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>DIGM5010 Foundations of Digital Media</title>
<meta name="description" content="">
<meta name="author" content="Graham Wakefield">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="apple-mobile-web-app-capable" content="yes">
<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent">
<link rel="stylesheet" href="css/basic.css" type="text/css" />
<link rel="stylesheet" href="css/github.css" type="text/css" />
<style>
img {
max-height: 75vh;
}
td { vertical-align: top;}
header {
background-color:#f5f5f5;
font-size: 75%;
padding: 0.5em;
}
footer {
background-color:#f5f5f5;
font-size: 75%;
padding: 0.5em;
}
</style>
</head>
<body class="centremaxwidth960">
<header><a href="index.html">Foundations of Digital Media</a></header>
<ul>
<li><a href="#digm5010-foundations-of-digital-media">DIGM5010 Foundations of Digital Media</a><ul>
<li><a href="#what-is-digm-5010-foundations">What is DIGM 5010 "Foundations"?</a></li>
</ul>
</li>
<li><a href="#week-0">Week 0</a><ul>
<li><a href="#a-question">A question</a></li>
<li><a href="#an-introduction">An introduction</a></li>
<li><a href="#a-reading">A reading</a></li>
</ul>
</li>
<li><a href="#week-1">Week 1</a><ul>
<li><a href="#computational-sketching">Computational sketching</a></li>
<li><a href="#lets-get-making">Let's get making</a></li>
</ul>
</li>
<li><a href="#week-2">Week 2</a><ul>
<li><a href="#what-is-research">What is Research?</a></li>
<li><a href="#a-call-for-papers">A Call for Papers</a></li>
<li><a href="#preparing-a-reading-list">Preparing a Reading List</a></li>
<li><a href="#making-2-animate-drawing">Making 2: animate drawing</a></li>
</ul>
</li>
<li><a href="#week-3">Week 3</a></li>
<li><a href="#week-4">Week 4</a><ul>
<li><a href="#annotated-bibliography">Annotated Bibliography</a></li>
</ul>
</li>
<li><a href="#week-5">Week 5</a></li>
<li><a href="#week-6">Week 6</a></li>
<li><a href="#week-7">Week 7</a></li>
<li><a href="#week-8">Week 8</a><ul>
<li><a href="#peer-review">Peer Review</a></li>
</ul>
</li>
<li><a href="#week-9">Week 9</a><ul>
<li><a href="#final-paper">Final Paper</a></li>
</ul>
</li>
<li><a href="#week-10">Week 10</a><ul>
<li><a href="#video-tutorial">Video Tutorial</a></li>
</ul>
</li>
<li><a href="#week-11">Week 11</a></li>
<li><a href="#week-12">Week 12</a></li>
</ul>
<hr>
<h1 id="digm5010-foundations-of-digital-media">DIGM5010 Foundations of Digital Media</h1>
<p>Thursdays, 1.30pm-4.30pm, Fall 2024, Fine Arts building room ACW 102</p>
<p><strong>Instructor:</strong> <a href="https://ampd.yorku.ca/profile/graham-wakefield/">Graham Wakefield</a> grrrwaaa a t york u do t ca</p>
<p><strong>Hello and welcome!</strong></p>
<h2 id="what-is-digm-5010-foundations">What is DIGM 5010 "Foundations"?</h2>
<p><strong>Synopsis:</strong> The purpose of Foundations is to equip and assist students to undertake <strong>graduate-level research</strong> in <strong>Digital Media</strong>. </p>
<p>DIGM5010 is foundational core course in the <a href="https://www.yorku.ca/gradstudies/digitalmedia/">Digital Media Graduate Program</a> (MA/MSc/PhD), co-organized by the <a href="https://computationalarts.ampd.yorku.ca">Department of Computational Arts</a> in the School of the Arts, Media, Performance & Design, and the department of <a href="https://lassonde.yorku.ca/eecs/">Electrical Engineering and Computer Science</a> in the Lassonde School of Engineering, York University.</p>
<blockquote>
<p>"The Graduate Program in Digital Media provides highly qualified students with the opportunity to do specialised hybrid research work in a program that uniquely combines computational science and artistic practices. Work in digital media focuses on a broad range of current and emerging forms of digitally supported media, with applications that range from computer games to interactive art."</p>
</blockquote>
<blockquote>
<p>The Digital Media graduate program's academic objectives include promotion of an interdisciplinary approach to computational art-making and technology development, providing students with 21st century “real-world” skills in tandem with research acumen. To work and conduct research in this area means skillfully bridging literacies in art, science and engineering practices. </p>
</blockquote>
<p>Developing these research literacies is what DIGM5010 is all about. </p>
<p>The goals of the <em>Foundations</em> course are therefore:</p>
<ul>
<li>to learn the essential methodological skills of graduate-level research in areas of digital media and computational arts</li>
<li>to develop deep understanding and a real feel for computation as a creative medium, </li>
<li>to develop the skills to attain literacy in mathematical, theoretical, and computational bases as they intersect with worlds of digital art-making,</li>
<li>to be able to adequately place your research within a larger network of relations and lineages, and to be able to articulate its relevance and identify its values in context.</li>
</ul>
<p>This means:</p>
<ul>
<li>being aware of the broad range of the field along with its nearer and farther histories, narrow and broader presents, and implicated or possible futures,</li>
<li>being able to find, read, and understand the languages through which research is articulated, in both theoretical and practical terms, </li>
<li>being able to create work across of a broad range of digital media that is effective and/or innovative.</li>
</ul>
<p>Establishing these foundations is ultimately evaluated through the potential to understand, transfer, and extend published research in these fields into new creative applications, recreating or mutating established research results, projects, or works to the specific interests of your research area(s) and creative domain(s). </p>
<p><em>(Reading, writing, making!)</em></p>
<p><strong>Format and evaluation</strong> </p>
<p>Each weekly meeting will vary in format, but always at the heart is the discussion between all of us. This isn't a course with a static syllabus of material -- it is an adaptive living system. </p>
<p>In the early part of the course the instructor may bring lecture material or assign readings or research tasks; and we will often dive into collectively coding or algorithmically reconstructing and reinterpreting work drawn from the literature, nestling theory in practice. You are also expected to bring work to share, <strong>making things</strong> in response to our discussions and course topic. You should be keeping your notes, studies and practices documented in a <strong>public journal</strong>. (Class participation, making and journalling make up the first 25% of the course grade.)</p>
<p><a href="https://docs.google.com/forms/d/e/1FAIpQLSdUCztWAi-z4x5r_RTXhsWnvqiw46hPZRIh7eqChm7FGoFGqQ/viewform?usp=sf_link">You can submit codepen sketches through this form</a></p>
<p>As this goes on, each of you will develop a focus on a specific topic to research in depth, leading to a project documented in a research paper. The project's goal is to functionally reproduce and/or interestingly mutate work from the research community and literature. </p>
<ul>
<li>It will be grounded through an <strong>extensive literature review</strong> (25%),</li>
<li>will demonstrate your foundational computational literacy and ability to understand and transfer research into creative applications (25%),</li>
<li>and will be documented in <strong>a research paper</strong> with scholarly citations <strong>suitable to submit to conferences or other appropriate venues</strong> (25%).</li>
</ul>
<p>We will go through draft processes and a simulated conference submission and review procedure later in the course to help understand academic research structures and refine your work. In the past years, some students have also been successful in submitting their final papers to real academic conferences.</p>
<p><strong>Online resources</strong></p>
<p>Almost everything about this course will be linked from <a href="https://alicelab.world/digm5010">https://alicelab.world/digm5010</a> -- bookmark this URL!</p>
<p>Previously we have also used a Microsoft Teams account for sharing file materials etc., but I have found it somewhat unreliable/unstable and I am open to alternatives if there are good suggestions.</p>
<p><strong>Remote participation</strong></p>
<p>Regardless whether we are meet in person or remotely, I usually prefer to open a Zoom session for my classes, and use share screen for the most part. </p>
<ul>
<li><a href="https://yorku.zoom.us/j/91019623418?pwd=75h0gYM5Je5nz5Pzbi2vGmWb3G96j4.1">Zoom meeting (same link every week)</a></li>
<li><a href="https://yorku.zoom.us/meeting/tJUtduCurDguG9ygI0mac22YuOOK5vLzj_wb/ics?icsToken=98tyKuCprjojHNaWtBiPRowcAoj4Xe7zpnZbjfpEmza1DiFQMFHPI81tGedpPMLa">Add it to your calendar (.ics file)</a></li>
</ul>
<p>I normally also record all sessions and share recordings with the course participants (so long as no participants have objections to this), as I have heard that it has been useful for many students to be able to review sessions after class hours, including when, due to factors outside their control, they could not attend in class time. <em>Synchronous attendance is highly recommended given the importance of critical discussion on the development of your studies in the program and your research/research-creation; but if you are expecting challenges in attending all times please do not worry. Having the sessions recorded alleviates some inevitable challenges of the graduate situation, and moreover allows some time to review any material if it seemed to fly too fast. You are all coming from different backgrounds so this is also inevitable.</em></p>
<hr>
<p><em>Note: The <a href="https://gradstudies.yorku.ca/current-students/regulations/courses-grading/">grading scheme for graduate study at York</a> is as follows: 90+ A+ (exceptional), 85+ A (excellent), 80+ A- (high), 75+ B+ (highly satisfactory), 70+ B (satisfactory), 60+ C (conditional), <60 F (fail) or I (incomplete).</em></p>
<hr>
<hr>
<h1 id="week-0">Week 0</h1>
<p>Sep 5, 2023</p>
<p><strong>Hello and welcome!</strong></p>
<p>We are in a program of digital media, co-run by computational arts and computer science. Art & science as "two cultures", meeting through a cybernetic medium of computation. </p>
<p>But perhaps "meeting" is too gentle a word. Sometimes it feels like a tectonic collision. To discover something new, we cannot follow a single path. Collisions between trajectories derail and open into new possibilities, that wouldn't be found if you only followed trend lines or deductive trails. </p>
<p>So, be comfortable to get out of your comfort zone. Learn from each other. It's OK to be awkward. Children are the most awkward, and the fastest learners, so let us be children again from time to time -- so long as we work hard at it! </p>
<p>So for example, what does "computation" mean to you?</p>
<hr>
<p>Deep dive: <a href="automata.html">What is computation?</a> - History, theory, implementation; programs as data</p>
<hr>
<h2 id="a-question">A question</h2>
<p>Take some time to think about this: </p>
<ul>
<li>Why did you want to study in the Digital Media program -- why do you want to dedicate several precious years of your life to research in computational art & science -- what does this mean for you? Is there a great risk, or a great unseen opportunity, in the computational/digital media world -- present and future -- one that also speaks to you?</li>
</ul>
<p><a href="https://docs.google.com/forms/d/e/1FAIpQLSdGbObBWxsQpDoewMLRYDhqJ16EJEsZbbbrpbnNrNkN2u03EA/viewform?usp=sf_link">Write into the form here</a></p>
<h2 id="an-introduction">An introduction</h2>
<p>Please add 2-4 slides to introduce yourself in The Google Slide deck here: <a href="https://docs.google.com/presentation/d/1lvAaIH7lXHz0sc02L7JXVsM_QySOY4SPPdc5tNI5HC4/edit">https://docs.google.com/presentation/d/1lvAaIH7lXHz0sc02L7JXVsM_QySOY4SPPdc5tNI5HC4/edit</a></p>
<ul>
<li>I suggest a brief (~100 words) of your background and the key words/ideas/questions for your work, with representative images/video etc. <ul>
<li>You can include a more formal bio, or artist statement, or something more informal about the inspirations that brought you to the program.</li>
<li>Remember to include your name, and reference details (name, link etc.) for any images or media you add.</li>
<li>Please be careful not to delete your colleague's slides!</li>
</ul>
</li>
</ul>
<h2 id="a-reading">A reading</h2>
<p>I said in class we should look at others’ Masters & PhD theses/dissertations for inspiration. Here’s the Masters thesis of Golan Levin, from when he was a student at MIT. He is now a professor at Carnegie Mellon University, and a key figure in the Art & Code community. There’s a lot to draw from this thesis, both theoretically and practically. Have a good read and bring some thoughts and questions for next week:
<a href="http://www.flong.com/archive/texts/publications/thesis/index.html">http://www.flong.com/archive/texts/publications/thesis/index.html</a></p>
<hr>
<hr>
<h1 id="week-1">Week 1</h1>
<p>Sep 12, 2023</p>
<p><a href="https://docs.google.com/presentation/d/1gukRi55omVeeQcjFBdKagZdfs3_pPLlhgsHfG1go4DU">Introductions</a></p>
<h2 id="computational-sketching">Computational sketching</h2>
<p>A futorologist said to me: to understand the future, we must go much further into the past; to see patterns that recur and trajectories behind the present. However this doesn't mean entering the future through a rear-view mirror (McLuhan's warning); it is to understand the language and concepts we see the world in today, and see their gaps and limitations. So it can be helful sometimes to step into the shoes of those that have gone before, to see how we ended up here, and what we may have lost or missed along the way. </p>
<p>Take <a href="https://en.wikipedia.org/wiki/John_Maeda">John Maeda</a>, the designer & MIT Media Lab professor, who pioneered reactive graphics in the era of the Macintosh and CD-ROM. </p>
<blockquote>
<p><strong>Design By Numbers (John Maeda, 1999)</strong><br>"Drawing by hand, using pencil on paper, is undisputedly the most natural means for visual expression. When moving on to the world of digital expression, however, the most natural means is not pencil and paper, but rather, computation. Today, many people strive to combine the traditional arts with the computer, and while they may succeed at producing a digitally empowered version of their art, they are not producing true digital art. True digital art embodies the core characteristics of the digital medium, which cannot be replicated in any other.</p>
<p>"Computation is intrinsically different from existing media because it is the only medium where the material and the process for shaping the material coexiist in the same entity: numbers. The only other medium where a similar phenomenon occurs is pure thought. It naturally follows that computational media could eventually present the rare opportunity to express a conceptual art that is not polluted by textual or other visual representation. This exciting future is still at least a decade or two away. For the moment, we are forced to settle with society's current search for true meaning in an enhanced, interactive version of the art that we have always known."</p>
</blockquote>
<p>Maeda studied with Muriel Cooper and Paul Rand, and redefined the use of electronic media as a tool for expression by combining computer programming with traditional artistic technique, which helped lay the groundwork for interactive motion graphics as seen on the web today.</p>
<p>Other key insights from Maeda's interactive graphics explorations:</p>
<ul>
<li>the most <strong>interesting</strong> pixels on the screen are the mouse</li>
<li>the mouse represents not just <strong>space</strong> but also <strong>time</strong> -- use it</li>
</ul>
<p>Maeda's courses and research in the Aesthetics & Computation group at MIT inspired a whole generation of creative coders. He taught Casey Reas and Ben Fry, and his <a href="https://en.wikipedia.org/wiki/Design_By_Numbers">Design By Numbers</a> software was the precursor of their Processing (and thence <a href="https://p5js.org/">P5.js</a>). </p>
<p>Maeda's courses challenged students to rethink the medium from its most basic elements. A typical assignment:</p>
<blockquote>
<p>Given a point in space over a finite rectangular area, create a parametric drawing that illustrates repetition, variety, or rhythm. <a href="https://acg.media.mit.edu/courses/mas964/presentation/panels.html">MAS 964 P</a></p>
</blockquote>
<p>Golan Levin was one of Maeda's students, and went on to focus specifically on the creation of audiovisual instruments, responding directly to Maeda's project. (For example, look at Curly and <a href="http://www.flong.com/archive/projects/yellowtail/index.html">Yellowtail</a>.) He is now a professor at Carnegie Mellon University, and a key figure in the Art & Code community. There’s a lot to draw from this thesis, both theoretically and practically. <a href="http://www.flong.com/archive/texts/publications/thesis/index.html">http://www.flong.com/archive/texts/publications/thesis/index.html</a> -- what were your thoughts and questions after reading this? (Also note the document structure.)</p>
<hr>
<h2 id="lets-get-making">Let's get making</h2>
<ul>
<li>A shareable workspace: <a href="https://codepen.io">codepen</a></li>
<li>The HTML5 trio: the HTML (DOM), CSS, and JavaScript<ul>
<li>HMTL: the page container and structure. The language forms a <strong>declarative</strong> data structure, roughly in a tree structure. </li>
<li>CSS: the rules of layout, rendering and style. The language forms a set of <strong>declarative</strong> definitions. </li>
<li>JS: dynamic generation and behaviour. The language forms <strong>procedural</strong> steps of action, invoked in response to events. </li>
</ul>
</li>
<li><a href="https://github.com/worldmaking/worldmaking.github.io/wiki/JS-notes">Javascript</a> </li>
<li>What is an API? <ul>
<li>E.g. the MDN <a href="https://developer.mozilla.org/en-US/docs/Web/API/Canvas_API/Tutorial">canvas documentation</a>. Canvas is a rectangular object in an HTML page, suitable for static and dynamic 2D or 3D graphics rendering.</li>
</ul>
</li>
<li>2D drawing in the web using <a href="https://github.com/worldmaking/worldmaking.github.io/wiki/JS-Canvas,-Vector,-Matrix-etc.-notes">Canvas, vectors, matrices</a> </li>
</ul>
<hr>
<p class="codepen" data-height="520" data-default-tab="js,result" data-user="grrrwaaa" data-slug-hash="yLdrXNQ" data-preview="true"><span><a href="https://codepen.io/grrrwaaa/pen/yLdrXNQ">Open pen.</a></span></p><script async src="https://static.codepen.io/assets/embed/ei.js"></script>
<hr>
<p class="codepen" data-height="520" data-default-tab="js,result" data-user="grrrwaaa" data-slug-hash="Yzdxwgj" data-preview="true"><span><a href="https://codepen.io/grrrwaaa/pen/Yzdxwgj">Open pen.</a></span></p><script async src="https://static.codepen.io/assets/embed/ei.js"></script>
<hr>
<p>Can you continue by drawing an example from Golan Levin's research-creation thesis?</p>
<hr>
<h1 id="week-2">Week 2</h1>
<p>Sep 19, 2023</p>
<ul>
<li>Online class today: - <a href="https://yorku.zoom.us/j/91019623418?pwd=75h0gYM5Je5nz5Pzbi2vGmWb3G96j4.1">Zoom meeting link</a></li>
</ul>
<h2 id="what-is-research">What is Research?</h2>
<p>Deep dive <a href="research.html">presentation</a> & discussion</p>
<hr>
<h2 id="a-call-for-papers">A Call for Papers</h2>
<p>Through this course you will write a research paper and take it through the process of literature review and development, drafting a paper in response to a call for research, and peer review and completion thereof, modeled on real processes of academic research publication. The call for papers we will use is adapted from calls for the <a href="https://s2024.siggraph.org/program/art-papers/">SIGGRAPH Art Papers</a> and the <a href="https://isea2025.isea-international.org/submission/submission-guideline/">ISEA (International Symposium on Electronic Arts)</a>. </p>
<ul>
<li>Note that ISEA 2025 (Seoul, Korea) has a deadline of 15 November 2024 -- if we can move quickly enough in the course you could submit to it! </li>
<li>Siggraph 2025 will be in Vancouver, but (as of writing) the submission deadlines are not yet published. It might be between January to March. </li>
</ul>
<p><em>(Broad terms of call, with theme(s) and topics)</em> </p>
<p>The "DIGM Computational Art Symposium" acts as a bridge between art and technology to rethink and explore our future. The dream is to bring art and engineering communities together, as has been so fruitful in history. We understand art in its broadest sense, encompassing different fields from fine art to design and architecture. Submissions exploring how computer science and interactive techniques — especially those linked to recent developments — that relate to questions of the future are particularly encouraged. We encourage submissions that discuss and explore within the fields of electronic arts, creative technology, digital culture and all manners of art-science-technology collaboration not yet born. We would like you to engage in the Renaissance of the 21st century!</p>
<p>Topics of interest include, but are not limited by:</p>
<ul>
<li>All modes of augmented, mixed, extended and virtual realities from interactive digital worlds to metaverse</li>
<li>Art-science collaborations and practices</li>
<li>Bio-art and artificial life</li>
<li>‘Bleeding edge’ concepts from art-science-technology</li>
<li>Computational media art as a critical and constructive intervention to the ongoing construction of social reality</li>
<li>Creative robotics and human-machine partnerships</li>
<li>Data visualization, sonification, data arts</li>
<li>Explorable explanations: complex ideas conveyed through interactive experiences</li>
<li>Indigenous futures</li>
<li>Machine learning as a co-creator</li>
<li>Media art archiving</li>
<li>New approaches to computational art research and creative practice-based methodologies</li>
<li>Posthuman, transhuman, and ’more than human’ paradigms</li>
<li>Theories of post-image, new aesthetics, and computer vision</li>
<li>Transmedia storytelling</li>
</ul>
<p><em>(Submission categories)</em> </p>
<p>Prospective authors may consider one of the following categories as they prepare their work for submission.</p>
<ul>
<li><strong>Projects and case studies.</strong> Papers in this category rigorously document a realized project that combines computational techniques with creative practice. They also critically explore its social, cultural, and affective impact.</li>
<li><strong>Methodological contributions.</strong> Papers in this category identify, document, and explore emergent methodological approaches that open new pathways to the practice and scholarship of computational art and/or engineering development as well as art-engineering collaboration. This could be in the form of a "white paper" about a new technique. </li>
<li><strong>Reproduction of research.</strong> Re-implmeent a known and significant research paper, and analyze the results. </li>
<li><strong>Innovation through art practices.</strong> Papers in this category explore, through artistic practice including technology development research, the potential use of emerging digital technologies and their impact for users and citizens. They may also express a transdisciplinary work between digital engineering and art practices to develop solutions that confront the major challenges of our times.</li>
<li><strong>History, theory, and criticism.</strong> Papers in this category offer new technically-informed historical, theoretical, and critical perspectives on computational art and on the technical artifacts, infrastructures, and communities that support them.</li>
<li><strong>Novel approach to literature as manifesto.</strong> Discuss more deeply ideas encountered in the bibliography as the basis for a foundational manifesto. Include both the discussion/argumentation as well as the resulting manifesto in the submission.</li>
<li>An <strong>Explorable Explanation</strong>. Inspired by the <a href="https://explorabl.es">Explorable Explanation</a> website, you can either<ul>
<li>a) present a new topic that could be represented and conveyed more effectively as a dynamic system, and in your paper discuss the design and implementation of it, or</li>
<li>b) choose one of the systems in <a href="https://explorabl.es">Explorable Explanations</a> and first offer a critique and second attempt to reproduce it, as an example of replicating research. Document what you observe, e.g. how it (meaningfully) differs (if it does), comparing related work, discussing what new avenues you find or suggest. </li>
<li>In either case don't concern yourself with a slick design, concentrate on what are the core mechanics of the idea, and how they convey an otherwise difficult subject.</li>
</ul>
</li>
</ul>
<p><em>(Paper requirements)</em></p>
<p>We invite paper submissions for original and substantial research, both traditional and non-traditional, that has not been previously published. Papers will follow full academic practices, through an extensive literature review, argumentation, and observations or evaluations of impact. All papers must follow academic standards and will undergo blind peer review based on quality, relevance, originality, and impact. </p>
<p>(See notes on the <a href="#final-paper">Final Paper submission</a> for details about formatting.)</p>
<p>Submissions will be uploaded online. We also ask you to add a very short text explaining why your submission is important for the academic and wider community, from raising critical issues to opening perspectives or generating solutions. In doing so, we aim to enhance the impact of your cultural contributions.</p>
<p>Authors will be required to present their papers with a duration of 10 minutes. </p>
<hr>
<h2 id="preparing-a-reading-list">Preparing a Reading List</h2>
<p>As the first step in this process, you will begin with preparing a collection of papers related to your research topic/question.</p>
<p><strong>Literature review part 1: Reading List</strong></p>
<p>In this course you will investigate a topic within a sub-area of the digital media realm that intersects with something of value to your own research goals in the program. </p>
<p>In the first phase you will build up a <strong>reading list</strong> on your chosen topic. Please create an online document that you can share (e.g. a github page, a google doc, etc.) to collect your notes and references as you develop this reading list.</p>
<p>As we saw in class, good research needs a good research question, but that doesn't always become apparent at first. Start wider until you are ready to go deep & narrow. Seek out key papers, conferences, and other key resources for the topic. </p>
<ul>
<li><p>Some investigative tips:</p>
<ul>
<li>Use Wikipedia to identify <strong>keywords or terms</strong>, questions and issues, foundational publications and controversies, etc. This can also help to make your search more narrow/specific. Look for the edges of a body of research. Wikipedia is an excellent network of conceptual nodes (but also a potential rabbithole). But remember that it is an encyclopedia, and should be used mainly as a guide map.</li>
<li>Use these terms and publications in <a href="https://scholar.google.com/">Google Scholar</a>, <a href="https://www.zotero.org">Zotero</a> and other academic search engines to find for papers that address the questions and issues. Follow <code>cited by</code> and <code>related articles</code> trails to find new leads. Aim to find the most significant (qualitatively & quantitatively) papers. You should be aiming for a collection of 25-50 potentially interesting papers on the topic at this point. </li>
<li>At the same time, look for conferences or journals that are more specific to your topic, and see if they have collections of proceedings online to browse through. </li>
<li>Not all papers are available as PDFs online. You might be able to find them via <a href="https://www.library.yorku.ca/web/bbl/e-resources/">York Libraries</a> or also communities like <a href="https://www.researchgate.net/">ResearchGate</a>, but do not let this roadblock your progress -- find alternatives to work from instead.</li>
<li>At this point you may be able to formulate a first draft of a title of the topic or area, perhaps even a key question or problem statement; but don't worry at this stage if you haven't yet.<ul>
<li>Collect this list as a <strong>Reading List</strong> along with:</li>
</ul>
</li>
<li>The specific topic title or</li>
<li>The keywords or search terms</li>
<li>The work-in-progress research question/problem statement/abstract</li>
</ul>
</li>
<li><p><a href="https://www.library.yorku.ca/web/ask-services/printing-and-computing/computing/off-campus-access/">York off-campus library access</a></p>
</li>
<li><p><a href="http://www.yorku.ca/computing/vpn-choice.html">York VPN links</a></p>
</li>
</ul>
<hr>
<h2 id="making-2-animate-drawing">Making 2: animate drawing</h2>
<p>Let's continue from last week's drawing app. </p>
<blockquote>
<p>First a quick note -- what we are doing looks a bit like p5.js. In fact, if we remember to refactor code that we will re-use into re-usable functions, then it might start to look even more like p5.js -- maybe we will have <code>line()</code> and <code>background()</code> etc. That's good: we are in the stage of <em>reproducing research</em>. And if we find there are moments where we want to do things a little differently, because of the needs of our project, that's good too -- we aren't limited to what's already given because we know how to remake it, and maybe we'll have a discovery that can advance research! </p>
</blockquote>
<ul>
<li><p>We saw how we can draw in response to mouse/touch movements, and add generative variation to them. </p>
</li>
<li><p>We talked about Maeda's comment "the most interesting pixels are the mouse" and this represents not just space but also <strong>time</strong>. How can we use the timing of a drawing gesture to modify the result? Can you think of ways to use speeds, rhythms, echoes, ?</p>
<ul>
<li>Can we <em>reify</em> the time of the gesture?</li>
</ul>
</li>
</ul>
<p>A more complex example, inspired by Paul Haberli's <em>Dynadraw</em>: </p>
<p class="codepen" data-height="520" data-default-tab="js,result" data-user="grrrwaaa" data-slug-hash="gOYQyrd?editors=0010" data-preview="true"><span><a href="https://codepen.io/grrrwaaa/pen/gOYQyrd?editors=0010">Open pen.</a></span></p><script async src="https://static.codepen.io/assets/embed/ei.js"></script>
<ul>
<li><p>Last week we also saw how we can make animations through an erase/draw loop, demonstrated by drawing random lines on each frame. But these have no consistency from one frame to the next. How can we add consistency?</p>
</li>
<li><p>Or: how can we combine both sketching and animating? How can we draw a line that then animates?</p>
<ul>
<li>Can we <em>reify</em> the drawing?</li>
</ul>
</li>
<li><p>With these steps, we should be in a position to attempt to reconstruct Golan Levin's Curly/<a href="http://www.flong.com/archive/projects/yellowtail/index.html">Yellowtail</a>, for example. </p>
</li>
</ul>
<!--
[Second class codepen](https://codepen.io/grrrwaaa/pen/jOXYdMd?editors=0010)
-->
<hr>
<p>Please continue working toward reconstruction of one of Golan Levin's thesis projects; or better still, to extend and mutate it into a new direction! We will share each other's codepens in the next class. </p>
<p>Some rules of thumb:</p>
<ul>
<li><p>Use the simplest limits you can -- e.g. limiting yourself to drawing only black lines. More colour, shape and style variations can always be added later. Let's focus on behaviour first.</p>
</li>
<li><p>Break a problem down into sub-problems. Approach the problem from a simpler approximation first -- the simplest version. E.g. make it work in a static way before a dynamic way, or make it work for one, before making it work for many, etc.</p>
</li>
<li><p>Try to work out a problem in pseudocode first -- just write it in commments, draw it on paper, etc, any form that is concrete will help to see the problem more clearly, and diving head first into code isn't often the right thing to do. Once the method becomes clearer, start converting pseudocode into "minimum viable" code.</p>
</li>
<li><p>Use event handlers (draw-frame, mouse, keyboard, timers, ...) to animate and interact with things. </p>
</li>
<li><p>Figure out working conditions logically from basic requirements. E.g. for anything to animate we're going to need to clear the screen on each frame, which means we're going to have to redraw everything every time, which means...</p>
</li>
<li><p>Use state (variables for numbers, strings, objects, arrays) to make things exist over time. Once captured, data can be replayed, modified, etc. Often you can represent state in a few different ways, and the choice will make some processes easier than others.</p>
</li>
<li><p>Test often. Each time you add one minor element, make sure it works for all likely input. </p>
</li>
<li><p>Handle special cases: starting values, boundary cases, error handling... </p>
</li>
<li><p>Don't worry about trying to make anything optimal -- make the most naive way that works, then refine from there. </p>
</li>
<li><p>Use abstractions (functions, objects) to encapsulate and structure ideas more easily & clearly. Any time you feel like you are writing the same code several times, replace it with a function or loop. Separate out reusable "support routines" from the code that represents the main ideas. </p>
</li>
<li><p>Comment the code and use good variable names -- you'll thank yourself in the future when you come back to it! (And anyone else looking at the code will thank you more -- remember research is about sharing!)</p>
</li>
<li><p>Take notes as you go. At any time you might have an idea of a different direction to explore -- you can only do one at once, so write them down! Even if they are just comments in the code.</p>
</li>
<li><p>Make many copies, saving a version (in Codepen you can do this via a Fork) for each minor milestone. If it goes wrong but in an interesting way (a happy accident), save a version of that too.</p>
</li>
</ul>
<hr>
<h1 id="week-3">Week 3</h1>
<p>Sep 26, 2023</p>
<ul>
<li><p>Reading list discussion</p>
</li>
<li><p>Review of code sketching</p>
</li>
</ul>
<hr>
<p>Topic: machine intelligence and artificial agents.</p>
<p>One of the most timely topics of focus today is that of machine learning and artificial intelligence, and particularly now the cohabitation of human/biological and machine agents and intelligences in the world. </p>
<p>For instance, York University recently established <a href="https://www.yorku.ca/research/cais/">The Center for AI & Society</a> organized research unit, and was awarded $80M from federal funding for the <a href="https://www.yorku.ca/research/connected-minds/">Connected Minds</a> program. See the <a href="https://www.yorku.ca/news/2023/04/28/york-university-leads-318-4m-first-of-kind-inclusive-next-gen-technology-research-initiative/">announcement here</a>. There will be many multidisciplinary projects funded through this, for which you might be hired as research assistants. There will be scholarships for graduate students (and post-doctroral research appointments) through this, to which you may apply. </p>
<p>What are the research questions, and especially, what can our field contribute? Where does this overlap or intersect with <em>your</em> interests? How will you articulate this?</p>
<hr>
<p>For the purposes of our DIGM5010 course: what are some of the <strong>foundations</strong> of our field that may inform this?</p>
<p><a href="agents.html">Tortoises, turtles, robot flocks and vehicle societies</a></p>
<!--
[Zoom recording](https://drive.google.com/file/d/1_4fOobVXYf6WecRKCWsi6b0j9EzCQzD6/view?usp=drive_link)
-->
<p><strong>References</strong></p>
<ul>
<li><a href="https://drive.google.com/drive/folders/1nUFDBRNpvKXp3-JiYwBIuN0a55T4vb-Y">Papert, Seymour A. Mindstorms (Excerpts)</a> </li>
<li><a href="https://drive.google.com/file/d/1FcBQEl6E3hvNy3q-ow4HaFn2jtOPaxvA">Braitenberg, Valentino. Vehicles. 1984</a></li>
<li><a href="https://tinlizzie.org/tinkertoy/">Alan Kay. Marvin Minsky & The Ultimate Tinkertoy</a></li>
<li><a href="https://www.red3d.com/cwr/steer/gdc99/">Craig Reynolds. Steering Behaviors For Autonomous Characters, Game Developers Conference. 1999</a></li>
</ul>
<hr>
<!--
Completing the Yellowtail
- [Zoom recording](https://drive.google.com/file/d/1YolHbf3uddSZOZ-taQPXe1pF25l5icMg/view?usp=drive_link)
<p class="codepen" data-height="520" data-default-tab="js,result" data-user="grrrwaaa" data-slug-hash="jOXYdMd?editors=0010" data-preview="true"><span><a href="https://codepen.io/grrrwaaa/pen/jOXYdMd?editors=0010">Open pen.</a></span></p><script async src="https://static.codepen.io/assets/embed/ei.js"></script>
-->
<hr>
<hr>
<h1 id="week-4">Week 4</h1>
<p>Oct 3, 2023</p>
<ul>
<li><p><a href="https://explorabl.es">Explorable Explanations</a></p>
<ul>
<li>For example, <a href="https://ncase.me/crowds/">The Wisdom and/or Madness of Crowds</a></li>
</ul>
</li>
<li><p><a href="steering.html">Steering: vehicles and flocks</a></p>
</li>
</ul>
<hr>
<p>Begin developing your readling list into an <strong>annotated bibliography</strong></p>
<hr>
<h2 id="annotated-bibliography">Annotated Bibliography</h2>
<ul>
<li>From your reading list, select at least 8 item to study in more careful detail as you create an <strong>Annotated Bibliography</strong>. <ul>
<li>Use skimming/speed reading and organization to identify those that are most interesting or most worthy of more detailed review; and which would constitute an adquate treatment of the topic. </li>
<li>Aim for diversity. Avoid using the same authors for the majority of the selection. Include distinct and opposing viewpoints if possible. </li>
<li>Use primary sources where possible (in particular avoid blog posts, news articles, etc.), unless the secondary source adds a significant new idea (in which case you may want to cite both).</li>
<li>Not everything has to be an academic paper, but ensure that at least 75% of your references are academic publications (conference articles, journal articles, etc.). </li>
</ul>
</li>
<li>Once your list is shortened, perform a deep read of each one, taking notes as you go. The annotation for each paper could typically be 200-500 words. <ul>
<li>I recommend highlighting PDFs but taking notes in a separate plain text document. </li>
<li>Don't note everything, focus on what the key points are to get a condensed overview of the whole paper. (A well-written paper makes one main point per paragraph, and not all points are significant.)<ul>
<li>Distinguish clearly between <ul>
<li>what is a summary of the paper, </li>
<li>what is a quotation from the paper (use quotation marks), </li>
<li>and what is your own thought in response (you could use (parentheses) or [square brackets] to indicate these). </li>
</ul>
</li>
<li>Note page numbers in the text document as you take notes. </li>
</ul>
</li>
<li>See <a href="https://spark.library.yorku.ca/wp-content/themes/glendonits-spark-20151125/resources/Annotated%20Bibliography%20Overview.pdf">York SPARK's guide to annotated bibliographies here</a>. </li>
<li>However, unlike the format and examples in that guide, I support and encourage bullet-point style summaries.</li>
<li>I also encourage you to copy out any specific quotations that you find significant, inspiring, or which neatly summarize the authors' points. </li>
</ul>
</li>
<li>After deep note-taking on each paper, read them again with your notes, and correct any mistakes or misunderstandings, amend your analyses, and note any new thoughts. This is your <strong>annotation</strong> for each paper. </li>
<li><a href="https://forms.gle/dw2CuCxeAnHWRJ2u6">You can submit the Annotated Reading list in this form, including</a><ul>
<li>The specific topic title or</li>
<li>The keywords or search terms</li>
<li>The research question/problem statement/abstract</li>
<li>Your initial Reading List</li>
<li>Your final Annotated Bibliography</li>
<li>Any meta-commentary on observations you found while researching the topic that are not specific to any one paper -- in particular, did you find a "gap" in the treatment of the topic that could be an important avenue for your own work?</li>
</ul>
</li>
<li>The final deadline for submission is <strong>Sunday Oct 13th</strong>.</li>
</ul>
<hr>
<p>Continuing code sketching, with turtles and mindstorms</p>
<!--
- [Zoom recording](https://drive.google.com/file/d/1_yZch7K50LojaVojQeUDublwyVCf5GAh/view?usp=sharing)
<p class="codepen" data-height="520" data-default-tab="js,result" data-user="grrrwaaa" data-slug-hash="mdaoRKa" data-preview="true"><span><a href="https://codepen.io/grrrwaaa/pen/mdaoRKa">Open pen.</a></span></p><script async src="https://static.codepen.io/assets/embed/ei.js"></script><p class="codepen" data-height="520" data-default-tab="js,result" data-user="grrrwaaa" data-slug-hash="LYMayEE" data-preview="true"><span><a href="https://codepen.io/grrrwaaa/pen/LYMayEE">Open pen.</a></span></p><script async src="https://static.codepen.io/assets/embed/ei.js"></script><p class="codepen" data-height="520" data-default-tab="js,result" data-user="grrrwaaa" data-slug-hash="PoXLmVe" data-preview="true"><span><a href="https://codepen.io/grrrwaaa/pen/PoXLmVe">Open pen.</a></span></p><script async src="https://static.codepen.io/assets/embed/ei.js"></script>
-->
<hr>
<h1 id="week-5">Week 5</h1>
<p>Oct 10 </p>
<ul>
<li><p>Review of schedule for remainder of semester</p>
<ul>
<li>The research paper (which can be a continuation of your bibliography and/or codework)<ul>
<li>The final submission</li>
<li>The call for papers</li>
<li>The peer review</li>
</ul>
</li>
<li>The video tutorial (which can support your paper)</li>
</ul>
</li>
<li><p>Complete your annotated bibliography</p>
</li>
<li><p><strong>Annotated bibliographies due Sunday Oct 13th</strong></p>
</li>
<li><p>Next week is reading week -- a perfect time for you work on your paper's first draft! </p>
</li>
<li><p>Sharing & discussing work so far</p>
</li>
<li><p>1-on-1 Q&As</p>
</li>
<li><p>Continuing exploring code sketching</p>
</li>
</ul>
<hr>
<hr>
<h1 id="week-6">Week 6</h1>
<p>[Reading Week]</p>
<ul>
<li>Work on your paper draft for the peer review session</li>
</ul>
<hr>
<hr>
<h1 id="week-7">Week 7</h1>
<p>Oct 24, 2023</p>
<ul>
<li>Sharing & discussing, writing & code</li>
</ul>
<!--
---
[Zoom recording](https://yorku.zoom.us/rec/share/ydBsTO_cShKJr6m4HSosOmmj0JPosbTi1KnZ7rcp16O1mBGwYbFpEUJsuCvRkypY.9L3Y1RsmL0YcwucL)
-->
<ul>
<li>Complete your paper draft. It <strong>must be submitted before next week's class</strong> - <a href="https://docs.google.com/forms/d/e/1FAIpQLSecdNzeUZRAiSQcIViboyWTCAxnuyAfphUGJGKy91H9ZKDDPg/viewform?usp=sf_link">submit the paper with this form</a></li>
</ul>
<hr>
<hr>
<h1 id="week-8">Week 8</h1>
<p>Oct 31, 2023</p>
<p><strong>Make sure your paper is submitted to the link above before this class!!</strong></p>
<ul>
<li>Peer review discussion</li>
</ul>
<p>What qualifies as <em>good</em> research? One way of knowing this is to look at how research is <em>reviewed</em>. Again, most grant appplications, but also journals and conference review bodies often publish guidelines for reviewers. These are the criteria by which your work will be evaluated. </p>
<ul>
<li><a href="https://www.wikihow.com/Review-a-Journal-Article">Wikihow</a> to review an article!</li>
<li>Guidelines from <a href="https://www.springer.com/authors/manuscript+guidelines?SGWID=0-40162-6-1261021-0#:~:text=Reviews%20should%20be%20conducted%20fairly,less%20useful%20to%20your%20field.">Springer</a>, <a href="https://authorservices.wiley.com/Reviewers/journal-reviewers/how-to-perform-a-peer-review/step-by-step-guide-to-reviewing-a-manuscript.html">Wiley</a>, <a href="https://www.elsevier.com/reviewers/how-to-review">Elsevier</a></li>
</ul>
<p>These are general guidelines, but practices and cultures of value can differ very greatly between different research communities -- and we are often transdiscplinary... </p>
<ul>
<li><p>Past reviews</p>
</li>
<li><p><strong>During class</strong>:</p>
<ul>
<li>Submit your <a href="#peer-review">Peer reviews</a> to <a href="https://docs.google.com/forms/d/e/1FAIpQLSeLBcwJXSRJCwpN54hRq7j1hvmryhlkrrE4OqGqazs43qIc9Q/viewform?usp=sf_link">the peer review form here</a></li>
</ul>
</li>
</ul>
<hr>
<h2 id="peer-review">Peer Review</h2>
<p>Recall our slides on <a href="research.html#/36">reviewing research</a></p>
<p>We will run an 'internal review' process, emulating what is frequently done in conference submission review processes. Typically this means:</p>
<ul>
<li>A call for work (papers, demonstrations, artworks, panels, etc.) is made public.</li>
<li>Authors submit a draft or extended abstract of a paper (or a proposal for an artwork etc.) by a certain deadline for review, usually using an online interface. </li>
<li>Reviews are most often performed "blind" or "double-blind" (that is, reviewers and authors are anonymized).</li>
<li>Each draft is sent to a handful of reviewers. Members of the review body are usually made up of many previous authors at the conferene. Though a conference may have hundreds of submissions, usually reviewers only have a handful assigned to them. </li>
<li>Reviewers complete a review of the submission, usually using an online interface, by a certain deadline. Sometimes a meta-review is performed by a lead jury member of the conference to synthesize the reviews and reach a verdict on acceptance. Sometimes submissions are accepted, sometimes rejected, sometimes accepted but on different terms (e.g. long paper submission may be accepted as a short paper, with requirement to reduce length.)</li>
<li>These reviews are sent back to authors, along with the accept/reject verdict. Authors of accepted papers must act upon any requirements or corrections identified by reviewers, and may follow further recommendations. Then the final submission is resubmitted with these changes by a new deadline (usually very shortly after receiving reviews).</li>
</ul>
<p><strong>For our purposes, you will act as both author and reviewer: each of you will act as reviewers for the other students' submissions.</strong></p>
<p>For general review guidelines, <a href="https://www.wikihow.com/Review-a-Journal-Article">see here</a> and <a href="https://authorservices.wiley.com/Reviewers/journal-reviewers/how-to-perform-a-peer-review/step-by-step-guide-to-reviewing-a-manuscript.html">here</a> or <a href="https://www.elsevier.com/reviewers/how-to-review">here</a>, or <a href="https://www.springer.com/authors/manuscript+guidelines?SGWID=0-40162-6-1261021-0#:~:text=Reviews%20should%20be%20conducted%20fairly,less%20useful%20to%20your%20field.">here</a>. Here are key points:</p>
<blockquote>
<p>"The purpose of peer review is to improve the quality of the manuscript under review, and of the material that is eventually published. Conscientious peer review is a time-consuming task but is essential to assure the quality of scientific journals." </p>
</blockquote>
<blockquote>
<p>Reviews should be conducted fairly and objectively. Personal criticism of the author is inappropriate. If the research reported in the manuscript is flawed, criticize the science, not the scientist. Criticisms should be objective, not merely differences of opinion, and intended to help the author improve his or her paper.</p>
</blockquote>
<blockquote>
<p>Comments should be constructive and designed to enhance the manuscript. You should consider yourself the authors’ mentor. Make your comments as complete and detailed as possible. Express your views clearly with supporting arguments and references as necessary. Include clear opinions about the strengths, weaknesses and relevance of the manuscript, its originality and its importance to the field. Specific comments that cite line numbers are most helpful. </p>
</blockquote>
<blockquote>
<p>Begin by identifying the major contributions of the paper. What are its major strengths and weaknesses, and its suitability for publication? Please include both general and specific comments bearing on these questions, and emphasize your most significant points. Support your general comments, positive or negative, with specific evidence.</p>
</blockquote>
<blockquote>
<p>Is the aim clearly stated? Do the title, abstract, key words, introduction, and conclusions accurately and consistently reflect the major point(s) of the paper? Is the writing concise, easy to follow, and interesting, without repetition?</p>
</blockquote>
<blockquote>
<p>Are the methods appropriate, sound, current, and described clearly enough that the work could be repeated by someone else? Is the research ethical and have the appropriate approvals/consent been obtained? Are appropriate analyses used? Are they sufficiently justified and explained? Are statements of significance justified? Are results supported by data? Are any of . the results counterintuitive? Are the conclusions supported by the data presented?</p>
</blockquote>
<blockquote>
<p>Are the references cited the most appropriate to support the manuscript? Are citations provided for all assertions of fact not supported by the data in this paper? Are any key citations missing? </p>
</blockquote>
<blockquote>
<p>Should any portions of the paper should be expanded, condensed, combined, or deleted? </p>
</blockquote>
<p>As a structure, our review is based on materials as used by the <a href="https://s2023.siggraph.org/program/art-papers/">SIGGRAPH Art Papers</a> review body. That process was double-blind (both authors & reviewers anonymized), but since we know each other, we'll run our review single-blind (authors anonymized). Each of you will be randomly assigned up to 3 papers to review. </p>
<hr>
<hr>
<h1 id="week-9">Week 9</h1>
<p>Nov 7, 2023</p>
<ul>
<li><p><strong>Peer reviews received</strong> </p>
<ul>
<li>Review outcome & process discussion. </li>
<li>Group and/or 1-on-1 discussion for final paper</li>
</ul>
</li>
<li><p>Possible topics: </p>
<ul>
<li>An introduction to git?</li>
<li>An introduction to Node.js?</li>
</ul>
</li>
</ul>
<h2 id="final-paper">Final Paper</h2>
<ol>
<li>The final paper continues from the <a href="#annotated-bibliography%5B">Literature Review</a>, and responds to the <a href="#the-call-for-papers">Call for Papers</a>. <ul>
<li>Find a few other papers online that have similar focus, and analyze their structure as a guide.</li>
<li>Find related conferences/symposia/journals/etc. to contrast other papers as well as submission and review criteria. </li>
<li>You should identify at least one conference/festival/other appropriate venue to submit your research or research-creation. Investigate papers submitted to this in past years, and the submission requirements and review criteria. </li>
<li>Document these findings in your journal.</li>
</ul>
</li>
<li>Papers can range from 2000-5000 words. You have two choices for publication format. <ol>
<li>A traditional conference-style paper. Papers must follow the standard template (adapted from ISEA2024) available <a href="https://docs.google.com/document/d/1WZkAN9oaT8pvVVKBRwRRgbwnuKmAU0JJ/edit?usp=share_link&ouid=112275914788197824145&rtpof=true&sd=true">here</a> or <a href="https://www.acm.org/binaries/content/assets/publications/taps/acm_submission_template.docx">here</a></li>
<li>A very modern, online-first academic article. That is, one designed to be read online, with at least some active components, rather than primarily on paper. The notion of publishing in academia has been rapidly changing, and these changes accelerated during the pandemic.<ul>
<li>See <a href="https://www.pubpub.org">https://www.pubpub.org</a> for an example of a modern online-first collaborative publishing venue. Many conferences in recent years have moved over to this format (e.g. NIME, ICLC). </li>
<li>See <a href="https://distill.pub">https://distill.pub</a> for an example of a modern, web-based peer-reviewed journal with embedded visualizations and interactive components. </li>
<li>See <a href="https://jar-online.net">https://jar-online.net</a> for a different example more focused on art theory & practice.</li>
<li>Alternatively, create your own using github, github-pages, html5/css/js, markdown/pandoc, D3.js, webgl or similar. </li>
<li>Whichever platform is used, the paper should meet academic standards of relevance, clarity of writing, structure, balanced and evidence-based argument, critical thinking, and appropriate level and kinds of academic references. </li>
</ul>
</li>
</ol>
</li>
<li>Post your final paper online to our final submission form here: <a href="https://forms.gle/zHPbsvSrtoA16xzAA">https://forms.gle/zHPbsvSrtoA16xzAA</a></li>
</ol>
<p>Please submit your final papers by December 8th, thank you!!</p>
<hr>
<hr>
<h1 id="week-10">Week 10</h1>
<p>Nov 14, 2023</p>
<ul>
<li><p>Possible topics: </p>
<ul>
<li>An introduction to git?</li>
<li>An introduction to Node.js?</li>
</ul>
</li>
<li><p><strong>For next week</strong>:</p>
<ul>
<li>Submit your <a href="#video-tutorial">Video Tutorial</a></li>
</ul>
</li>
</ul>
<hr>
<h2 id="video-tutorial">Video Tutorial</h2>
<p>Research is about <em>sharing</em>. Sometimes, that requires sharing <em>how</em>. </p>
<ol>
<li>Create a video-based tutorial (roughly 10-20mins) to introduce a technical topic.<ul>
<li>It could be an introduction to a platform we are not covering in class</li>
<li>or an exploration of a library/API or SDK etc. in Javascript</li>
<li>or alternatively, it could be a tutorial on a technique or algorithm or mechanism or a part of mathematics etc.</li>
</ul>
</li>
<li>Whichever you choose, it should cover both of: <ul>
<li>introducing the key concepts, the unusual and interesting parts, and related work</li>
<li>deep-dive developing a demonstration (coding a sketch) from the ground up, explaining via voiceover what you are doing at each step and why. </li>
</ul>
</li>
<li>You are welcome to use any screen-recording tool. Zoom is OK, Camtasia is pretty fancy, OBS is very powerful and free. Whatever you use, I recommend doing a few takes. Sometimes the first take is the best, sometimes the third. You are welcome to edit them together if it makes sense. But don't lose time making it 'slick' -- that's not the point here. People like <a href="https://www.youtube.com/channel/UCvjgXvBlbQiydffZU7m1_aw">Dan Shiffman</a> or <a href="https://www.youtube.com/channel/UCYO_jab_esuFRV4b17AJtAw">3Blue1Brown</a> do make beautiful videos but the most important part is that they convey <em>what</em> is interesting/valuable/powerful/etc. about the technical system/tool/algorithm/etc by explaining <em>how</em> it works. </li>
</ol>
<hr>
<hr>
<h1 id="week-11">Week 11</h1>
<p>Nov 21, 2023</p>
<ul>
<li><strong>Video tutorials due</strong><ul>
<li><a href="https://docs.google.com/presentation/d/1L8oUYKt1oO6vrxgB36ArqI_stz8U0TyHMAWhnPjafPs/edit?usp=sharing">Add your video tutorial to the slides here</a></li>
</ul>
</li>
</ul>
<p>One-on-one guidance for papers & presentations preparation</p>
<hr>
<hr>
<h1 id="week-12">Week 12</h1>
<p>Nov 28, 2023</p>
<p><strong>Final presentations</strong></p>
<p>We have about 10-15 minutes per presentation, plus 5 minutes for questions & discussion! </p>
<!--
[Zoom recording](https://yorku.zoom.us/rec/share/99TfEFAgXaklPBZdmx9u5TRDJGjn28DUPJIQZvnImOzhsTCX2GCPkZIAg3N8AhOQ.n4PrI8uAqSOaHr0f)
-->
<hr>
<p><a href="https://docs.google.com/forms/d/e/1FAIpQLSdUCztWAi-z4x5r_RTXhsWnvqiw46hPZRIh7eqChm7FGoFGqQ/viewform?usp=sf_link">You can submit all of your codepen sketches as we go along through this form</a>. </p>
<!--
Research step 1: survey the field / [literature review](#literature-review-1)
---
# Week 4
Oct 5, 2023
Places to look:
- [3Blue1Brown](https://www.youtube.com/channel/UCYO_jab_esuFRV4b17AJtAw)
- [Desmos](https://www.desmos.com/calculator) is a quick online grapher
- [Math as code](https://github.com/Jam3/math-as-code) -- how to translate between math notation and JS code
- [Explorable Explanations](https://explorabl.es) -- far more than math!
[Microworlds](vehicles.html) - [Turtle talk](https://codepen.io/grrrwaaa/pen/KKqJGQK?editors=0010)
**Homework**: choose an Explorable Explanation that relates to your research topic. For practice, try to reconstruct part of the explorable system!
## Literature Review 2
- From your reading list, select at least 8 of them to study in more careful detail as you create an **Annotated Bibliography**.
- Use skimming/speed reading and organization to identify those that are most interesting or most worthy of more detailed review; and which would constitute an adquate treatment of the topic.
- Aim for diversity. Avoid using the same authors for the majority of the selection. Include distinct and opposing viewpoints if possible.
- Use primary sources where possible (in particular avoid blog posts, news articles, etc.), unless the secondary source adds a significant new idea (in which case you may want to cite both).
- Not everything has to be an academic paper, but ensure that at least 75% of your references are academic publications (conference articles, journal articles, etc.).
- Once your list is shortened, perform a deep read of each one, taking notes as you go. The annotation for each paper could typically be 200-500 words.
- I recommend highlighting PDFs but taking notes in a separate plain text document.
- Don't note everything, focus on what the key points are to get a condensed overview of the whole paper. (A well-written paper makes one main point per paragraph, and not all points are significant.)
- Distinguish clearly between
- what is a summary of the paper,
- what is a quotation from the paper (use quotation marks),
- and what is your own thought in response (you could use (parentheses) or [square brackets] to indicate these).
- Note page numbers in the text document as you take notes.
- See [York SPARK's guide to annotated bibliographies here](https://spark.library.yorku.ca/wp-content/themes/glendonits-spark-20151125/resources/Annotated%20Bibliography%20Overview.pdf).
- However, unlike the format and examples in that guide, I support and encourage bullet-point style summaries.
- I also encourage you to copy out any specific quotations that you find significant, inspiring, or which neatly summarize the authors' points.
- After deep note-taking on each paper, read them again with your notes, and correct any mistakes or misunderstandings, amend your analyses, and note any new thoughts. This is your **annotation** for each paper.
- Post the results into your journal:
- The specific topic title or
- The keywords or search terms
- The research question/problem statement/abstract
- Your initial Reading List
- Your final Annotated Bibliography
- Any meta-commentary on observations you found while researching the topic that are not specific to any one paper -- in particular, did you find a "gap" in the treatment of the topic that could be an important avenue for your own work?
For example, [here's](https://alicelab.world/digm5010/vehicles.html#annotated-notes) my own annotated bibliography notes on Seymour Papert's Mindstorms.
| Sep 29: [Week 3](#week-3) | Practice/Review | [Lit Review step 1](#literature-review-1) |
| Oct 06: [Week 4](#week-4) | Annotated Bibliographies
[Explorable Explanations](https://explorabl.es)
| Oct 13: [Reading Week](#reading-week) | | (work on Lit Review step 2) |
| Oct 20: [Week 5](#week-5) | What to do next? (Markov, [Time](time.html)) | [Lit Review step 2](#literature-review-2) | [Oulipo Selections](https://drive.google.com/drive/folders/1nUFDBRNpvKXp3-JiYwBIuN0a55T4vb-Y)
| Oct 27: [Week 6](#week-6) | Project work | [Practice (Journal)](#online-journal--practice-studies) | [Mathews: An Acoustic Compiler](http://ia601505.us.archive.org/7/items/bstj40-3-677/bstj40-3-677.pdf)
| Nov 03: [Week 7](#week-7) | [Time and sound](time.html) | [Paper-project abstract](#final-paper) |
| Nov 10: [Week 8](#week-8) | Papers focus | [Video tutorial](#video-tutorial) |
| Nov 17: [Week 9](#week-9) | Peer reviewing | [Final paper](#final-paper) [draft for review](#peer-review) |
| Nov 24: [Week 10](#week-10) | [Time and sound](time.html): gen | |
| Dec 01: [Week 11](#week-11) | | Presentation |
| Dec 10: | | [Final Paper](#final-paper) |
*-->
<!--
(Oct 12 No class -- York Reading Week)
Oct 19, 2023
Oct 26, 2023
Nov 2, 2023
Nov 9, 2023
Nov 16, 2023
Nov 23, 2023
Nov 30, 2023
Data:
characters, oulipo to gpt
code is also data
pixels, shaders,
samples, signals
data art, viz, open data, ...
-----
Implementing Vehicles. Now we need vectors and forces.
**Make:** Extend / mutate [the code we built in class](https://codepen.io/grrrwaaa/pen/mdwqLqX?editors=0010)
## Online Journal & Practice Studies
You will create an online journal. If you set up a github repository, you can use the **wiki** feature as a very simple, markdown-flavoured online note taker; or simply create markdown files in the github repository itself.
Every week, please post an update on your journal, capturing the work you have been doing. The journal as a whole will serve as a documentation of your development in the course. For practice based work, posts should include video, screenshots, embedded scripts, links to github code, or some other concete material. Posts don't need to be long, but should focus on key questions and/or insights discovered along the way. What surprised you? Did you surprise yourself? What are the key challenges you found? We will bring these into the discussion every week.
This weekly post should include practice studies, such as links to (or embeds of) Codepen scripts. Every week I will share some prompts for these studies. These studies can be relatively simple but should demonstrate something you have learned or document an investigation you have made. Make, make make!
As the course progresses, this journal will capture your progress in development towards the major assignments, which will also be added to the journal.
-----
## Week 2
[What is research](research.html)?
Research step 1: survey the field / [literature review](#literature-review-1)
[From Vehicles to Mindstorms](vehicles.html)
Sharing code sketches (drawing, vehicles)
[**Zoom recording**](https://yorku.zoom.us/rec/share/DPZrN3q7kWcU6weYwy_n_qQxBMh2s_ck-SRUeEgJTbGsB4kGydGFQSH1C3uZ9ZXv.Uy0rj9H84_W1jUAu)
Please remember to **email me** with a link to your online journal, including the sketches and notes taken so far, and your literature review/reading list as you develop it!
## Literature Review 1
You will investigate a **topic** that ideally intersects this year's topic/theme (AI) with something of value to your own research goals. Good research always begins by seeking out key papers and other relevant research resources.
- Some investigative tips:
- Use Wikipedia to identify **keywords or terms**, questions and issues, foundational publications and controversies, etc. This can also help to make your search more narrow/specific. Look for the edges of a body of research. Wikipedia is an excellent network of conceptual nodes (but also a potential rabbithole). But remember that it is an encyclopedia, and should be used mainly as a guide map.
- Use these terms and publications in [Google Scholar](https://scholar.google.com/) and other academic search engines to find for papers that address the questions and issues. Follow `cited by` and `related articles` trails to find new leads. Aim to find the most significant (qualitatively & quantitatively) papers. You should be aiming for a collection of 25-50 potentially interesting papers on the topic at this point.
- At the same time, look for conferences or journals that are more specific to your topic, and see if they have collections of proceedings online to browse through.
- Not all papers are available as PDFs online. You might be able to find them via [York Libraries](https://www.library.yorku.ca/web/bbl/e-resources/) or also communities like [ResearchGate](https://www.researchgate.net/), but do not let this roadblock your progress -- find alternatives to work from instead.
- At this point you may be able to formulate a first draft of a title of the topic or area, perhaps even a key question or problem statement; but don't worry at this stage if you haven't yet.
- Collect this list as a **Reading List**, formatted with MLA, APA or Chicago style as you prefer (but keep it consistent) -- again, Scholar can help source these, but be aware that not all entries are complete. Any non-academic/non-paper references may need special citation styles (e.g. URLs, published films or audio recordings, etc.)
- Post the results into your journal:
- The specific topic title or
- The keywords or search terms
- The research question/problem statement/abstract
- Your initial Reading List
- [York off-campus library access](https://www.library.yorku.ca/web/ask-services/printing-and-computing/computing/off-campus-access/)
- [York VPN links](http://www.yorku.ca/computing/vpn-choice.html)
-----
## Week 3
Practice / Review
Places to look:
- [3Blue1Brown](https://www.youtube.com/channel/UCYO_jab_esuFRV4b17AJtAw)
- [Desmos](https://www.desmos.com/calculator) is a quick online grapher
- [Math as code](https://github.com/Jam3/math-as-code) -- how to translate between math notation and JS code
- [Explorable Explanations](https://explorabl.es) -- far more than math!
[Microworlds](vehicles.html) - [Turtle talk](https://codepen.io/grrrwaaa/pen/KKqJGQK?editors=0010)
[**Zoom recording**](https://yorku.zoom.us/rec/share/ARbKcbdmZykOw61DZ12Uq5W2ALgRpQN8Vso22emu57jmsf4Sfmwp1x0cCra6S_Si.JVycVe4Oy80CPDRk)
**Homework**: choose an [Explorable Explanation](https://explorabl.es) that relates to your research topic. For practice, try to reconstruct part of the explorable system!
-----
## Week 4
- Sharing Explorable Explanations!
- [My fireflies](https://codepen.io/grrrwaaa/pen/rNwXydw?editors=0010)
**[Zoom Recording](https://yorku.zoom.us/rec/share/LGURDi70u4a3U4q7ri7IUg89xNPcf5MP00LQ3d4PbGvq7L4mOBSR8-4WGYtpt54Z.Xi-Dv-jrUnppTFkk)*
## Literature Review 2
- From your reading list, select at least 8 of them to study in more careful detail as you create an **Annotated Bibliography**.
- Use skimming/speed reading and organization to identify those that are most interesting or most worthy of more detailed review; and which would constitute an adquate treatment of the topic.
- Aim for diversity. Avoid using the same authors for the majority of the selection. Include distinct and opposing viewpoints if possible.
- Use primary sources where possible (in particular avoid blog posts, news articles, etc.), unless the secondary source adds a significant new idea (in which case you may want to cite both).
- Not everything has to be an academic paper, but ensure that at least 75% of your references are academic publications (conference articles, journal articles, etc.).
- Once your list is shortened, perform a deep read of each one, taking notes as you go. The annotation for each paper could typically be 200-500 words.
- I recommend highlighting PDFs but taking notes in a separate plain text document.
- Don't note everything, focus on what the key points are to get a condensed overview of the whole paper. (A well-written paper makes one main point per paragraph, and not all points are significant.)
- Distinguish clearly between
- what is a summary of the paper,
- what is a quotation from the paper (use quotation marks),
- and what is your own thought in response (you could use (parentheses) or [square brackets] to indicate these).
- Note page numbers in the text document as you take notes.
- See [York SPARK's guide to annotated bibliographies here](https://spark.library.yorku.ca/wp-content/themes/glendonits-spark-20151125/resources/Annotated%20Bibliography%20Overview.pdf).
- However, unlike the format and examples in that guide, I support and encourage bullet-point style summaries.
- I also encourage you to copy out any specific quotations that you find significant, inspiring, or which neatly summarize the authors' points.
- After deep note-taking on each paper, read them again with your notes, and correct any mistakes or misunderstandings, amend your analyses, and note any new thoughts. This is your **annotation** for each paper.
- Post the results into your journal:
- The specific topic title or
- The keywords or search terms
- The research question/problem statement/abstract
- Your initial Reading List
- Your final Annotated Bibliography
- Any meta-commentary on observations you found while researching the topic that are not specific to any one paper -- in particular, did you find a "gap" in the treatment of the topic that could be an important avenue for your own work?
For example, [here's](https://alicelab.world/digm5010/vehicles.html#annotated-notes) my own annotated bibliography notes on Seymour Papert's Mindstorms.
## Reading Week
Work on your annotated bibliography and your project!
-----
## Week 5
- News: [AI:Talks series in Digital Media](ai_talks.pdf)
- The question at the heart of an automoton: "what to do next?"
- State machines, [Markov processes](https://en.wikipedia.org/wiki/Markov_chain); text analysis and resynthesis
- Remember [Turtle Talk](https://codepen.io/grrrwaaa/pen/KKqJGQK)
- [Time and sound](time.html)
- Scripts:
- [Markov text generator](https://codepen.io/grrrwaaa/pen/YzxGxWv)
- [Markov text generator 2](https://codepen.io/grrrwaaa/pen/YzxWRNx)
**[Zoom Recording](hhttps://yorku.zoom.us/rec/share/aK1K9GIV1o7dndxYPUPEDlcjmyedVQM3JgBhB6t9dJV2iVEz2FK_Rpy7w2AZLdQ.qKbhoPp028yMmKHK)**
- [An example JS library for advanced Markov-driven text analysis & resynthesis](https://github.com/dhowe/ritajs#a-simple-sketch)
-----
## Week 6
- Project work
Due next week: [Paper-project abstract](#final-paper)
-----
## Week 7
- [Paper-project abstracts](#final-paper) & discussion
- [Time and sound](time.html) continued
- Music-N, instruments and sequences
- [In class script](https://codepen.io/grrrwaaa/pen/oNepMZz)
- [Pre-baked script](https://codepen.io/grrrwaaa/pen/XWajXXM)
Due next week: [Video Tutorial](#video-tutorial)
**[Zoom recording](https://yorku.zoom.us/rec/share/WEje6R6vErTm9yfs_Kkg-qRCfIzq11u66eWiQMS1qfMPS5DoiOwRvSCaeztH0iRd.RtHLq4a01H66xe2O)**
## Video Tutorial
Research is about *sharing*. Sometimes, that requires sharing *how*.
1. Create a video-based tutorial (roughly 10-20mins) to introduce a technical topic.
- It could be an introduction to a platform we are not covering in class
- or an exploration of a library/API or SDK etc. available for one of our platforms
- or alternatively, it could be a tutorial on a technique or algorithm or mechanism or a part of mathematics etc.
2. Whichever you choose, it should cover both of:
- introducing the key concepts, the unusual and interesting parts, and related work
- deep-dive developing a demonstration (coding a sketch) from the ground up, explaining via voiceover what you are doing at each step and why.
3. You are welcome to use any screen-recording tool. Zoom is OK, Camtasia is pretty fancy, OBS is very powerful. Whatever you use, I recommend doing a few takes. Sometimes the first take is the best, sometimes the third. You are welcome to edit them together if it makes sense. But don't lose time making it 'slick' -- that's not the point here. People like Dan Shiffman or 3Blue1Brown do make beautiful videos but the most important part is that they convey *what* is interesting/valuable/powerful/etc. about the technical system/tool/algorithm/etc by explaining *how* it works.
-----
## Week 8
- Discussion about abstracts, final papers, and
- Peer review preview:
- Sharing past reviews (and reviewing)
- Example: SIGGRAPH Art Papers
- [The form](https://forms.gle/pWesCCBQkeMKWX6y7)
- Video tutorials
[Final paper](#final-paper) [draft for review](#peer-review)
-----
## Week 9
**[Zoom recording](https://yorku.zoom.us/rec/share/tcnLkfrrxxapfsjmWn15gcox0LM-MYQg8BQVgs3iCLqsFL82eqkj7oa1ruGgeIC1.erXQvut-v6uZlJDP)**
-----
## Week 10
- Time & Sound: gen~
- **[Zoom recording](https://yorku.zoom.us/rec/share/5qPQPGpqXj3_Z0ZKsrRIQ80POnrvI0IPJNYPbGFl6CHngtp2ikOWHgf4QInXwsu4.xCE8R0lMZZfOKCwr)**
-->
<hr>
<footer>DIGM5010 2021-22</footer>
</body>
<script src="js/connect.js"></script>
</html>