---

ASSAS Data Hub

The ASSAS Data Hub is a web application to store and visualize ASTEC simulation data on the Large Scale Data Facility at KIT. Its database contains the ASTEC archive in binary raw format and offers a conversion in other data formats. At the moment only a conversion in hdf5 data format is supported.

• Prequisites
• Installation
• Upload ASTEC Data
• Database View
• RESTful API

Prerequisites

The ASSAS Data Hub is a flask web application, which requires the following additional software packages:

• MongoDB Version 7.0.6
• Python3.11 virtual environment
• ASTEC V3.1.1 installation
• Cron 1.5.2

Installation

Start application

Entrypoint of the application is wsgi.py (Python Web Server Gateway Interface) and can be started with:

$ python wsgi.py

The application starts as a custom flask app. Test version available under http://assas.scc.kit.edu:5000/assas_app/home on a virtual machine inside the KIT infrastructure.

NoSQL Database

Runs on CONNECTIONSTRING = r'mongodb://localhost:27017/'.

Restart NoSQL Database:

$ service mongod restart

Mount lsdf share

The following command mounts the LSDF on the server system for the user USER:

$ sudo mount -t cifs -o vers=2.0,username='USER',uid=$(id -u),gid=$(id -g) //os.lsdf.kit.edu/kit/scc/projects/ASSAS /mnt/ASSAS

Reverse-proxy configuration

Upload ASTEC data

The upload of ASTEC data is supported through an upload application under tools/assas_data_uploader.py. The use of the upload application requires the following:

1. Create Partner- and Guest-KIT Account: https://www.scc.kit.edu/en/services/gup.php
2. Create Access to the LSDF with this Account: https://www.lsdf.kit.edu/
3. Installation of Python3.10+ and rysnc: https://wiki.ubuntuusers.de/rsync/
4. Define the ASTEC archive directory tree

The commandline interface of the upload application requires the following parameters:

• --user (-u): KIT internal batch which has access to the LSDF
• --source (-s): Path to the directory tree which will be uploaded (ASTEC Project directory)
• --name (-n): Corresponding name of the archive visible in the database
• --description (-d): Corresponding description of the archive visible in the database
• --archives (-a): Sub path to the actual ASTEC archive inside the directory tree, or a list of sub paths

The commandline interface of the upload application has the following optional parameter:

• --uuid (-i): Upload identifier of an upload process which was already started

Note: This parameter can be used to resume an interrupted or failed upload. One must determine the upload uuid from the standard output of the upload application.

Examples

The upload application can be executed via commandline as follows:

$ python tools/assas_data_uploader.py -u my_user -s my_source_path -n my_name -d my_description -a my_archive_path

If there is a project tree with several ASTEC runs, one can define a list of archive paths:

$ python tools/assas_data_uploader.py -u my_user -s my_source_path -n my_name -d my_description -a my_archive_path_1, my_archive_path_2, ....

Database view

The database view displays a list with all available datasets and provides the following parameters:

• Index: Unique index of dataset
• Size: Size of ASTEC binary archive
• Size hdf5: Size of the hdf5 file after conversion
• Date: Date of the upload time
• User: User which has uploaded the dataset
• Status: Status of the uploaded dataset
• Name: Given name of the uploaded dataset

By click on the column cell File the user can download By click on the parameter Name the user comes to a detailed view with following meta information about the dataset:

General

• Name (same as on the database view)
• Description

Data

The following meta information is extarcted during the upload and conversion process:

• Variables: List of extracted variables
• Channels: Number of ectracted channels
• Meshes: Number of extracted meshes
• Samples: Number of extracted samples

RESTful API

The ASSAS Data Hub provides a RESTful API to query training data in an automated way.

Read data

Writing data

---