https://github.com/aamaricci/driver-database

A database of programs to solve specific problems using one or more QcmPlab libraries
https://github.com/aamaricci/driver-database

Last synced: 4 days ago
JSON representation

A database of programs to solve specific problems using one or more QcmPlab libraries

• Host: GitHub
• URL: https://github.com/aamaricci/driver-database
• Owner: aamaricci
• Created: 2020-12-01T11:06:29.000Z (almost 4 years ago)
• Default Branch: master
• Last Pushed: 2024-10-15T16:20:27.000Z (about 1 month ago)
• Last Synced: 2024-10-16T21:57:46.937Z (about 1 month ago)
• Language: Fortran
• Homepage:
• Size: 3.15 MB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
This is a sparse collection of programs that implement a case-by-case solution to vary of different problems, using libraries available in the QcmPlab Organization. 

The programs are divided in different directories, named after the method used: **Dmft_ED** for Exact Diagonalization based DMFT method, **SlaveSpins** for the Slave Spins method, **Lattice_ED** for programs implementing lattice Exact Diagonalization, etc. 

 

### Build instructions

- Install in your system the required the QcmPlab libraries that you need (`SciFor`,`DMFT-tools`, etc.)

- Edit to your needs the upper part of the `makefile` in the suitable working directory where your code reside.  

This amounts to set variables for:

    - The driver name _without_ `.f90` extension, e.g. `EXE=ed_bhz_2d`    

    - The fortran compiler [`FC`] of choice: `ifort`, `gnu` or `mpif90` alias are supported.   

    - The platform of choice; either `gnu` or `intel`, to define compilation options.   

    - The target directory for the compiled executable [`DIREXE`]; remember to add it to the `PATH`[^*]  

- Open a terminal therein and run `$ make`: the executable will be built and placed in `DIREXE`

- Open in your working directory a terminal and run ``. 

    - A default input file will be dumped therein as `used.input.`

- Edit to your needs the input file with your text editor of choice and save it as `input.`

- Then you can run again the executable and start crunching numbers!

[^*]: Append ```export PATH=:$PATH``` to your ```$HOME/.bashrc``` file