# Details on biodb

Pierrick Roger

#### 10 June 2021

#### Abstract

AAA

#### Package

biodb 1.0.4

# 1 Introduction

In this document are presented different aspects of biodb in more details: the object oriented programming model adopted, its architecture, how to configure the package, how to create connectors and delete them, understanding the request scheduler, how to tune the logging system.

# 2 Object oriented programming (OOP) model

In R, you may already know the two classical OOP models S3 and S4. S4 is certainly the most used model, and is based on an original system of generic methods that can be specialized for each class.

Two more recent OOP models exist in R: Reference Classes (aka RC or R5 from package methods) and R6 (from package R6). These two models are very similar. The biodb package uses a mix of RC and R6, but will switch completely to R6 in a near future.

They both implement an object model and based on references. This means that each object is unique, never copied and accessed through references. In this system, the created objects are not copied, but their reference are copied. Any modification of an object in one part of the code, will be visible from all other parts of the code. This means that when you pass an instance to a function, that function is able to modify the instance.

Also, in RC and R6, the functions are attached to the object. In other words, the mechanism to call a function on a object is different from S4. The calling mechanism is thus slightly different, in RC or R6 we write `myObject$myFunction()` instead of `myFunction(myObject)` in S4.

See Reference Classes chapter from package methods and this introduction to R6 for more details.

# 3 Initialization & termination

biodb uses an initialization/termination scheme. You must first initialize the library by creating an instance of the main class `BiodbMain`:

    mybiodb <- biodb::newInst()

    ## INFO  [14:51:50.754] Loading definitions from package biodb version 1.0.4.

    ## Warning in Sys.setlocale(locale = "en_US.UTF-8"): OS reports request to set
    ## locale to "en_US.UTF-8" cannot be honored

And when you are done with the library, you have to terminate the instance explicitly:

    mybiodb$terminate()

    ## INFO  [14:51:51.363] Closing BiodbMain instance...

We will need a biodb instance for the rest of this vignette. Let us call the constructor again:

    mybiodb <- biodb::newInst()

    ## INFO  [14:51:51.410] Loading definitions from package biodb version 1.0.4.

    ## Warning in Sys.setlocale(locale = "en_US.UTF-8"): OS reports request to set
    ## locale to "en_US.UTF-8" cannot be honored

# 4 Management classes

Several class instances are attached to the biodb instance for managing different aspects of biodb: creating connectors, configuring biodb, accessing the cache system, etc.

See table 1 for a list of these instances and their purpose.

Table 1: The management classes
Only one instance is created for each of theses classes, and attached to the `BiodbMain` instance,
Class | Method to get the instance | Description
--- | --- | ---
BiodbConfig | `mybiodb$getConfig()` | Access to configuration values, and modification.
BiodbDbsInfo | `mybiodb$getDbsInfo()` | Databases information (name, description, request frequency, etc).
BiodbEntryFields | `mybiodb$getEntryFields()` | Entry fields information (description, type, cardinality, etc).
BiodbFactory | `mybiodb$getFactory()` | Creation of connectors and entries.
BiodbPersistentCache | `mybiodb$getPersistentCache()` | Cache system on disk.
BiodbRequestScheduler | `mybiodb$getRequestScheduler()` | Send requests to web servers, respecting the frequency limit for each database server.

# 5 Configuration

Several configuration values are defined inside the `definitions.yml` file of biodb. New configuration values can also be defined in extension packages.

To get a list of the existing configuration keys with their current value, run:

    mybiodb$getConfig()

    ## Biodb configuration instance.
    ##   Values:
    ##      allow.huge.downloads :  TRUE
    ##      autoload.extra.pkgs :  FALSE
    ##      cache.all.requests :  TRUE
    ##      cache.directory :  C:\Users\BIOCBU~1\AppData\Local/biodb/biodb/Cache
    ##      cache.read.only :  FALSE
    ##      cache.subfolders :  TRUE
    ##      cache.system :  TRUE
    ##      compute.fields :  TRUE
    ##      dwnld.chunk.size :  NA
    ##      dwnld.timeout :  3600
    ##      entries.sep :  |
    ##      force.locale :  TRUE
    ##      intra.field.name.sep :  .
    ##      multival.field.sep :  ;
    ##      offline :  FALSE
    ##      proton.mass :  1.007276
    ##      svn.binary.path :  C:\PROGRA~1\TORTOI~1\bin\svn.exe
    ##      test.functions :  NA
    ##      use.cache.for.local.db :  FALSE
    ##      useragent :  NA

To get a data frame of all keys with their title (short description), type and default value, call (result in 2):

    x <- mybiodb$getConfig()$listKeys()

Table 2: List of keys with some of their parameters
key | title | type | default
--- | --- | --- | ---
allow.huge.downloads | Authorize download of big files. | logical | TRUE
autoload.extra.pkgs | Enable automatic loading of extension packages. | logical | FALSE
cache.all.requests | Enable caching of all requests and their results. | logical | TRUE
cache.directory | Path to the cache folder. | character | C:~1/biodb/biodb/Cache
cache.read.only | Set cache system in read only mode. | logical | FALSE
cache.subfolders | Use subfolders to divide files into cache folder. | logical | TRUE
cache.system | Enable cache system. | logical | TRUE
use.cache.for.local.db | Enable the use of the cache system also for local databases. | logical | FALSE
dwnld.chunk.size | The number of new entries to wait before saving them into the cache. | integer | NA
dwnld.timeout | Download timeout in seconds. | integer | 3600
compute.fields | Enable automatic computing of missing fields. | logical | TRUE
force.locale | Force change of current locale for the application. | logical | TRUE
multival.field.sep | The separator used for concatenating values. | character | ;
intra.field.name.sep | The separator use for building a field name. | character | .
entries.sep | The separator used between values from different entries. | character | |
offline | Stops sending requests to the network. | logical | FALSE
proton.mass | The mass of one proton. | numeric | 1.0072765
svn.binary.path | The path to the svn binary. | character | C:11.exe
test.functions | List of functions to test. | character | NA
useragent | The application name and contact address to send to the contacted web server. | character | NA

To get the description of a key, run:

    mybiodb$getConfig()$getDescription('cache.directory')

    ## [1] "The directory in which cache files are stored. The default location depends on your operating system."

To get a value, run:

    mybiodb$getConfig()$get('cache.directory')

    ## [1] "C:\\Users\\BIOCBU~1\\AppData\\Local/biodb/biodb/Cache"

To set a field value, run:

    mybiodb$getConfig()$set('cache.directory', '~/my.biodb.cache')

If the field is boolean, you can use the following methods instead:

    mybiodb$getConfig()$enable('offline')

    ## INFO  [14:51:52.207] Enable offline.

    mybiodb$getConfig()$disable('offline')

    ## INFO  [14:51:52.207] Disable offline.

Configuration keys have default values. You can get a key’s default value with this call:

    mybiodb$getConfig()$getDefaultValue('cache.directory')

    ## [1] "C:\\Users\\BIOCBU~1\\AppData\\Local/biodb/biodb/Cache"

Environment variables can be used to overwrite default values. To get the name of the environment variable associated with a particular key, call the following method:

    mybiodb$getConfig()$getAssocEnvVar('cache.directory')

    ## [1] "BIODB_CACHE_DIRECTORY"

# 6 Databases information

Before creating any connector, you can information on the available databases and their connector classes.

Getting the databases info instance will print you a list of all available database connector classes:

    mybiodb$getDbsInfo()

    ## Biodb databases information instance.
    ## The following databases are defined:
    ##   comp.csv.file: Compound CSV File connector class.
    ##   comp.sqlite: Compound SQLite connector class.
    ##   mass.csv.file: Mass spectra CSV File connector class.
    ##   mass.sqlite: Mass spectra SQLite connector class.

If you want more information on one particular connector, run:

    mybiodb$getDbsInfo()$get('mass.csv.file')

    ## Mass spectra CSV File class.
    ##   Class: mass.csv.file.
    ##   Package: biodb.
    ##   Description: A connector to handle a mass spectra database stored inside a CSV file. It is possible to choose the separator for the CSV file, as well as match the column names with the biodb entry fields...
    ##   Entry content type: tsv.

# 7 Available database connectors

This package is delivered with two connectors for local databasses: MassCsvFile annd MassSqlite. However it is extendable, and in fact other packages already exist or will soon be made available on Bioconductor or GitHub for accessing other databases like ChEBI, Uniprot, HMDB, KEGG, Massbank or Lipidmaps. You may also write your own connector by extending biodb. If you are interested, a vignette explains what you need to do in details.

When creating the instance of the `BiodbMain` class you should have received a message like “Loading definitions from package …” if any extending package has also been installed on your system. Connector definitions found in extending packages are automatically loaded when instantiating `BiodbMain`, thus you do not need to call `library()` to individually load each extending package.

To get a list of available connectors, simply print information about your `BiodbMain` instance:

    mybiodb

# 8 Creating connectors

Connectors are created through the factory instance.

To get the factory instance, run:

    mybiodb$getFactory()

    ## Biodb factory instance.

Here is the creation of a Compound CSV File connector, using TSV file:

    chebi.tsv <- system.file("extdata", "chebi_extract.tsv", package='biodb')
    conn <- mybiodb$getFactory()$createConn('comp.csv.file', url=chebi.tsv)
    conn

    ## Compound CSV File instance.
    ##   Class: comp.csv.file.
    ##   Package: biodb.
    ##   Description: A connector to handle a compound database stored inside a CSV file. It is possible to choose the separator for the CSV file, as well as match the column names with the biodb entry fields..
    ##   Entry content type: tsv.
    ##   URLs: base.url: C:/Users/biocbuild/bbs-3.13-bioc/tmpdir/RtmpCYBmzI/Rinst2a1426cf5ad3/biodb/extdata/chebi_extract.tsv.
    ##   ID: comp.csv.file.
    ## INFO  [14:51:52.535] Loading file database "C:/Users/biocbuild/bbs-3.13-bioc/tmpdir/RtmpCYBmzI/Rinst2a1426cf5ad3/biodb/extdata/chebi_extract.tsv".

The connector instance allows you to send requests to the database to retrieve entries directly with `getEntry()`:

    conn$getEntry('1018')

    ## Biodb Compound CSV File entry instance 1018.

or run more complex queries like a search:

    conn$searchForEntries(list(monoisotopic.mass=list(value=136.05, delta=0.1)))

    ## [1] 1390

See vignette Manipulating entry objects to learn how to access database entries and manipulate them.

All the connectors inherit from super class `BiodbConn`, hence they share a set of common methods like `getEntryIds()`, `getEntry()` and `searchForEntries()`. Moreover a connector may inherit from special super classes like `BiodbMassdbConn` or `BiodbCompoundConn`, in which case they will inherit specific methods. In the case of `BiodbMassdbConn`, it will be methods targeted toward mass spectra like `getNbPeaks()`, `searchForMassSpectra()`, `msmsSearch()`, etc. In the case of `BiodbCompoundConn`, it will be `annotateMzValues()`. Those methods are generic and thus can be used with any connector inheriting the super class.

When creating a connector, the factory keeps a reference to it in a list. If you try to create again the same connector, the method `createConn()` will throw an error. However to can use the `getConn()` method to get back the connector instance from its identifier or database name (if there is only one instance for the database):

    conn <- mybiodb$getFactory()$getConn('comp.csv.file')

The factory is also responsible for creating the `BiodbEntry` objects, and as for the connectors, it stores them into a list (called the “volatile cache”). When asking again for the same entry, the factory will return the reference is has kept in the list.

To delete a connector, which is a good thing to do if you are not done with biodb but you have finished using a particular connector, run:

    mybiodb$getFactory()$deleteConn(conn)

    ## INFO  [14:51:52.988] Connector "comp.csv.file" deleted.

This will free all memory used for this connector, including the created entries. Be careful to do not keep those entry objects in some variable on your side, otherwise the memory will not be released by R.

# 9 Request scheduler

The `BiodbRequestScheduler` instance is responsible for sending requests to web server, taking care of respecting the frequency specified by the `scheduler.n` and `scheduler.t` parameters, and for receiving results and saving them to cache.

The cache is used to give back a result immediately without contacting the server, in case the exact same request has already been run previously.

You do not have to interact with the request scheduler, it runs as a back end component.

# 10 Entry fields information

The `BiodbEntryFields` instance stores information about all entry fields declared inside definitions YAML files.

Get the entry fields instance:

    mybiodb$getEntryFields()

    ## Biodb entry fields information instance.

Get information about a field:

    mybiodb$getEntryFields()$get('monoisotopic.mass')

    ## Entry field "monoisotopic.mass".
    ##   Description: Monoisotopic mass, in u (unified atomic mass units) or Da (Dalton). It is computed using the mass of the primary isotope of the elements including the mass defect (mass difference between neutron and proton, and nuclear binding energy). Used with high resolution mass spectrometers. See https://en.wikipedia.org/wiki/Monoisotopic_mass.
    ##   Class: double.
    ##   Type: mass.
    ##   Cardinality: one.
    ##   Aliases: exact.mass.

The object returned is a `BiodbEntryField` instance. See the help page of this class to get a list of all methods you can call on such an instance.

# 11 Persistent cache system

The persistent cache system is responsible for saving entry contents and results of web server requests onto disk, and reuse them later to avoid recontacting the web server.

Run the following method to get the instance of the `BiodbPersistentCache` class:

    mybiodb$getPersistentCache()

    ## Biodb persistent cache system instance.
    ##   The path to the cache system is: ~/my.biodb.cache
    ##   The cache is readable.
    ##   The cache is writable.

It is possible to delete files from the cache directly from the persistent cache instance. However it is a lot preferable to do it from the connector instance. If we open an instance of the ChEBI example connector from the vignette Creating a new connector. :

    source(system.file("extdata", "ChebiExConn.R", package='biodb'))
    source(system.file("extdata", "ChebiExEntry.R", package='biodb'))
    mybiodb$loadDefinitions(system.file("extdata", "chebi_ex.yml", package='biodb'))
    conn <- mybiodb$getFactory()$createConn('chebi.ex')

And load some entry:

    entry <- conn$getEntry('17001')

The entry is now downloaded into the cache system. We can check that with the following call:

    mybiodb$getPersistentCache()$fileExist(conn$getCacheId(), name='17001', ext=conn$getEntryFileExt())

    ## [1] TRUE

And get the path to the cache file:

    mybiodb$getPersistentCache()$getFilePath(conn$getCacheId(), name='17001', ext=conn$getEntryFileExt())

    ## [1] "~/my.biodb.cache/chebi.ex-0c5076ac2a43d16dbce503a44b09f649/17001.xml"

If we delete the entry content from the cache:

    conn$deleteAllEntriesFromPersistentCache()

The file does not exist anymore:

    mybiodb$getPersistentCache()$fileExist(conn$getCacheId(), name='17001', ext=conn$getEntryFileExt())

    ## [1] FALSE

But the entry object is still in memory. We need to delete entry instances with the following call:

    conn$deleteAllEntriesFromVolatileCache()

Note that the results of web server requests are still inside the cache folder. In order to force a new downloading of data, we need to erase those files too. The following call will erase all cache files associated with a connector, including the files deleted by `deleteAllEntriesFromPersistentCache()`:

    conn$deleteWholePersistentCache()

    ## INFO  [14:51:55.910] Erasing all files in "~/my.biodb.cache/chebi.ex-0c5076ac2a43d16dbce503a44b09f649".

# 12 Logging messages

biodb uses the lgr package for logging messages. The lgr instance used by biodb can be gotten by calling:

    biodb::getLogger()

    ## <Logger> [info] biodb
    ##
    ## inherited appenders:
    ##   console: <AppenderConsole> [all] -> console

See the lgr home page for demonstration on how to use it.

You can use the following biodb short cuts to send messages of different levels. To send an information message:

    biodb::logInfo("%d entries have been processed.", 12)

    ## INFO  [14:51:56.098] 12 entries have been processed.

To send a debug message:

    biodb::logDebug("The file %s has been written.", 'myfile.txt')

To send a trace message:

    biodb::logTrace("%d bytes written.", 1284902)

In addition biodb defines two methods to throw an error or a warning and log this error or warning at the same time. These are `biodb::error()` and `biodb::warn()`.

By default the lgr package displays information messages. If you want to silence all messages, just run `lgr::lgr$remove_appender(1)`. This is will remove the default appender and silence all messages from all packages using lgr, including biodb. However if you just want to silence biodb messages, run:

    biodb::getLogger()$set_threshold(300)

Information messages are now silenced:

    biodb::logInfo("hello")

For enabling again:

    biodb::getLogger()$set_threshold(400)

And messages are echoed again:

    biodb::logInfo("hello")

    ## INFO  [14:51:56.535] hello

# 13 Closing biodb instance

Do not forget to terminate your biodb instance once you are done with it:

    mybiodb$terminate()

    ## INFO  [14:51:56.582] Closing BiodbMain instance...
    ## INFO  [14:51:56.598] Connector "chebi.ex" deleted.

# 14 References