https://gitlab.com/januseriksen/pymbe
- HEAD
- refs/heads/bg_mrcc
- refs/heads/bg_pyscf
- refs/heads/bookkeeping
- refs/heads/cfour_casci
- refs/heads/change_phases
- refs/heads/dev
- refs/heads/dual_exp
- refs/heads/dynamic_orbs
- refs/heads/e_contrib_plot
- refs/heads/ecc_cfour
- refs/heads/energy_corr
- refs/heads/energy_est
- refs/heads/impr_get_dim
- refs/heads/impr_mpi_scheme
- refs/heads/impr_mpi_timings
- refs/heads/master
- refs/heads/miscellaneous
- refs/heads/mo_ints
- refs/heads/mp2
- refs/heads/mpi_energy
- refs/heads/mpi_improvements
- refs/heads/mpi_plot
- refs/heads/mpi_time
- refs/heads/natural_orbs
- refs/heads/new_bg_order
- refs/heads/new_data_struct
- refs/heads/new_orb_generator
- refs/heads/new_screen
- refs/heads/norm_dist_screen
- refs/heads/open_source
- refs/heads/orbital_screening
- refs/heads/qcscf
- refs/heads/remove_energy_corr
- refs/heads/restart_utils
- refs/heads/rm_orb_ent
- refs/heads/rm_timings
- refs/heads/screen_tuple
- refs/heads/shared_mem
- refs/heads/sparsity
- refs/heads/style_impro
- refs/merge-requests/1/head
- refs/merge-requests/10/head
- refs/merge-requests/11/head
- refs/merge-requests/12/head
- refs/merge-requests/13/head
- refs/merge-requests/13/merge
- refs/merge-requests/14/head
- refs/merge-requests/14/merge
- refs/merge-requests/15/head
- refs/merge-requests/15/merge
- refs/merge-requests/16/head
- refs/merge-requests/16/merge
- refs/merge-requests/17/head
- refs/merge-requests/17/merge
- refs/merge-requests/18/head
- refs/merge-requests/18/merge
- refs/merge-requests/19/head
- refs/merge-requests/19/merge
- refs/merge-requests/2/head
- refs/merge-requests/20/head
- refs/merge-requests/21/head
- refs/merge-requests/21/merge
- refs/merge-requests/22/head
- refs/merge-requests/22/merge
- refs/merge-requests/23/head
- refs/merge-requests/23/merge
- refs/merge-requests/24/head
- refs/merge-requests/24/merge
- refs/merge-requests/25/head
- refs/merge-requests/25/merge
- refs/merge-requests/26/head
- refs/merge-requests/26/merge
- refs/merge-requests/27/head
- refs/merge-requests/27/merge
- refs/merge-requests/28/head
- refs/merge-requests/28/merge
- refs/merge-requests/3/head
- refs/merge-requests/4/head
- refs/merge-requests/5/head
- refs/merge-requests/6/head
- refs/merge-requests/7/head
- refs/merge-requests/8/head
- refs/merge-requests/9/head
Cook and download a directory from the Software Heritage Vault
You have requested the cooking of the directory with identifier swh:1:dir:0f8f895df6eff700132f93d4bcda0a88e7139659 into a standard tar.gz archive.
Are you sure you want to continue ?
Download a directory from the Software Heritage Vault
You have requested the download of the directory with identifier swh:1:dir:0f8f895df6eff700132f93d4bcda0a88e7139659 as a standard tar.gz archive.
Are you sure you want to continue ?
Cook and download a revision from the Software Heritage Vault
You have requested the cooking of the history heading to revision with identifier swh:1:rev:a666b2a064d3c85b7ce7ae2b47b1144733e06ac8 into a bare git archive.
Are you sure you want to continue ?
Download a revision from the Software Heritage Vault
You have requested the download of the history heading to revision with identifier swh:1:rev:a666b2a064d3c85b7ce7ae2b47b1144733e06ac8 as a bare git archive.
Are you sure you want to continue ?
Invalid Email !
The provided email is not well-formed.
Download link has expired
The requested archive is no longer available for download from the Software Heritage Vault.
Do you want to cook it again ?
Take a new snapshot of a software origin
If the archived software origin currently browsed is not synchronized with its upstream version (for instance when new commits have been issued), you can explicitly request Software Heritage to take a new snapshot of it.
Use the form below to proceed. Once a request has been submitted and accepted, it will be processed as soon as possible. You can then check its processing state by visiting this dedicated page.
Processing "take a new snapshot" request ...
To reference or cite the objects present in the Software Heritage archive, permalinks based on SoftWare Hash IDentifiers (SWHIDs) must be used.
Select below a type of object currently browsed in order to display its associated SWHID and permalink.
further polish to bg_summary
| File | Mode | Size |
|---|---|---|
| input-mol.inp | -rw-r--r-- | 109 bytes |
| input-param.inp | -rw-r--r-- | 219 bytes |
| molecules.txt | -rw-r--r-- | 1.8 KB |
