Advanced Search
Search Results
35 total results found
Notices & Terms of Use
REVISION DATE: 2025-12-20
Notices & Terms of Use
REVISION DATE: 12-20-2025
Notices & Terms of Use
REVISION DATE: 12-20-2025
LabLynx Lab Automation Suite: AI-assisted Used Oil Analysis Use Case
Used Oil Analysis DemoSummaryUsed Oil Analysis Laboratories perform tests on machine fluids to predict machine failure and preventative maintenance events. One of the key disciplines for used oil analysis is called Tribology. In this article we propose a techn...
The LabLynx ELN Suite: LIMS Without the Price Tag
Transforming Lab Workflows with ELNs: A Deep Dive into the LabLynx ELN SuiteIn today’s fast-evolving scientific landscape, labs of all sizes are turning to Electronic Lab Notebooks (ELNs) to revolutionize how research is documented, shared, and managed. Whethe...
Introduction
This suite of training modules are meant to be a guide for SciForge developers to get familiar with the infrastructure and tools used for plugin development as they begin their development journey. Traditional API documentation lists out the available endpoint...
SciForge API: Prerequisites
IntroductionThis is the first in a series of training modules, intended to familiarize developers with the setup and usage of a development environment for the SciForge API. This API is most often used with the ELab LIMS, and so training focuses primarily on t...
SciForge API: Getting Started
Development takes place in a dockerized environment that is nearly identical to the production system. While it is possible to develop without docker, training covers the recommended approach. LabLynx developers generally must develop within the dockerized env...
SciForge API: Development Configuration
Video: Environment Configuration Example The configuration that is managed by the .env (environment) file, and a DNS address for the SciForge development environment, are the final aspects of setup that need to be completed in order for the development environ...
SciForge: Starting and Stopping Development
In training modules to this point, we have covered the setup of the development environment to include:Cloned all necessary codeSetup DNS addresses for Traefik and for the Sciforge development environmentSetup Traefik to reverse proxy the development APISetup ...
Sciforge API: Managing Application Keys
An Application Key (or AppKey) is used to authenticate API requests. This document shows how you can generate AppKeys in Elab to access the Sciforge API. Video: App Key Management RequirementsFirst the ELab Appkey functionality will need to be present in the...
Sciforge API: Access with Application Keys
The prior module covered the generation of an Application Key (or AppKey). Now, it is time to learn to access the API endpoints.The your AppKey and the associated ELab username, a JWT token is first generated, that can then be used to access the rest of the AP...
SciForge API: Code Architecture
SciForge code is organized to enable a SOLID and DRY approach to programming the API. The flexibility to build your own plugins goes hand in hand with the flexibility of Elab, and the expectation that every instance is used differently. Existing code can be ex...
Sciforge API: Development Pipelines
The SciForge API has two code bases that it can pull from for any given client. This module provides an overview of the software pipeline and automated aspects of code implementation.The first is our commercial-off-the-shelf (COTS) repository “elab_api”. This...
SciForge API: Bring it all together
The point of the training program is to facilitate the setup of the development environment, and to then develop changes. There is an assumption that developers are familiar with the publicly available technologies that the product is based on, such as GraphQL...