A general description of the goal(s) of the school can be found on the [https://www.yambo-code.eu/2023/02/18/yambo-school-2023/ Yambo main website]

== Use CINECA computational resources ==
Yambo tutorials will be run on the MARCONI100 (M100) accelerated cluster. You can find info about M100 [https://wiki.u-gov.it/confluence/display/SCAIUS/UG3.2%3A+MARCONI100+UserGuide#UG3.2:MARCONI100UserGuide here].
In order to access computational resources provided by CINECA you need your personal username and password that were sent you by the organizers.

=== Connect to the cluster using ssh ===

You can access M100 via <code>ssh</code> protocol in different ways.

''' - Connect using username and password '''

Use the following command replacing your username:
$ ssh username@login.m100.cineca.it

However, in this way you have to type your password each time you want to connect.

''' - Connect using ssh key '''

You can setup a ssh key pair to avoid typing the password each time you want to connect to M100. To do so, go to your <code>.ssh</code> directory (usually located in the <code>home</code> directory):
$ cd $HOME/.ssh

If you don't have this directory, you can create it with <code>mkdir $HOME/.ssh</code>.

Once you are in the <code>.ssh</code> directory, run the <code>ssh-keygen</code> command to generate a private/public key pair:
$ ssh-keygen
Generating public/private rsa key pair.
Enter file in which to save the key: m100_id_rsa
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in <your_.ssh_dir>/m100_id_rsa
Your public key has been saved in <your_.ssh_dir>/m100_id_rsa.pub
The key fingerprint is:
<...>
The key's randomart image is:
<...>

Now you need to copy the '''public''' key to M100. You can do that with the following command (for this step you need to type your password):
$ ssh-copy-id -i <your_.ssh_dir>/m100_id_rsa.pub <username>@login.m100.cineca.it

Once the public key has been copied, you can connect to M100 without having to type the password using the <code>-i</code> option:
$ ssh -i <your_.ssh_dir>/m100_id_rsa username@login.m100.cineca.it

To simplify even more, you can paste the following lines in a file named <code>config</code> located inside the <code>.ssh</code> directory adjusting username and path:
Host m100
HostName login.m100.cineca.it
User username
IdentityFile <your_.ssh_dir>/m100_id_rsa

With the <code>config</code> file setup you can connect simply with
$ ssh m100

=== General instructions to run tutorials ===

Before proceeding, it is useful to know the different workspaces you have available on M100, which can be accessed using environment variables. The main ones are:
* <code>$HOME</code>: it's the <code>home</code> directory associated to your username;
* <code>$WORK</code>: it's the <code>work</code> directory associated to the account where the computational resources dedicated to this school are allocated;
* <code>$CINECA_SCRATCH</code>: it's the <code>scratch</code> directory associated to your username.
You can find more details about storage and FileSystems [https://wiki.u-gov.it/confluence/display/SCAIUS/UG2.5%3A+Data+storage+and+FileSystems here].

Please don't forget to '''run all tutorials in your scratch directory''':
$ echo $CINECA_SCRATCH
/m100_scratch/userexternal/username
$ cd $CINECA_SCRATCH

Computational resources on M100 are managed by the job scheduling system [https://slurm.schedmd.com/overview.html Slurm]. Most part of Yambo tutorials during this school can be run in serial, except some that need to be executed on multiple processors. Generally, Slurm batch jobs are submitted using a script, but the tutorials here are better understood if run interactively. The two procedures that we will use to submit interactive and non interactive jobs are explained below.

''' - Run a job using a batch script '''

This procedure is suggested for the tutorials and examples that need to be run in parallel. In these cases you need to submit the job using a batch script <code>job.sh</code>, whose generic structure is the following:
$ more job.sh
#!/bin/bash
#SBATCH --account=tra23_Yambo # Charge resources used by this job to specified account
#SBATCH --time=00:10:00 # Set a limit on the total run time of the job allocation in hh:mm:ss
#SBATCH --job-name=JOB # Specify a name for the job allocation
#SBATCH --partition=m100_usr_prod # Request a specific partition for the resource allocation
#
#SBATCH --nodes=<N> # Number of nodes to be allocated for the job
#SBATCH --ntasks-per-node=<nt> # Number of MPI tasks invoked per node
#SBATCH --ntasks-per-socket=<nt/2> # Tasks invoked on each socket
#SBATCH --cpus-per-task=<nc> # Number of OMP threads per task

module purge
module load hpc-sdk/2022--binary
module load spectrum_mpi/10.4.0--binary
export PATH=/m100_work/tra23_Yambo/softwares/YAMBO/5.2-mpi/bin:$PATH

export OMP_NUM_THREADS=<nc>

mpirun --rank-by core -np ${SLURM_NTASKS} \
yambo -F <input> -J <output>

Please note that these instructions must be compatible with the specific M100 [https://wiki.u-gov.it/confluence/display/SCAIUS/UG3.2%3A+MARCONI100+UserGuide#UG3.2:MARCONI100UserGuide-SystemArchitecture architecture] and [https://wiki.u-gov.it/confluence/display/SCAIUS/UG3.2%3A+MARCONI100+UserGuide#UG3.2:MARCONI100UserGuide-Accounting accounting] systems. The complete list of Slurm options can be found [https://slurm.schedmd.com/sbatch.html here]. However, you will find ready-to-use batch scripts in locations specified during the tutorials.

To submit the job, use the <code>sbatch</code> command:
$ sbatch job.sh
Submitted batch job <JOBID>

To check the job status, use the <code>squeue</code> command:
$ squeue -u <username>
JOBID PARTITION NAME USER ST TIME NODES NODELIST(REASON)
<...> m100_usr_ JOB username R 0:01 <N> <...>

''' - Open an interactive session '''

This procedure is suggested for most of the tutorials, since the majority of these is meant to be run in serial from the command line. With the command below, you can open an interactive session of 1 hour to execute commands in serial (complete documentation [https://slurm.schedmd.com/salloc.html here]):
$ salloc --account=tra23_Yambo --nodes=1 --ntasks-per-node=1 --cpus-per-task=1 --partition=m100_usr_prod --qos=m100_qos_dbg --time=01:00:00
salloc: Granted job allocation 10164647
salloc: Waiting for resource configuration
salloc: Nodes r256n01 are ready for job

With <code>squeue</code> you can see that there is now a job running:
$ squeue -u username
JOBID PARTITION NAME USER ST TIME NODES NODELIST(REASON)
10164647 m100_usr_ interact username R 0:02 1 r256n01

To run the tutorial, <code>ssh</code> into the node specified by the job allocation and <code>cd</code> to your scratch directory:
$ ssh r256n01
$ cd $CINECA_SCRATCH

Then, you need to load <code>yambo</code> as in the batch script above. Please note that the serial version of the code is in a different directory:
$ module purge
$ module load hpc-sdk/2022--binary
$ module load spectrum_mpi/10.4.0--binary
$ export PATH=/m100_work/tra23_Yambo/softwares/YAMBO/5.2-ser/bin:$PATH

== Tutorials ==

=== DAY 1 - Monday, 22 May ===

'''16:15 - 18:30 From the DFT ground state to the complete setup of a Many Body calculation using Yambo'''

* [[First steps: walk through from DFT(standalone)|First steps: Initialization and more ]]
* [[Next steps: RPA calculations (standalone)|Next steps: RPA calculations ]]
* [[Yambopy tutorial: band structures|Band structures with yambopy: Tutorial 1 (BN)]]
* [[Yambopy tutorial: band structures|Band structures with yambopy: Tutorial 2 (Iron)]]

=== DAY 2 - Tuesday, 23 May ===

'''14:00 - 16:30 A tour through GW simulation in a complex material (from the blackboard to numerical computation: convergence, algorithms, parallel usage)'''

* [[GW tutorial Rome 2023 | GW computations on practice: how to obtain the quasi-particle band structure of a bulk material ]]

=== DAY 3 - Wednesday, 24 May ===

'''17:00 - 18:30 Real-time Bethe-Salpeter equation''' Fulvio Paleari (), Davide Sangalli (CNR-ISM, Italy)

* [[Linear response from real time simulations]] (extract from this the part with yambo_rt)

=== DAY 4 - Thursday, May 25 ===

'''14:00 - 16:30 Real-time approach with the time dependent berry phase''' Myrta Gruning (), Davide Sangalli (CNR-ISM, Italy)

* [[Linear response from real time simulations]] (extract from this the part with yambo_nl)
* [[Non-linear response TD-HSEX: hBN]] (to be created, inputs from Ignacio)

* [[Real time approach to non-linear response]] (to decide if we do also AlAS part 1)
* [[Correlation effects in the non-linear response]] (to decide if we do also AlAS part 2)

=== DAY 5 - Friday, 26 May ===

== Lectures ==

=== DAY 1 - Monday, 22 May ===

Rome 2023

2023-05-17T15:48:11Z

Matteo.dalessio: /* Connect to the cluster using ssh */

A general description of the goal(s) of the school can be found on the [https://www.yambo-code.eu/2023/02/18/yambo-school-2023/ Yambo main website]

== Use CINECA computational resources ==
Yambo tutorials will be run on the MARCONI100 (M100) accelerated cluster. You can find info about M100 [https://wiki.u-gov.it/confluence/display/SCAIUS/UG3.2%3A+MARCONI100+UserGuide#UG3.2:MARCONI100UserGuide here].
In order to access computational resources provided by CINECA you need your personal username and password that were sent you by the organizers.

=== Connect to the cluster using ssh ===

You can access M100 via <code>ssh</code> protocol in different ways.

''' - Connect using username and password '''

Use the following command replacing your username:
$ ssh username@login.m100.cineca.it

However, in this way you have to type your password each time you want to connect.

''' - Connect using ssh key '''

You can setup a ssh key pair to avoid typing the password each time you want to connect to M100. To do so, go to your <code>.ssh</code> directory (usually located in the <code>home</code> directory):
$ cd $HOME/.ssh

If you don't have this directory, you can create it with <code>mkdir $HOME/.ssh</code>.

Once you are in the <code>.ssh</code> directory, run the <code>ssh-keygen</code> command to generate a private/public key pair:
$ ssh-keygen
Generating public/private rsa key pair.
Enter file in which to save the key: m100_id_rsa
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in <your_.ssh_dir>/m100_id_rsa
Your public key has been saved in <your_.ssh_dir>/m100_id_rsa.pub
The key fingerprint is:
<...>
The key's randomart image is:
<...>

Now you need to copy the '''public''' key to M100. You can do that with the following command (for this step you need to type your password):
$ ssh-copy-id -i <your_.ssh_dir>/m100_id_rsa.pub <username>@login.m100.cineca.it

Once the public key has been copied, you can connect to M100 without having to type the password using the <code>-i</code> option:
$ ssh -i <your_.ssh_dir>/m100_id_rsa username@login.m100.cineca.it

To simplify even more, you can paste the following lines in a file named <code>config</code> located inside the <code>.ssh</code> directory adjusting username and path:
Host m100
HostName login.m100.cineca.it
User username
IdentityFile <your_.ssh_dir>/m100_id_rsa

With the <code>config</code> file setup you can connect simply with
$ ssh m100

=== General instructions to run tutorials ===

Before proceeding, it is useful to know the different workspaces you have available on M100, which can be accessed using environment variables. The main ones are:
* <code>$HOME</code>: it's the <code>home</code> directory associated to your username;
* <code>$WORK</code>: it's the <code>work</code> directory associated to the account where the computational resources dedicated to this school are allocated;
* <code>$CINECA_SCRATCH</code>: it's the <code>scratch</code> directory associated to your username.
You can find more details about storage and FileSystems [https://wiki.u-gov.it/confluence/display/SCAIUS/UG2.5%3A+Data+storage+and+FileSystems here].

Please don't forget to '''run all tutorials in your scratch directory''':
$ echo $CINECA_SCRATCH
/m100_scratch/userexternal/username
$ cd $CINECA_SCRATCH

Computational resources on M100 are managed by the job scheduling system [https://slurm.schedmd.com/overview.html Slurm]. Most part of Yambo tutorials during this school can be run in serial, except some that need to be executed on multiple processors. Generally, Slurm batch jobs are submitted using a script, but the tutorials here are better understood if run interactively. The two procedures that we will use to submit interactive and non interactive jobs are explained below.

''' - Run a job using a batch script '''

This procedure is suggested for the tutorials and examples that need to be run in parallel. In these cases you need to submit the job using a batch script <code>job.sh</code>, whose generic structure is the following:
$ more job.sh
#!/bin/bash
#SBATCH --account=tra23_Yambo # Charge resources used by this job to specified account
#SBATCH --time=00:10:00 # Set a limit on the total run time of the job allocation in hh:mm:ss
#SBATCH --job-name=JOB # Specify a name for the job allocation
#SBATCH --partition=m100_usr_prod # Request a specific partition for the resource allocation
#
#SBATCH --nodes=<N> # Number of nodes to be allocated for the job
#SBATCH --ntasks-per-node=<nt> # Number of MPI tasks invoked per node
#SBATCH --ntasks-per-socket=<nt/2> # Tasks invoked on each socket
#SBATCH --cpus-per-task=<nc> # Number of OMP threads per task

module purge
module load hpc-sdk/2022--binary
module load spectrum_mpi/10.4.0--binary
export PATH=/m100_work/tra23_Yambo/softwares/YAMBO/5.2-mpi/bin:$PATH

export OMP_NUM_THREADS=<nc>

mpirun --rank-by core -np ${SLURM_NTASKS} \
yambo -F <input> -J <output>

Please note that these instructions must be compatible with the specific M100 [https://wiki.u-gov.it/confluence/display/SCAIUS/UG3.2%3A+MARCONI100+UserGuide#UG3.2:MARCONI100UserGuide-SystemArchitecture architecture] and [https://wiki.u-gov.it/confluence/display/SCAIUS/UG3.2%3A+MARCONI100+UserGuide#UG3.2:MARCONI100UserGuide-Accounting accounting] systems. The complete list of Slurm options can be found [https://slurm.schedmd.com/sbatch.html here]. However, you will find ready-to-use batch scripts in locations specified during the tutorials.

To submit the job, use the <code>sbatch</code> command:
$ sbatch job.sh
Submitted batch job <JOBID>

To check the job status, use the <code>squeue</code> command:
$ squeue -u <username>
JOBID PARTITION NAME USER ST TIME NODES NODELIST(REASON)
<...> m100_usr_ JOB username R 0:01 <N> <...>

''' - Open an interactive session '''

This procedure is suggested for most of the tutorials, since the majority of these is meant to be run in serial from the command line. With the command below, you can open an interactive session of 1 hour to execute commands in serial (complete documentation [https://slurm.schedmd.com/salloc.html here]):
$ salloc --account=tra23_Yambo --nodes=1 --ntasks-per-node=1 --cpus-per-task=1 --partition=m100_usr_prod --qos=m100_qos_dbg --time=01:00:00
salloc: Granted job allocation 10164647
salloc: Waiting for resource configuration
salloc: Nodes r256n01 are ready for job

With <code>squeue</code> you can see that there is now a job running:
$ squeue -u username
JOBID PARTITION NAME USER ST TIME NODES NODELIST(REASON)
10164647 m100_usr_ interact username R 0:02 1 r256n01

To run the tutorial, <code>ssh</code> into the node specified by the job allocation and <code>cd</code> to your scratch directory:
$ ssh r256n01
$ cd $CINECA_SCRATCH

Then, you need to load <code>yambo</code> as in the batch script above. Please note that the serial version of the code is in a different directory:
$ module purge
$ module load hpc-sdk/2022--binary
$ module load spectrum_mpi/10.4.0--binary
$ export PATH=/m100_work/tra23_Yambo/softwares/YAMBO/5.2-ser/bin:$PATH

== Tutorials ==

=== DAY 1 - Monday, 22 May ===

'''16:15 - 18:30 From the DFT ground state to the complete setup of a Many Body calculation using Yambo'''

* [[First steps: walk through from DFT(standalone)|First steps: Initialization and more ]]
* [[Next steps: RPA calculations (standalone)|Next steps: RPA calculations ]]
* [[Yambopy tutorial: band structures|Band structures with yambopy: Tutorial 1 (BN)]]
* [[Yambopy tutorial: band structures|Band structures with yambopy: Tutorial 2 (Iron)]]

=== DAY 2 - Tuesday, 23 May ===

'''14:00 - 16:30 A tour through GW simulation in a complex material (from the blackboard to numerical computation: convergence, algorithms, parallel usage)'''

* [[GW tutorial Rome 2023 | GW computations on practice: how to obtain the quasi-particle band structure of a bulk material ]]

=== DAY 3 - Wednesday, 24 May ===

'''17:00 - 18:30 Real-time Bethe-Salpeter equation''' Fulvio Paleari (), Davide Sangalli (CNR-ISM, Italy)

* [[Linear response from real time simulations]] (extract from this the part with yambo_rt)

=== DAY 4 - Thursday, May 25 ===

'''14:00 - 16:30 Real-time approach with the time dependent berry phase''' Myrta Gruning (), Davide Sangalli (CNR-ISM, Italy)

* [[Linear response from real time simulations]] (extract from this the part with yambo_nl)
* [[Non-linear response TD-HSEX: hBN]] (to be created, inputs from Ignacio)

* [[Real time approach to non-linear response]] (to decide if we do also AlAS part 1)
* [[Correlation effects in the non-linear response]] (to decide if we do also AlAS part 2)

=== DAY 5 - Friday, 26 May ===

== Lectures ==

=== DAY 1 - Monday, 22 May ===

Rome 2023

2023-05-17T15:48:01Z

Matteo.dalessio: /* Connect to the cluster using ssh */

A general description of the goal(s) of the school can be found on the [https://www.yambo-code.eu/2023/02/18/yambo-school-2023/ Yambo main website]

== Use CINECA computational resources ==
Yambo tutorials will be run on the MARCONI100 (M100) accelerated cluster. You can find info about M100 [https://wiki.u-gov.it/confluence/display/SCAIUS/UG3.2%3A+MARCONI100+UserGuide#UG3.2:MARCONI100UserGuide here].
In order to access computational resources provided by CINECA you need your personal username and password that were sent you by the organizers.

=== Connect to the cluster using ssh ===

You can access M100 via <code>ssh</code> protocol in different ways.

''' - Connect using username and password '''

Use the following command replacing your username:
$ ssh username@login.m100.cineca.it

However, in this way you have to type your password each time you want to connect.

''' - Connect using ssh key '''

You can setup a ssh key pair to avoid typing the password each time you want to connect to M100. To do so, go to your <code>.ssh</code> directory (usually located in the <code>home</code> directory):
$ cd $HOME/.ssh

If you don't have this directory, you can create it with <code>mkdir $HOME/.ssh</code>.

Once you are in the <code>.ssh</code> directory, run the <code>ssh-keygen</code> command to generate a private/public key pair:
$ ssh-keygen
Generating public/private rsa key pair.
Enter file in which to save the key: m100_id_rsa
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in <your_.ssh_dir>/m100_id_rsa
Your public key has been saved in <your_.ssh_dir>/m100_id_rsa.pub
The key fingerprint is:
<...>
The key's randomart image is:
<...>

Now you need to copy the '''public''' key to M100. You can do that with the following command (for this step you need to type your password):
$ ssh-copy-id -i <your_.ssh_dir>/m100_id_rsa.pub <username>@login.m100.cineca.it

Once the public key has been copied, you can connect to M100 without having to type the password using the <code>-i</code> option:
$ ssh -i <your_.ssh_dir>/m100_id_rsa username@login.m100.cineca.it

To simplify even more, you can paste the following lines in a file named <code>config</code> located inside the <code>.ssh</code> directory adjusting username and path:
Host m100
HostName login.m100.cineca.it
User username
IdentityFile <your_.ssh_dir>/m100_id_rsa

With the <code>config</code> file setup you can connect simply with
$ ssh m100

=== General instructions to run tutorials ===

Before proceeding, it is useful to know the different workspaces you have available on M100, which can be accessed using environment variables. The main ones are:
* <code>$HOME</code>: it's the <code>home</code> directory associated to your username;
* <code>$WORK</code>: it's the <code>work</code> directory associated to the account where the computational resources dedicated to this school are allocated;
* <code>$CINECA_SCRATCH</code>: it's the <code>scratch</code> directory associated to your username.
You can find more details about storage and FileSystems [https://wiki.u-gov.it/confluence/display/SCAIUS/UG2.5%3A+Data+storage+and+FileSystems here].

Please don't forget to '''run all tutorials in your scratch directory''':
$ echo $CINECA_SCRATCH
/m100_scratch/userexternal/username
$ cd $CINECA_SCRATCH

Computational resources on M100 are managed by the job scheduling system [https://slurm.schedmd.com/overview.html Slurm]. Most part of Yambo tutorials during this school can be run in serial, except some that need to be executed on multiple processors. Generally, Slurm batch jobs are submitted using a script, but the tutorials here are better understood if run interactively. The two procedures that we will use to submit interactive and non interactive jobs are explained below.

''' - Run a job using a batch script '''

This procedure is suggested for the tutorials and examples that need to be run in parallel. In these cases you need to submit the job using a batch script <code>job.sh</code>, whose generic structure is the following:
$ more job.sh
#!/bin/bash
#SBATCH --account=tra23_Yambo # Charge resources used by this job to specified account
#SBATCH --time=00:10:00 # Set a limit on the total run time of the job allocation in hh:mm:ss
#SBATCH --job-name=JOB # Specify a name for the job allocation
#SBATCH --partition=m100_usr_prod # Request a specific partition for the resource allocation
#
#SBATCH --nodes=<N> # Number of nodes to be allocated for the job
#SBATCH --ntasks-per-node=<nt> # Number of MPI tasks invoked per node
#SBATCH --ntasks-per-socket=<nt/2> # Tasks invoked on each socket
#SBATCH --cpus-per-task=<nc> # Number of OMP threads per task

module purge
module load hpc-sdk/2022--binary
module load spectrum_mpi/10.4.0--binary
export PATH=/m100_work/tra23_Yambo/softwares/YAMBO/5.2-mpi/bin:$PATH

export OMP_NUM_THREADS=<nc>

mpirun --rank-by core -np ${SLURM_NTASKS} \
yambo -F <input> -J <output>

Please note that these instructions must be compatible with the specific M100 [https://wiki.u-gov.it/confluence/display/SCAIUS/UG3.2%3A+MARCONI100+UserGuide#UG3.2:MARCONI100UserGuide-SystemArchitecture architecture] and [https://wiki.u-gov.it/confluence/display/SCAIUS/UG3.2%3A+MARCONI100+UserGuide#UG3.2:MARCONI100UserGuide-Accounting accounting] systems. The complete list of Slurm options can be found [https://slurm.schedmd.com/sbatch.html here]. However, you will find ready-to-use batch scripts in locations specified during the tutorials.

To submit the job, use the <code>sbatch</code> command:
$ sbatch job.sh
Submitted batch job <JOBID>

To check the job status, use the <code>squeue</code> command:
$ squeue -u <username>
JOBID PARTITION NAME USER ST TIME NODES NODELIST(REASON)
<...> m100_usr_ JOB username R 0:01 <N> <...>

''' - Open an interactive session '''

This procedure is suggested for most of the tutorials, since the majority of these is meant to be run in serial from the command line. With the command below, you can open an interactive session of 1 hour to execute commands in serial (complete documentation [https://slurm.schedmd.com/salloc.html here]):
$ salloc --account=tra23_Yambo --nodes=1 --ntasks-per-node=1 --cpus-per-task=1 --partition=m100_usr_prod --qos=m100_qos_dbg --time=01:00:00
salloc: Granted job allocation 10164647
salloc: Waiting for resource configuration
salloc: Nodes r256n01 are ready for job

With <code>squeue</code> you can see that there is now a job running:
$ squeue -u username
JOBID PARTITION NAME USER ST TIME NODES NODELIST(REASON)
10164647 m100_usr_ interact username R 0:02 1 r256n01

To run the tutorial, <code>ssh</code> into the node specified by the job allocation and <code>cd</code> to your scratch directory:
$ ssh r256n01
$ cd $CINECA_SCRATCH

Then, you need to load <code>yambo</code> as in the batch script above. Please note that the serial version of the code is in a different directory:
$ module purge
$ module load hpc-sdk/2022--binary
$ module load spectrum_mpi/10.4.0--binary
$ export PATH=/m100_work/tra23_Yambo/softwares/YAMBO/5.2-ser/bin:$PATH

== Tutorials ==

=== DAY 1 - Monday, 22 May ===

'''16:15 - 18:30 From the DFT ground state to the complete setup of a Many Body calculation using Yambo'''

* [[First steps: walk through from DFT(standalone)|First steps: Initialization and more ]]
* [[Next steps: RPA calculations (standalone)|Next steps: RPA calculations ]]
* [[Yambopy tutorial: band structures|Band structures with yambopy: Tutorial 1 (BN)]]
* [[Yambopy tutorial: band structures|Band structures with yambopy: Tutorial 2 (Iron)]]

=== DAY 2 - Tuesday, 23 May ===

'''14:00 - 16:30 A tour through GW simulation in a complex material (from the blackboard to numerical computation: convergence, algorithms, parallel usage)'''

* [[GW tutorial Rome 2023 | GW computations on practice: how to obtain the quasi-particle band structure of a bulk material ]]

=== DAY 3 - Wednesday, 24 May ===

'''17:00 - 18:30 Real-time Bethe-Salpeter equation''' Fulvio Paleari (), Davide Sangalli (CNR-ISM, Italy)

* [[Linear response from real time simulations]] (extract from this the part with yambo_rt)

=== DAY 4 - Thursday, May 25 ===

'''14:00 - 16:30 Real-time approach with the time dependent berry phase''' Myrta Gruning (), Davide Sangalli (CNR-ISM, Italy)

* [[Linear response from real time simulations]] (extract from this the part with yambo_nl)
* [[Non-linear response TD-HSEX: hBN]] (to be created, inputs from Ignacio)

* [[Real time approach to non-linear response]] (to decide if we do also AlAS part 1)
* [[Correlation effects in the non-linear response]] (to decide if we do also AlAS part 2)

=== DAY 5 - Friday, 26 May ===

== Lectures ==

=== DAY 1 - Monday, 22 May ===