This Docker image is designed to run the Python module eencijfer, providing an easy method to prepare raw 1cho data. The module is used for processing raw data files, and this image simplifies its deployment and execution.
We have provided three methods to work with this python module with as little pre-requisites as possible:
Warning
Important Note: Do not upload "1cho" data files containing sensitive data to GitHub Codespace! Only upload "Decodering" files, which filenames start with "Dec_"
eencijfer
Python module, making it straightforward to use without needing to install Python or the module on your system.Ensure Docker is installed on your system. Docker is necessary to run the eencijfer module encapsulated within the Docker image.
You can download Docker for your system through the following link Docker.
There is no configuration needed. If users want to take advantage of the config.INI possibilities of the Python eencijfer package, users can put a config.INI in the cwd to tailor the processing according to their specific use case. An example file is given (config.INI.example, rename this to config.INI and adapt contents to tailor your needs.). The default configuration assumes reading and writing from the current working directory where the batch or bat script is executed. This means you do not need to specify paths unless you wish to change the default behavior.
A result
directory will be automatically created and populated with the processed files once the eencijfer
module has completed its processing. This directory will be located in the current working directory where the batch or bat script is run, when using the default
config settings.
To run the Docker image, execute the provided batch or bat script. This script will handle the Docker run command, ensuring that the eencijfer
module is executed within the Docker container. The script will automatically map the current working directory to the Docker container, allowing you to easily input the raw data file for processing.
If you encounter any issues, ensure that Docker is running correctly on your system. Check the Docker logs for any error messages that may indicate what went wrong during the execution.
Warning
Important Note: Do not upload "1cho" data files containing sensitive data to the Codespace!
Instead, opt for the devpod solution described in the next section.
This repository supports GitHub Codespaces, which allows you to create a cloud-based development environment directly from the repository. To create a Codespace, follow these steps:
This will launch a Visual Studio Code instance hosted on GitHub, with the eencijfer
module pre-installed. You can access the terminal within the Codespace and install any additional dependencies or run commands as needed. To upload "Decodering" files, right-click within the Codespace and select "Upload..."
In order to convert the raw files, run the command eencijfer convert
in the terminal. This will convert to parquest files by default, in order to wite to csv you should run eencijfer convert --export-format csv
.
Please note that you should not upload "1cho" data files containing sensitive data. Instead, use the devpod solution described below.
eencijfer
moduleUpload...
In order to convert the data files, run eencijfer convert
. You can opt to use flags, such as -C to convert all columns to character, and --export-format
to set the extension you wish. You can choose either csv or parquet for the time being.
We have included a work-in-progress
jupyter notebook to visualize the data. At the moment it assumes you have all 1cHo files and have converted them to parquet.
An alternative to using GitHub Codespaces is to use the devpod solution. Follow these steps:
The devpod solution provides a secure and isolated environment for working with sensitive data files.
eencijfer
python module.eencijfer
command in the terminal.Upload...
Right click on the file browser in order to upload files to the workspace.
In order to convert the data files, run eencijfer convert
. You can opt to use flags, such as -C to convert all columns to character, and --export-format
to set the extension you wish. You can choose either csv or parquet for the time being.
We have included a work-in-progress
jupyter notebook to visualize the data. At the moment it assumes you have all 1cHo files and have converted them to parquet.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4