<commit_before>---

# Misc variables...
pv_name: pv-chemcentral-postgresql
pvc_name: chemcentral-postgresql-claim
data_loader_pv_name: pv-chemcentral-loader
data_loader_pvc_name: chemcentral-data-loader-pvc

# Parameters for the ChemCentral Loader.
#
# Typical loader classes are: -
#
# - EMoleculesBBSmilesLoader
# - EnamineRealDsiLoader
# - MolportSmilesLoader
#
# The class controls the flavour of loader being launched.
loader_class: MolportSmilesLoader
# The file (used by single-file loaders)
loader_file: -
# The loader base directory and file pattern
# (for Molport-like multi-file loaders)
loader_dir: molport-2018-08
loader_pattern: iis_smiles-*.txt.gz
# The number of molecules to load (0 == all)
loader_limit: 0

# The ChemCentral Service Account
# in the Infrastructure project
oc_cc_infra_sa: chemcentral-postgres

# Here PVs used by the application (the squonk-work-dir for example)
# are returned to an 'Available' state if they're currently
# in a 'Released' state. Note: it is the user's responsibility
# to protect themselves for data loss here. This will inspect the
# "state" of all PVs in the squonk *and* infrastructure projects.
recycle_released_pvs: yes

# What volume type are we using? One of: -
#
# - dynamic
# - nfs
# - none
#
#   When using `dynamic' remember to set
#   the accompanying 'volume_storage_class' variable (see below)
#
#   When using 'nfs' you must have provisioned the NFS volumes
#
#   When set to 'none' the user is expected to have provisioned
#   the persistent volumes and claims suitable for the project.
oc_cc_infra_volume_type: "{{ ansible_env.OC_INFRA_VOLUME_TYPE }}"

# When using dynamic volumes the storage
# class needs to be defined...
volume_storage_class: cloud-block-volume
<commit_msg>- Fixed error with unused parameter value<commit_after>---

# Misc variables...
pv_name: pv-chemcentral-postgresql
pvc_name: chemcentral-postgresql-claim
data_loader_pv_name: pv-chemcentral-loader
data_loader_pvc_name: chemcentral-data-loader-pvc

# Parameters for the ChemCentral Loader.
#
# Typical loader classes are: -
#
# - EMoleculesBBSmilesLoader
# - EnamineRealDsiLoader
# - MolportSmilesLoader
#
# The class controls the flavour of loader being launched.
loader_class: MolportSmilesLoader
# The file (used by single-file loaders)
loader_file: Undefined
# The loader base directory and file pattern
# (for Molport-like multi-file loaders)
loader_dir: molport-2018-08
loader_pattern: iis_smiles-*.txt.gz
# The number of molecules to load (0 == all)
loader_limit: 0

# The ChemCentral Service Account
# in the Infrastructure project
oc_cc_infra_sa: chemcentral-postgres

# Here PVs used by the application (the squonk-work-dir for example)
# are returned to an 'Available' state if they're currently
# in a 'Released' state. Note: it is the user's responsibility
# to protect themselves for data loss here. This will inspect the
# "state" of all PVs in the squonk *and* infrastructure projects.
recycle_released_pvs: yes

# What volume type are we using? One of: -
#
# - dynamic
# - nfs
# - none
#
#   When using `dynamic' remember to set
#   the accompanying 'volume_storage_class' variable (see below)
#
#   When using 'nfs' you must have provisioned the NFS volumes
#
#   When set to 'none' the user is expected to have provisioned
#   the persistent volumes and claims suitable for the project.
oc_cc_infra_volume_type: "{{ ansible_env.OC_INFRA_VOLUME_TYPE }}"

# When using dynamic volumes the storage
# class needs to be defined...
volume_storage_class: cloud-block-volume

{'fraction_non_alphanumeric': 0.07923033389926429, 'fraction_numerical': 0.004527447651386531, 'mean_word_length': 4.69243156199678, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1370933', 'n_tokens_mistral': 1131, 'n_tokens_neox': 1080, 'n_words': 399}