cfin-hpc-tools 0.2.3b0__tar.gz

cfin_hpc_tools-0.2.3b0/LICENSE.txt

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) [year] [fullname]
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

cfin_hpc_tools-0.2.3b0/PKG-INFO

@@ -0,0 +1,93 @@
+Metadata-Version: 2.4
+Name: cfin-hpc-tools
+Version: 0.2.3b0
+Summary: Some general grid-engine HPC tools, mainly geared for UCL systems but should be generalisable. Note this is not a UCL endorsed package.
+Author-email: Chris Finan <c.finan@ucl.ac.uk>
+License-Expression: GPL-3.0-or-later
+Project-URL: Homepage, https://cfinan.gitlab.io/cluster
+Project-URL: Repository, https://gitlab.com/cfinan/cluster
+Classifier: Programming Language :: Python
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: Implementation :: CPython
+Classifier: Programming Language :: Python :: Implementation :: PyPy
+Requires-Python: <3.14,>=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE.txt
+Requires-Dist: terminaltables>=3.1
+Requires-Dist: cfin-pyaddons
+Provides-Extra: dev
+Requires-Dist: pytest; extra == "dev"
+Requires-Dist: pytest-dependency; extra == "dev"
+Requires-Dist: flake8; extra == "dev"
+Requires-Dist: bump2version; extra == "dev"
+Requires-Dist: build; extra == "dev"
+Requires-Dist: twine; extra == "dev"
+Dynamic: license-file
+
+# Getting started with hpc-tools
+
+__version__: `0.2.3b0`
+
+[hpc-tools](https://gitlab.com/cfinan/cluster) is a Python package with some additional bash scripts/configuration files designed to simplify submitting array jobs on a cluster. Whilst it is written with Grid Engine in mind it can probably be re-purposed for other systems (such as LSF) - although this has not been tested in any way. Also, this has only been tested on the University College London (UCL) systems, Myriad and the CS cluster.
+
+There is [online](https://cfinan.gitlab.io/cluster/index.html) documentation for hpc-tools and offline PDF documentation can be downloaded [here](https://gitlab.com/cfinan/cluster/-/blob/master/resources/pdf/hpc-tools.pdf).
+
+## Installation instructions
+At present, hpc-tools is undergoing development and no packages exist yet on PyPi. Therefore it is recommended that it is installed in either of the two ways listed below. First, clone this repository and then `cd` to the root of the repository.
+
+### Installation using pip
+
+```
+pip install cfin-hpc-tools
+```
+
+### Installation using conda
+A conda build is also available for Python v3.7, v3.8 and v3.9 on linux-64.
+```
+conda install -c cfin cfin-hpc-tools
+```
+
+### Post Python install
+After installation of hpc-tools, there are some manual setup steps.
+
+#### Setup a mapping file
+The main submission script, `pyjasub` works by building job submission commands from user arguments. Therefore there is a mapping step to map between the user aguments and the cluster arguments. This happens internally but how the mapping is performed is controlled by a mapping config file. Examples, can be seen in the `./resources/mappings` directory of the repository and is also shown below:
+
+```
+[mappings]
+array=-t {0}-{1}:{2}
+
+# Multiple arguments are separated by commas, such as two memory arguments
+mem=-l hmem={0}, -l vmem={0}
+time=-l h_rt={0}
+nodes=-l hostname={0}
+shell=-S {0}
+out=-o {0}
+err=-e {0}
+batch=-tc {0}
+tmp_size=-l tmpfs={0}
+scratch_size=-l tscratch={0}
+```
+
+This follows a `.ini` format and and the Python formatting characters `{0}`, `{1}` etc... will be substituted with arguments. The mappings should be under the section header `[mappings]`.
+
+As a single the mappings file is expected per system, the location of the mappings file should be set in your `~/.bashrc`:
+
+```
+export QSUB_PYTHON_MAPPING="/path/to/mappings.conf"
+```
+
+As the mappings file is a potential security risk, is should only be readable by you. This is checked by `pyjasub` and if any other users have any of `rwx` on the mapping file then `pyjasub` will error out with a `PermissionError`.
+
+The abstraction of the cluster arguments has some plusses and minuses, it allows similar commands and job files can be used in different setups. However, this is at the expense of granular control. Having said that `pyjasub` can handle most everyday cluster uses and can probably be extended easily. Currently, `pyjasub` has only really been tested using `GridEngine`, however, it should be able to be adapted for `LSF`.
+
+#### Add the `bin` directory to your `PATH`
+There are a number of bash scripts used by `pyjasub`. Whilst, they are not obligatory and the user has full control of the task script, they can be used to perform some setup and cleanup operations. If you make sure that the directory `.resources/bin` is added to your `PATH`, for example, in your `~/.bashrc` file:
+
+```
+export "${PATH}:/path/to/cluster/resources/bin"
+```

cfin_hpc_tools-0.2.3b0/README.md

@@ -0,0 +1,63 @@
+# Getting started with hpc-tools
+
+__version__: `0.2.3b0`
+
+[hpc-tools](https://gitlab.com/cfinan/cluster) is a Python package with some additional bash scripts/configuration files designed to simplify submitting array jobs on a cluster. Whilst it is written with Grid Engine in mind it can probably be re-purposed for other systems (such as LSF) - although this has not been tested in any way. Also, this has only been tested on the University College London (UCL) systems, Myriad and the CS cluster.
+
+There is [online](https://cfinan.gitlab.io/cluster/index.html) documentation for hpc-tools and offline PDF documentation can be downloaded [here](https://gitlab.com/cfinan/cluster/-/blob/master/resources/pdf/hpc-tools.pdf).
+
+## Installation instructions
+At present, hpc-tools is undergoing development and no packages exist yet on PyPi. Therefore it is recommended that it is installed in either of the two ways listed below. First, clone this repository and then `cd` to the root of the repository.
+
+### Installation using pip
+
+```
+pip install cfin-hpc-tools
+```
+
+### Installation using conda
+A conda build is also available for Python v3.7, v3.8 and v3.9 on linux-64.
+```
+conda install -c cfin cfin-hpc-tools
+```
+
+### Post Python install
+After installation of hpc-tools, there are some manual setup steps.
+
+#### Setup a mapping file
+The main submission script, `pyjasub` works by building job submission commands from user arguments. Therefore there is a mapping step to map between the user aguments and the cluster arguments. This happens internally but how the mapping is performed is controlled by a mapping config file. Examples, can be seen in the `./resources/mappings` directory of the repository and is also shown below:
+
+```
+[mappings]
+array=-t {0}-{1}:{2}
+
+# Multiple arguments are separated by commas, such as two memory arguments
+mem=-l hmem={0}, -l vmem={0}
+time=-l h_rt={0}
+nodes=-l hostname={0}
+shell=-S {0}
+out=-o {0}
+err=-e {0}
+batch=-tc {0}
+tmp_size=-l tmpfs={0}
+scratch_size=-l tscratch={0}
+```
+
+This follows a `.ini` format and and the Python formatting characters `{0}`, `{1}` etc... will be substituted with arguments. The mappings should be under the section header `[mappings]`.
+
+As a single the mappings file is expected per system, the location of the mappings file should be set in your `~/.bashrc`:
+
+```
+export QSUB_PYTHON_MAPPING="/path/to/mappings.conf"
+```
+
+As the mappings file is a potential security risk, is should only be readable by you. This is checked by `pyjasub` and if any other users have any of `rwx` on the mapping file then `pyjasub` will error out with a `PermissionError`.
+
+The abstraction of the cluster arguments has some plusses and minuses, it allows similar commands and job files can be used in different setups. However, this is at the expense of granular control. Having said that `pyjasub` can handle most everyday cluster uses and can probably be extended easily. Currently, `pyjasub` has only really been tested using `GridEngine`, however, it should be able to be adapted for `LSF`.
+
+#### Add the `bin` directory to your `PATH`
+There are a number of bash scripts used by `pyjasub`. Whilst, they are not obligatory and the user has full control of the task script, they can be used to perform some setup and cleanup operations. If you make sure that the directory `.resources/bin` is added to your `PATH`, for example, in your `~/.bashrc` file:
+
+```
+export "${PATH}:/path/to/cluster/resources/bin"
+```

cfin_hpc_tools-0.2.3b0/cfin_hpc_tools.egg-info/PKG-INFO

@@ -0,0 +1,93 @@
+Metadata-Version: 2.4
+Name: cfin-hpc-tools
+Version: 0.2.3b0
+Summary: Some general grid-engine HPC tools, mainly geared for UCL systems but should be generalisable. Note this is not a UCL endorsed package.
+Author-email: Chris Finan <c.finan@ucl.ac.uk>
+License-Expression: GPL-3.0-or-later
+Project-URL: Homepage, https://cfinan.gitlab.io/cluster
+Project-URL: Repository, https://gitlab.com/cfinan/cluster
+Classifier: Programming Language :: Python
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: Implementation :: CPython
+Classifier: Programming Language :: Python :: Implementation :: PyPy
+Requires-Python: <3.14,>=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE.txt
+Requires-Dist: terminaltables>=3.1
+Requires-Dist: cfin-pyaddons
+Provides-Extra: dev
+Requires-Dist: pytest; extra == "dev"
+Requires-Dist: pytest-dependency; extra == "dev"
+Requires-Dist: flake8; extra == "dev"
+Requires-Dist: bump2version; extra == "dev"
+Requires-Dist: build; extra == "dev"
+Requires-Dist: twine; extra == "dev"
+Dynamic: license-file
+
+# Getting started with hpc-tools
+
+__version__: `0.2.3b0`
+
+[hpc-tools](https://gitlab.com/cfinan/cluster) is a Python package with some additional bash scripts/configuration files designed to simplify submitting array jobs on a cluster. Whilst it is written with Grid Engine in mind it can probably be re-purposed for other systems (such as LSF) - although this has not been tested in any way. Also, this has only been tested on the University College London (UCL) systems, Myriad and the CS cluster.
+
+There is [online](https://cfinan.gitlab.io/cluster/index.html) documentation for hpc-tools and offline PDF documentation can be downloaded [here](https://gitlab.com/cfinan/cluster/-/blob/master/resources/pdf/hpc-tools.pdf).
+
+## Installation instructions
+At present, hpc-tools is undergoing development and no packages exist yet on PyPi. Therefore it is recommended that it is installed in either of the two ways listed below. First, clone this repository and then `cd` to the root of the repository.
+
+### Installation using pip
+
+```
+pip install cfin-hpc-tools
+```
+
+### Installation using conda
+A conda build is also available for Python v3.7, v3.8 and v3.9 on linux-64.
+```
+conda install -c cfin cfin-hpc-tools
+```
+
+### Post Python install
+After installation of hpc-tools, there are some manual setup steps.
+
+#### Setup a mapping file
+The main submission script, `pyjasub` works by building job submission commands from user arguments. Therefore there is a mapping step to map between the user aguments and the cluster arguments. This happens internally but how the mapping is performed is controlled by a mapping config file. Examples, can be seen in the `./resources/mappings` directory of the repository and is also shown below:
+
+```
+[mappings]
+array=-t {0}-{1}:{2}
+
+# Multiple arguments are separated by commas, such as two memory arguments
+mem=-l hmem={0}, -l vmem={0}
+time=-l h_rt={0}
+nodes=-l hostname={0}
+shell=-S {0}
+out=-o {0}
+err=-e {0}
+batch=-tc {0}
+tmp_size=-l tmpfs={0}
+scratch_size=-l tscratch={0}
+```
+
+This follows a `.ini` format and and the Python formatting characters `{0}`, `{1}` etc... will be substituted with arguments. The mappings should be under the section header `[mappings]`.
+
+As a single the mappings file is expected per system, the location of the mappings file should be set in your `~/.bashrc`:
+
+```
+export QSUB_PYTHON_MAPPING="/path/to/mappings.conf"
+```
+
+As the mappings file is a potential security risk, is should only be readable by you. This is checked by `pyjasub` and if any other users have any of `rwx` on the mapping file then `pyjasub` will error out with a `PermissionError`.
+
+The abstraction of the cluster arguments has some plusses and minuses, it allows similar commands and job files can be used in different setups. However, this is at the expense of granular control. Having said that `pyjasub` can handle most everyday cluster uses and can probably be extended easily. Currently, `pyjasub` has only really been tested using `GridEngine`, however, it should be able to be adapted for `LSF`.
+
+#### Add the `bin` directory to your `PATH`
+There are a number of bash scripts used by `pyjasub`. Whilst, they are not obligatory and the user has full control of the task script, they can be used to perform some setup and cleanup operations. If you make sure that the directory `.resources/bin` is added to your `PATH`, for example, in your `~/.bashrc` file:
+
+```
+export "${PATH}:/path/to/cluster/resources/bin"
+```

cfin_hpc_tools-0.2.3b0/cfin_hpc_tools.egg-info/SOURCES.txt

@@ -0,0 +1,139 @@
+LICENSE.txt
+README.md
+pyproject.toml
+cfin_hpc_tools.egg-info/PKG-INFO
+cfin_hpc_tools.egg-info/SOURCES.txt
+cfin_hpc_tools.egg-info/dependency_links.txt
+cfin_hpc_tools.egg-info/entry_points.txt
+cfin_hpc_tools.egg-info/requires.txt
+cfin_hpc_tools.egg-info/top_level.txt
+docs/Makefile
+docs/make.bat
+docs/build/doctrees/contributing.doctree
+docs/build/doctrees/environment.pickle
+docs/build/doctrees/example_job_array.doctree
+docs/build/doctrees/getting_started.doctree
+docs/build/doctrees/index.doctree
+docs/build/doctrees/package_management.doctree
+docs/build/doctrees/scripts.doctree
+docs/build/doctrees/workflow.doctree
+docs/build/doctrees/scripts/make_jaf.doctree
+docs/build/doctrees/scripts/pyjasub.doctree
+docs/build/latex/LICRcyr2utf8.xdy
+docs/build/latex/LICRlatin2utf8.xdy
+docs/build/latex/LatinRules.xdy
+docs/build/latex/Makefile
+docs/build/latex/hpc-tools.aux
+docs/build/latex/hpc-tools.fdb_latexmk
+docs/build/latex/hpc-tools.fls
+docs/build/latex/hpc-tools.idx
+docs/build/latex/hpc-tools.ilg
+docs/build/latex/hpc-tools.ind
+docs/build/latex/hpc-tools.log
+docs/build/latex/hpc-tools.out
+docs/build/latex/hpc-tools.pdf
+docs/build/latex/hpc-tools.tex
+docs/build/latex/hpc-tools.toc
+docs/build/latex/latexmkjarc
+docs/build/latex/latexmkrc
+docs/build/latex/make.bat
+docs/build/latex/python.ist
+docs/build/latex/sphinx.sty
+docs/build/latex/sphinx.xdy
+docs/build/latex/sphinxhighlight.sty
+docs/build/latex/sphinxhowto.cls
+docs/build/latex/sphinxlatexadmonitions.sty
+docs/build/latex/sphinxlatexcontainers.sty
+docs/build/latex/sphinxlatexgraphics.sty
+docs/build/latex/sphinxlatexindbibtoc.sty
+docs/build/latex/sphinxlatexlists.sty
+docs/build/latex/sphinxlatexliterals.sty
+docs/build/latex/sphinxlatexnumfig.sty
+docs/build/latex/sphinxlatexobjects.sty
+docs/build/latex/sphinxlatexshadowbox.sty
+docs/build/latex/sphinxlatexstyleheadings.sty
+docs/build/latex/sphinxlatexstylepage.sty
+docs/build/latex/sphinxlatexstyletext.sty
+docs/build/latex/sphinxlatextables.sty
+docs/build/latex/sphinxmanual.cls
+docs/build/latex/sphinxmessages.sty
+docs/build/latex/sphinxoptionsgeometry.sty
+docs/build/latex/sphinxoptionshyperref.sty
+docs/build/latex/sphinxpackagecyrillic.sty
+docs/build/latex/sphinxpackagefootnote.sty
+docs/source/conf.py
+docs/source/contributing.rst
+docs/source/example_job_array.md
+docs/source/getting_started.md
+docs/source/index.rst
+docs/source/package_management.md
+docs/source/scripts.rst
+docs/source/workflow.rst
+docs/source/_static/style.css
+docs/source/_templates/layout.html
+docs/source/scripts/make_jaf.rst
+docs/source/scripts/pyjasub.rst
+hpc_tools/__init__.py
+hpc_tools/_version.py
+hpc_tools/common.py
+hpc_tools/file_helper.py
+hpc_tools/make_general_job_array_file.py
+hpc_tools/pyjasub.py
+resources/bash_scripts/README.md
+resources/bash_scripts/env_test.ini
+resources/bash_scripts/env_test.sh
+resources/bash_scripts/initialise_job.sh
+resources/bash_scripts/job_array_tests.sh
+resources/bash_scripts/post_run.sh
+resources/bash_scripts/pre_run.sh
+resources/bash_scripts/profile.sh
+resources/bash_scripts/run_job_array.sh
+resources/bash_scripts/skeleton_job_array_run.sh
+resources/bash_scripts/skeleton_job_array_task.sh
+resources/bash_scripts/tar_logs.sh
+resources/bin/README.md
+resources/bin/csub
+resources/bin/task_init.sh
+resources/bin/task_setup.sh
+resources/bin/wrap
+resources/ci_cd/README.md
+resources/ci_cd/before_script.sh
+resources/ci_cd/pages.sh
+resources/ci_cd/pypi-upload.sh
+resources/ci_cd/run_docker.sh
+resources/ci_cd/run_pages.sh
+resources/ci_cd/sphinx.txt
+resources/conda/build/py310/LICENSE
+resources/conda/build/py310/build.sh
+resources/conda/build/py310/meta.yaml
+resources/conda/build/py37/LICENSE
+resources/conda/build/py37/build.sh
+resources/conda/build/py37/meta.yaml
+resources/conda/build/py38/LICENSE
+resources/conda/build/py38/build.sh
+resources/conda/build/py38/meta.yaml
+resources/conda/build/py39/LICENSE
+resources/conda/build/py39/build.sh
+resources/conda/build/py39/meta.yaml
+resources/conda/envs/py310/conda_create.yaml
+resources/conda/envs/py310/conda_update.yaml
+resources/conda/envs/py37/conda_create.yaml
+resources/conda/envs/py37/conda_update.yaml
+resources/conda/envs/py38/conda_create.yaml
+resources/conda/envs/py38/conda_update.yaml
+resources/conda/envs/py39/conda_create.yaml
+resources/conda/envs/py39/conda_update.yaml
+resources/config/md5_sum.ini
+resources/example/README.md
+resources/example/create_example_files.sh
+resources/example/create_job_array.sh
+resources/example/example_job.cnf
+resources/example/example_task.sh
+resources/job_array/README.md
+resources/job_array/file-split-job-array.sh
+resources/mappings/README.md
+resources/mappings/cs_mappings.cnf
+resources/mappings/my_mappings.cnf
+resources/tasks/README.md
+resources/tasks/file-chunk-task.sh
+resources/tasks/md5sum.task.sh

cfin_hpc_tools-0.2.3b0/cfin_hpc_tools.egg-info/dependency_links.txt

@@ -0,0 +1 @@
+

cfin_hpc_tools-0.2.3b0/cfin_hpc_tools.egg-info/entry_points.txt

@@ -0,0 +1,3 @@
+[console_scripts]
+make-jaf = hpc_tools.make_general_job_array_file:main
+pyjasub = hpc_tools.pyjasub:main

cfin_hpc_tools-0.2.3b0/cfin_hpc_tools.egg-info/requires.txt

@@ -0,0 +1,10 @@
+terminaltables>=3.1
+cfin-pyaddons
+
+[dev]
+pytest
+pytest-dependency
+flake8
+bump2version
+build
+twine

cfin_hpc_tools-0.2.3b0/cfin_hpc_tools.egg-info/top_level.txt

@@ -0,0 +1,4 @@
+dist
+docs
+hpc_tools
+resources

cfin_hpc_tools-0.2.3b0/docs/Makefile

@@ -0,0 +1,20 @@
+# Minimal makefile for Sphinx documentation
+#
+
+# You can set these variables from the command line, and also
+# from the environment for the first two.
+SPHINXOPTS    ?=
+SPHINXBUILD   ?= sphinx-build
+SOURCEDIR     = source
+BUILDDIR      = build
+
+# Put it first so that "make" without argument is like "make help".
+help:
+	@$(SPHINXBUILD) -M help "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O)
+
+.PHONY: help Makefile
+
+# Catch-all target: route all unknown targets to Sphinx using the new
+# "make mode" option.  $(O) is meant as a shortcut for $(SPHINXOPTS).
+%: Makefile
+	@$(SPHINXBUILD) -M $@ "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O)

cfin_hpc_tools-0.2.3b0/docs/build/latex/LICRcyr2utf8.xdy

@@ -0,0 +1,101 @@
+;; -*- coding: utf-8; mode: Lisp; -*-
+;; style file for xindy
+;; filename: LICRcyr2utf8.xdy
+;; description: style file for xindy which maps back LaTeX Internal
+;;   Character Representation of Cyrillic to utf-8
+;; usage: for use with pdflatex produced .idx files.
+;; Contributed by the Sphinx team, July 2018.
+(merge-rule "\IeC {\'\CYRG }" "Ѓ" :string)
+(merge-rule "\IeC {\'\CYRK }" "Ќ" :string)
+(merge-rule "\IeC {\'\cyrg }" "ѓ" :string)
+(merge-rule "\IeC {\'\cyrk }" "ќ" :string)
+(merge-rule "\IeC {\CYRA }" "А" :string)
+(merge-rule "\IeC {\CYRB }" "Б" :string)
+(merge-rule "\IeC {\CYRC }" "Ц" :string)
+(merge-rule "\IeC {\CYRCH }" "Ч" :string)
+(merge-rule "\IeC {\CYRD }" "Д" :string)
+(merge-rule "\IeC {\CYRDJE }" "Ђ" :string)
+(merge-rule "\IeC {\CYRDZE }" "Ѕ" :string)
+(merge-rule "\IeC {\CYRDZHE }" "Џ" :string)
+(merge-rule "\IeC {\CYRE }" "Е" :string)
+(merge-rule "\IeC {\CYREREV }" "Э" :string)
+(merge-rule "\IeC {\CYRERY }" "Ы" :string)
+(merge-rule "\IeC {\CYRF }" "Ф" :string)
+(merge-rule "\IeC {\CYRG }" "Г" :string)
+(merge-rule "\IeC {\CYRGUP }" "Ґ" :string)
+(merge-rule "\IeC {\CYRH }" "Х" :string)
+(merge-rule "\IeC {\CYRHRDSN }" "Ъ" :string)
+(merge-rule "\IeC {\CYRI }" "И" :string)
+(merge-rule "\IeC {\CYRIE }" "Є" :string)
+(merge-rule "\IeC {\CYRII }" "І" :string)
+(merge-rule "\IeC {\CYRISHRT }" "Й" :string)
+(merge-rule "\IeC {\CYRJE }" "Ј" :string)
+(merge-rule "\IeC {\CYRK }" "К" :string)
+(merge-rule "\IeC {\CYRL }" "Л" :string)
+(merge-rule "\IeC {\CYRLJE }" "Љ" :string)
+(merge-rule "\IeC {\CYRM }" "М" :string)
+(merge-rule "\IeC {\CYRN }" "Н" :string)
+(merge-rule "\IeC {\CYRNJE }" "Њ" :string)
+(merge-rule "\IeC {\CYRO }" "О" :string)
+(merge-rule "\IeC {\CYRP }" "П" :string)
+(merge-rule "\IeC {\CYRR }" "Р" :string)
+(merge-rule "\IeC {\CYRS }" "С" :string)
+(merge-rule "\IeC {\CYRSFTSN }" "Ь" :string)
+(merge-rule "\IeC {\CYRSH }" "Ш" :string)
+(merge-rule "\IeC {\CYRSHCH }" "Щ" :string)
+(merge-rule "\IeC {\CYRT }" "Т" :string)
+(merge-rule "\IeC {\CYRTSHE }" "Ћ" :string)
+(merge-rule "\IeC {\CYRU }" "У" :string)
+(merge-rule "\IeC {\CYRUSHRT }" "Ў" :string)
+(merge-rule "\IeC {\CYRV }" "В" :string)
+(merge-rule "\IeC {\CYRYA }" "Я" :string)
+(merge-rule "\IeC {\CYRYI }" "Ї" :string)
+(merge-rule "\IeC {\CYRYO }" "Ё" :string)
+(merge-rule "\IeC {\CYRYU }" "Ю" :string)
+(merge-rule "\IeC {\CYRZ }" "З" :string)
+(merge-rule "\IeC {\CYRZH }" "Ж" :string)
+(merge-rule "\IeC {\cyra }" "а" :string)
+(merge-rule "\IeC {\cyrb }" "б" :string)
+(merge-rule "\IeC {\cyrc }" "ц" :string)
+(merge-rule "\IeC {\cyrch }" "ч" :string)
+(merge-rule "\IeC {\cyrd }" "д" :string)
+(merge-rule "\IeC {\cyrdje }" "ђ" :string)
+(merge-rule "\IeC {\cyrdze }" "ѕ" :string)
+(merge-rule "\IeC {\cyrdzhe }" "џ" :string)
+(merge-rule "\IeC {\cyre }" "е" :string)
+(merge-rule "\IeC {\cyrerev }" "э" :string)
+(merge-rule "\IeC {\cyrery }" "ы" :string)
+(merge-rule "\IeC {\cyrf }" "ф" :string)
+(merge-rule "\IeC {\cyrg }" "г" :string)
+(merge-rule "\IeC {\cyrgup }" "ґ" :string)
+(merge-rule "\IeC {\cyrh }" "х" :string)
+(merge-rule "\IeC {\cyrhrdsn }" "ъ" :string)
+(merge-rule "\IeC {\cyri }" "и" :string)
+(merge-rule "\IeC {\cyrie }" "є" :string)
+(merge-rule "\IeC {\cyrii }" "і" :string)
+(merge-rule "\IeC {\cyrishrt }" "й" :string)
+(merge-rule "\IeC {\cyrje }" "ј" :string)
+(merge-rule "\IeC {\cyrk }" "к" :string)
+(merge-rule "\IeC {\cyrl }" "л" :string)
+(merge-rule "\IeC {\cyrlje }" "љ" :string)
+(merge-rule "\IeC {\cyrm }" "м" :string)
+(merge-rule "\IeC {\cyrn }" "н" :string)
+(merge-rule "\IeC {\cyrnje }" "њ" :string)
+(merge-rule "\IeC {\cyro }" "о" :string)
+(merge-rule "\IeC {\cyrp }" "п" :string)
+(merge-rule "\IeC {\cyrr }" "р" :string)
+(merge-rule "\IeC {\cyrs }" "с" :string)
+(merge-rule "\IeC {\cyrsftsn }" "ь" :string)
+(merge-rule "\IeC {\cyrsh }" "ш" :string)
+(merge-rule "\IeC {\cyrshch }" "щ" :string)
+(merge-rule "\IeC {\cyrt }" "т" :string)
+(merge-rule "\IeC {\cyrtshe }" "ћ" :string)
+(merge-rule "\IeC {\cyru }" "у" :string)
+(merge-rule "\IeC {\cyrushrt }" "ў" :string)
+(merge-rule "\IeC {\cyrv }" "в" :string)
+(merge-rule "\IeC {\cyrya }" "я" :string)
+(merge-rule "\IeC {\cyryi }" "ї" :string)
+(merge-rule "\IeC {\cyryo }" "ё" :string)
+(merge-rule "\IeC {\cyryu }" "ю" :string)
+(merge-rule "\IeC {\cyrz }" "з" :string)
+(merge-rule "\IeC {\cyrzh }" "ж" :string)