## Description

## Defining the data sets to analyze yourself

For project 3, you can propose own data sets that relate to your research interests or just use existing data sets from say

The approach to the analysis of these new data sets should follow to a large extent what you did in projects 1 and 2. That is:

- Whether you end up with a regression or a classification problem, you should employ at least two of the methods we have discussed among
**linear regression (including Ridge and Lasso)**,**Logistic Regression**,**Neural Networks**,**Support Vector Machines**and**Decision Trees, Random Forests**,**Bagging and Boosting**. You could for example explore all of the approaches from decision trees, via bagging and voting classifiers, to random forests, boosting and finally XGboost. If you wish to venture into**convolutional neural networks**or**recurrent neural networks**, or extensions of neural networkds, feel free to do so. - For project 3, you should feel free to use your own codes from projects 1 and 2, eventually write your own for SVMs and/or Decision trees/random forests/bagging/boostingâ€™ or use the available functionality of
**ScikitLearn**,**Tensorflow**, etc. - The estimates you used and tested in projects 1 and 2 should also be included, that is the
*R*2-score,**MSE**, confusion matrix, accuracy score, information gain, cross-validation and/or bootstrap if these are relevant.

*Â *c 1999-2019, “Data Analysis and Machine Learning

FYS-STK3155/FYS4155″:”http://www.uio.no/studier/emner/matnat/fys/FYS3155/index-

eng.html”. Released under CC Attribution-NonCommercial 4.0

license

- If possible, you should link the data sets with exisiting research and analyses thereof. Scientific articles which have used Machine Learning algorithms to analyze the data are highly welcome. Perhaps you can improve previous analyses and even publish a new article?
- A critical assessment of the methods with ditto perspectives and recommendations is also something you need to include.

All in all, the report should follow the same pattern as the two previous ones, with abstract, introduction, methods, code, results, conclusions etc..

We propose also an alternative to the above. This is a project on using machine learning methods (neural networks mainly) to the solution of ordinary differential equations and partial differential equations, with a final twist on how to diagonalize a symmetric matrix with neural networks..

This is a field with a large interest recently, spanning from studies of turbulence in fluid mechanics and meteorology to the solution of quantum mechanical systems.

## The basic structure of your project

Here follows a set up on how to structure your report and analyze the data you have opted for.

**Part a). **The first part deals with structuring and reading the data, much along the same lines as done in projects 1 and 2. Explain how the data are produced and place them in a proper context.

**Part b). **You need to include at least two central algorithms, or as an alternative explore methods from decisions tree to bagging, random forests and boosting. Explain the basics of the methods you have chosen to work with. This would be your theory part.

**Part c).Â Â Â **Then describe your algorithm and its implementation and tests you have performed.

**Part d). **Then presents your results and findings, link with existing literature and more.

**Part e).Â Â **Finally, here you should present a critical assessment of the methods you have studied and link your results with the existing literature.

## Solving partial differential equations with neural networks

For this variant of project 3, we will assume that you have some background in the solution of partial differential equations using finite difference schemes.

We will study the solution of the diffusion equation in one dimension using a standard explicit scheme and neural networks to solve the same equations.

For the explicit scheme, you can study for example chapter 10 of the lecture notes in Computational Physics or alternative sources. For the solution of ordinary and partial differential equations using neural networks, the lectures by Kristine Baluka Hein at this course are highly recommended.

For the machine learning part you can use your own code from project 2 or the functionality of for example **Tensorflow/Keras**.

**Part a), setting up the problem. **The physical problem can be that of the temperature gradient in a rod of length *L *= 1 at *x *= 0 and *x *= 1. We are looking at a one-dimensional problem

*,t > *0*,x âˆˆ *[0*,L*]

or

*u**xx *= *u**t,*

with initial conditions, i.e., the conditions at *t *= 0,

*u*(*x,*0) = sin(*Ï€x*)Â Â Â Â Â Â Â Â Â Â Â Â Â 0 *< x < L,*

with *L *= 1 the length of the *x*-region of interest. The boundary conditions are

*u*(0*,t*) = 0Â Â Â Â Â Â Â Â Â Â *t â‰¥ *0*,*

and

*u*(*L,t*) = 0Â Â Â Â Â Â Â Â Â Â *t â‰¥ *0*.*

The function *u*(*x,t*) can be the temperature gradient of a rod. As time increases, the velocity approaches a linear variation with *x*.

We will limit ourselves to the so-called explicit forward Euler algorithm with discretized versions of time given by a forward formula and a centered difference in space resulting in

_{ut }* _{â‰ˆ }u*(

*x,t*+ âˆ†

*t*)

*âˆ’ u*(

*x,t*)

_{= }

*u*(

*x*

*i,t*

*j*+ âˆ†

*t*)

*âˆ’ u*(

*x*

*i,t*

*j*)

âˆ†*tÂ Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â *âˆ†*t*

and

*u*(*x *+ âˆ†*x,t*) *âˆ’ *2*u*(*x,t*) + *u*(*x âˆ’ *âˆ†*x,t*) *u**xx**,*

or

*u*(*x _{i }*+ âˆ†

*x,t*)

_{j}*âˆ’*2

*u*(

*x*) +

_{i},t_{j}*u*(

*x*âˆ†

_{i }âˆ’*x,t*)

_{j}*u*

*xx*

*.*

Write down the algorithm and the equations you need to implement. Find also the analytical solution to the problem.

**Part b).Â Â **Implement the explicit scheme algorithm and perform tests of the solution for âˆ†*x *= 1*/*10, âˆ†*x *= 1*/*100 using âˆ†*t *as dictated by the stability limit of the explicit scheme. The stability criterion for the explicit scheme requires that âˆ†*t/*âˆ†*x*^{2 }*â‰¤ *1*/*2.

Study the solutions at two time points *t*_{1 }and *t*_{2 }where *u*(*x,t*_{1}) is smooth but still significantly curved and *u*(*x,t*_{2}) is almost linear, close to the stationary state.

**Part c) Neural networks. **Study now the lecture notes on solving ODEs and PDEs with neural network and use either your own code from project 2 or the functionality of tensorflow/keras to solve the same equation as in part

b). Discuss your results and compare them with the standard explicit scheme. Include also the analytical solution and compare with that.

**Part d) Solving eigenvalue problems. **Follow the discussion in the work of Yi *et al. *in the article from Computers and Mathematics with Applications 47, 1155 (2004), and use your differential equation solver with neural networks, set up a simple square, real and symmetric 6 *Ã— *6 matrix and find the eigenvalues. Compare with the solution from numerical diagonalization with standard eigenvalue solvers from linear algebra.

**Part e). **Finally, present a critical assessment of the methods you have studied and discuss the potential for the solving differential equations and eigenvalue problems with machine learning methods.

## Introduction to numerical projects

Here follows a brief recipe and recommendation on how to write a report for each project.

- Give a short description of the nature of the problem and the eventual numerical methods you have used.
- 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.
- Include the source code of your program. Comment your program properly.
- If possible, try to find analytic solutions, or known limits in order to test your program when developing the code.
- 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.
- 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.
- Try to give an interpretation of you results in your answers to the problems.
- 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.
- 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.

## Format for electronic delivery of report and programs

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:

- Use Devilry to hand in your projects, log in at http://devilry.ifi. no with your normal UiO username and password and choose either â€™fysstk3155â€™ or â€™fysstk4155â€™. There you can load up the files within the deadline.
- Upload
**only**the report file! For the source code file(s) you have developed please provide us with your link to your github domain. The report file should include all of your discussions and a list of the codes you have developed. Do not include library files which are available at the course homepage, unless you have made specific changes to them. - In your git 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.
- In this and all later projects, you should include tests (for example unit tests) of your code(s).
- Comments from us on your projects, approval or not, corrections to be made etc can be found under your Devilry domain and are only visible to you and the teachers of the course.

Finally, we encourage you to collaborate. Optimal working groups consist of 2-3 students. You can then hand in a common report.

## Software and needed installations

If you have Python installed (we recommend Python3) and you feel pretty familiar with installing different packages, we recommend that you install the following Python packages via **pip **as

- pip install numpy scipy matplotlib ipython scikit-learn tensorflow sympy pandas pillow

For Python3, replace **pip **with **pip3**.

See below for a discussion of **tensorflow **and **scikit-learn**.

For OSX users we recommend also, after having installed Xcode, to install **brew**. Brew allows for a seamless installation of additional software via for example

- brew install python3

For Linux users, with its variety of distributions like for example the widely popular Ubuntu distribution you can use **pip **as well and simply install Python as

- sudo apt-get install python3 (or python for python2.7)

etc etc.

If you donâ€™t want to install various Python packages with their dependencies separately, we recommend two widely used distrubutions which set up all relevant dependencies for Python, namely

- Anaconda Anaconda is an open source distribution of the Python and R programming languages for large-scale data processing, predictive analytics, and scientific computing, that aims to simplify package management and deployment. Package versions are managed by the package management system
**conda** - Enthought canopy is a Python distribution for scientific and analytic computing distribution and analysis environment, available for free and under a commercial license.

Popular software packages written in Python for ML are

These are all freely available at their respective GitHub sites. They encompass communities of developers in the thousands or more. And the number of code developers and contributors keeps increasing.