Skip to content

Commit 4ed332f

Browse files
committed
Release magsil-1-1
0 parents  commit 4ed332f

File tree

12 files changed

+4246
-0
lines changed

12 files changed

+4246
-0
lines changed

.github/workflows/release.yml

Lines changed: 55 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,55 @@
1+
name: release
2+
3+
on:
4+
push:
5+
tags:
6+
- v[0-9]*.[0-9]*.[0-9]*
7+
8+
env:
9+
SKF_NAME: "${{ github.event.repository.name }}"
10+
11+
jobs:
12+
13+
skf-archive:
14+
15+
runs-on: ubuntu-latest
16+
17+
steps:
18+
19+
- name: Checkout sk set
20+
uses: actions/checkout@v4
21+
22+
- name: Get version number
23+
run: |
24+
GIT_TAG=$(git describe --tags --match 'v[0-9]*.[0-9]*.[0-9]*')
25+
SKF_VERSION=$(echo $GIT_TAG | sed -E 's/^v([0-9]+)\.([0-9])+\.([0-9]+)$/\1-\2/')
26+
SKF_PATCH=$(echo $GIT_TAG | sed -E 's/^v([0-9]+)\.([0-9])+\.([0-9]+)$/\3/')
27+
echo "SKF_VERSION=${SKF_VERSION}" >> ${GITHUB_ENV}
28+
echo "SKF_PATCH=${SKF_PATCH}" >> ${GITHUB_ENV}
29+
ARCHIVE_NAME="${SKF_NAME}-${SKF_VERSION}"
30+
echo "ARCHIVE_NAME=${ARCHIVE_NAME}" >> ${GITHUB_ENV}
31+
if [[ ${SKF_PATCH} -eq 0 ]]; then
32+
echo "RELEASE_NAME=${ARCHIVE_NAME}" >> ${GITHUB_ENV}
33+
else
34+
echo "RELEASE_NAME=${ARCHIVE_NAME} (p${SKF_PATCH})" >> ${GITHUB_ENV}
35+
fi
36+
37+
- name: Create archive
38+
run: |
39+
mkdir -p _build/${ARCHIVE_NAME}
40+
cp $(find . -maxdepth 1 -not -type 'd') _build/${ARCHIVE_NAME}
41+
cp -a skfiles/* _build/${ARCHIVE_NAME}
42+
tar -C _build -c -v -J -f ${ARCHIVE_NAME}.tar.xz ${ARCHIVE_NAME}
43+
# mkdir -p _build/${ARCHIVE_NAME}-extras
44+
# cp -r extras/* _build/${ARCHIVE_NAME}-extras
45+
# tar -C _build -c -v -J -f ${ARCHIVE_NAME}-extras.tar.xz ${ARCHIVE_NAME}-extras
46+
47+
- name: Create release
48+
uses: softprops/action-gh-release@v2
49+
with:
50+
name: ${{ env.RELEASE_NAME }}
51+
preserve_order: True
52+
files: |
53+
${{ env.ARCHIVE_NAME }}.tar.xz
54+
# ${{ env.ARCHIVE_NAME }}-extras.tar.xz
55+
body_path: RELEASE.md

CHANGELOG.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
# Changelog
2+
3+
## magsil-1-1
4+
5+
First public release under CC-BY-SA license

LICENSE

Lines changed: 428 additions & 0 deletions
Large diffs are not rendered by default.

README

Lines changed: 62 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,62 @@
1+
(c) 2017, Helio A Duarte, Universidade Federal de Minas Gerais
2+
All rights reserved
3+
4+
This work is licensed under the Creative Commons Attribution-ShareAlike 4.0
5+
International License. To view a copy of this license, consult the LICENSE file
6+
or visit http://creativecommons.org/licenses/by-sa/4.0/ .
7+
8+
NOTE: The rights holder(s) for this work explicitly require that the attribution
9+
conditions of this license are enforced. Use in part or in whole of this data is
10+
permitted only under the condition that the scientific background of the
11+
Licensed Material will be CITED IN ANY PUBLICATIONS ARISING FROM ITS USE. The
12+
required references are specified in this file and must be included in resulting works.
13+
14+
15+
#########################################################################
16+
# #
17+
# Semi-relativistic, self-consistent charge Slater-Koster tables for #
18+
# density-functional based tight-binding (DFTB) for materials science #
19+
# simulations." GPQIT, UNIVERSIDADE FEDERAL DE MINAS GERAIS, 2009-2013 #
20+
# #
21+
# Maicon P. Lourenco (maiconpl01@gmail.com, maicon_pl@yahoo.com.br) #
22+
# Augusto F. Oliveira (augustof.chem@gmail.com) #
23+
# Helio A. Duarte (duarteh@ufmg.br, helioaduarte@gmail.com) #
24+
# #
25+
#########################################################################
26+
27+
Required references
28+
-------------------
29+
30+
Complete set:
31+
[1]
32+
J. Frenzel, A. F. Oliveira N. Jardillier, T.Heine & G Seifert
33+
"Semi-relativistic, self-consistent charge Slater-Koster tables for
34+
density-functional based tight-binding (DFTB) for materials
35+
science simulations." TU-Dresden 2004-2009.
36+
37+
Mg-O-Si-H:
38+
[2]
39+
Lourenco, M. P.; de Oliveira, C.; Oliveira, A. F.; Guimarães, L.;
40+
Duarte, H. A.; Structural, Electronic, and Mechanical Properties
41+
of Single-Walled Chrysotile Nanotube Models.
42+
Phys. Chem. C, 2012, 116 (17). DOI: 10.1021/jp301048p
43+
Guimaraes, L., Enyashin, A. N., Frenzel, J., Heine, T., Duarte, H. A.
44+
& Seifert, G., "Imogolite Nanotubes: Stability, electronic and
45+
mechanical properties", Nano, 2007, 1, 362-368.
46+
http://dx.doi.org/10.1021/nn700184k
47+
48+
Details of the atomic calculations:
49+
-----------------------------------
50+
51+
DFT, semi-relativistic, V_xc=Ceperly-Alder, potential super-position,
52+
STO basis-functions with 5 values for xi and i=0,1,2,3
53+
(Seifert,Phys.Chem.A,111(26),5609-5613,2007)
54+
additional harmonic potential (r/r0)^n0 with n0=2 and r0(H)=1.3,
55+
r0(O)=2.7, r0(Mg)=5.1 and r0(Si)=4.2 for s,p functions
56+
and r0(Si)=2.1 for d-functions (r0 in atomic units).
57+
58+
Repulsive potentials are fitted to work with the following systems:
59+
------------------------------------------------------------------
60+
61+
1) Mg-O-Si-H (Ref. [2])
62+
Chrysotile nanotubes

RELEASE.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
# Parameter set magsil-1-1
2+
3+
Density Functional Tight Binding (DFTB) parameter set for chrisotyle nanotubes.
4+
5+
Before applying it in your work, **consult the [README](README) file to ensure correct usage**.
6+
7+
8+
## License Information
9+
10+
The parameter set is distributed under the [Creative Commons Attribution-ShareAlike 4.0 International (CC-BY-SA)](LICENSE) license.
11+
12+
**Important Note:** The creators of this work require that you **adhere to the attribution requirements** specified by this license. If you use this data, either in part or in full, in any research or publication, you must properly cite the scientific references associated with this material. **The necessary citations are listed in the [README](README) file and must be included in all resulting publications.**

0 commit comments

Comments
 (0)