Skip to content

Commit 6461031

Browse files
committed
update
1 parent fb19e13 commit 6461031

File tree

17 files changed

+803
-3012
lines changed

17 files changed

+803
-3012
lines changed
Lines changed: 139 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,139 @@
1+
{
2+
"cells": [
3+
{
4+
"cell_type": "markdown",
5+
"id": "84f984f3",
6+
"metadata": {
7+
"editable": true
8+
},
9+
"source": [
10+
"<!-- HTML file automatically generated from DocOnce source (https://github.com/doconce/doconce/)\n",
11+
"doconce format html CNNandmore.do.txt -->\n",
12+
"<!-- dom:TITLE: Project 1 CNNs, RNNs, Autoencoders and more -->"
13+
]
14+
},
15+
{
16+
"cell_type": "markdown",
17+
"id": "0882d07d",
18+
"metadata": {
19+
"editable": true
20+
},
21+
"source": [
22+
"# Project 1 CNNs, RNNs, Autoencoders and more\n",
23+
"**[FYS5429/9429](https://www.uio.no/studier/emner/matnat/fys/FYS5429/index-eng.html), Advanced machine learning and data analysis for the physical sciences, University of Oslo, Norway**\n",
24+
"\n",
25+
"Date: **Spring semester 2026, deadline March 20**"
26+
]
27+
},
28+
{
29+
"cell_type": "markdown",
30+
"id": "5199227c",
31+
"metadata": {
32+
"editable": true
33+
},
34+
"source": [
35+
"## Discriminative methods\n",
36+
"\n",
37+
"This project explores different discriminative methods, starting with\n",
38+
"standard neural networks, then moving to Comvolutional NNs (CNNs) or\n",
39+
"Recurrent NNs (RNNs), Autoencoders and/or Graphical NNs (GNNs). It\n",
40+
"allows also for a smooth transition to generative methods like\n",
41+
"Boltzmann machines, VAEs, GANs and Diffusion models. These methods are\n",
42+
"the topic of the second project."
43+
]
44+
},
45+
{
46+
"cell_type": "markdown",
47+
"id": "6d5f8ddc",
48+
"metadata": {
49+
"editable": true
50+
},
51+
"source": [
52+
"### Images and more\n",
53+
"\n",
54+
"A data set which many of you are familiar with is the MNIST set of\n",
55+
"handwritten numbers, see\n",
56+
"<https://en.wikipedia.org/wiki/MNIST_database>. Here you can\n",
57+
"study this data set with NNs, CNNs and eventually autoencoders or\n",
58+
"GNNs. For project 2 you could continue with the same data set and\n",
59+
"explore generative methods. You can obviously replace this data set\n",
60+
"with other images, such as images from modeling of phase transitions\n",
61+
"in physical systems, see <https://www.arxiv.org/abs/2501.05547> or\n",
62+
"other data sets of your choice."
63+
]
64+
},
65+
{
66+
"cell_type": "markdown",
67+
"id": "4c485860",
68+
"metadata": {
69+
"editable": true
70+
},
71+
"source": [
72+
"### Time series\n",
73+
"\n",
74+
"Another frequently occuring type of data are so-called time\n",
75+
"series. Here again you can start with NNs, move over to RNNs and\n",
76+
"autoencoders. Similarly, for project 2, you can include VAEs,\n",
77+
"Diffusion models or other generative methods. At the end you will have\n",
78+
"studied a broad set of deep learning methods, allowing you thereby to\n",
79+
"assess their pros and cons.\n",
80+
"\n",
81+
"Feel free to develop own codes or use libraries like TensorFlow and/or PyTorch."
82+
]
83+
},
84+
{
85+
"cell_type": "markdown",
86+
"id": "3b7a5b34",
87+
"metadata": {
88+
"editable": true
89+
},
90+
"source": [
91+
"## Introduction to numerical projects\n",
92+
"\n",
93+
"Here follows a brief recipe and recommendation on how to write a report for each\n",
94+
"project.\n",
95+
"\n",
96+
" * Give a short description of the nature of the problem and the eventual numerical methods you have used.\n",
97+
"\n",
98+
" * Describe the algorithm you have used and/or developed. Here you may find it convenient to use pseudocoding. In many cases you can describe the algorithm in the program itself.\n",
99+
"\n",
100+
" * Include the source code of your program. Comment your program properly.\n",
101+
"\n",
102+
" * If possible, try to find analytic solutions, or known limits in order to test your program when developing the code.\n",
103+
"\n",
104+
" * Include your results either in figure form or in a table. Remember to label your results. All tables and figures should have relevant captions and labels on the axes.\n",
105+
"\n",
106+
" * Try to evaluate the reliabilty and numerical stability/precision of your results. If possible, include a qualitative and/or quantitative discussion of the numerical stability, eventual loss of precision etc.\n",
107+
"\n",
108+
" * Try to give an interpretation of you results in your answers to the problems.\n",
109+
"\n",
110+
" * Critique: if possible include your comments and reflections about the exercise, whether you felt you learnt something, ideas for improvements and other thoughts you've made when solving the exercise. We wish to keep this course at the interactive level and your comments can help us improve it.\n",
111+
"\n",
112+
" * Try to establish a practice where you log your work at the computerlab. You may find such a logbook very handy at later stages in your work, especially when you don't properly remember what a previous test version of your program did. Here you could also record the time spent on solving the exercise, various algorithms you may have tested or other topics which you feel worthy of mentioning."
113+
]
114+
},
115+
{
116+
"cell_type": "markdown",
117+
"id": "306bdab8",
118+
"metadata": {
119+
"editable": true
120+
},
121+
"source": [
122+
"## Format for electronic delivery of report and programs\n",
123+
"\n",
124+
"The preferred format for the report is a PDF file. You can also use DOC or postscript formats or as an ipython notebook file. As programming language we prefer that you choose between C/C++, Fortran2008 or Python. The following prescription should be followed when preparing the report:\n",
125+
"\n",
126+
" * Send us an email in order to hand in your projects with a link to your GitHub/Gitlab repository.\n",
127+
"\n",
128+
" * In your GitHub/GitLab or similar repository, please include a folder which contains selected results. These can be in the form of output from your code for a selected set of runs and input parameters.\n",
129+
"\n",
130+
"Finally, \n",
131+
"we encourage you to collaborate. Optimal working groups consist of \n",
132+
"2-3 students. You can then hand in a common report."
133+
]
134+
}
135+
],
136+
"metadata": {},
137+
"nbformat": 4,
138+
"nbformat_minor": 5
139+
}
195 Bytes
Binary file not shown.

0 commit comments

Comments
 (0)