JupyterLab and Python for Data Acquisition in GI.cloud

 What Is JupyterLab?

JupyterLab is a browser-based environment for working with notebooks, Python scripts, data, terminals and visualisations. Combined with Gantner Instruments GI.cloud, it gives technical teams a reproducible workspace for accessing distributed measurement data, exploring signals, creating analytics and preparing reports, without moving every workflow to a local engineering PC. 

Why Use JupyterLab for Data Acquisition and Analysis? 

Data acquisition projects generate more than raw samples. Teams must validate sensor behaviour, align timestamps, filter noise, calculate engineering quantities, detect events, compare assets and communicate results. JupyterLab supports this full analytical loop while keeping code, assumptions and outputs together.

• Explore measurement data interactively before committing to a production algorithm.

• Use NumPy, pandas, SciPy and domain-specific packages for signal processing and statistics.

• Create plots, dashboards and engineering reports from the same source data.

• Share repeatable methods among engineers, researchers, analysts, educators and students.

• Move proven logic from a notebook into a tested Python module, scheduled job or edge application.

 How JupyterLab and Python Integrate with GI.cloud

GI.cloud is Gantner Instruments’ cloud storage and monitoring platform. It connects edge measurement systems with a scalable backend, time-series storage, visualisation, device management and open interfaces. 

In a typical architecture, the Q.series measurement modules and Q.station controller acquire, synchronise, and pre-process physical measurement signals at the edge. GI.cloud receives, stores, and visualises selected data streams from one or multiple measurement locations. Python notebooks or scripts can then access the data through authorised interfaces and project-specific services to perform additional processing and analysis, enrich the measurement data, and return calculated results to the wider workflow. 

 Cloud Python Workflow for DAQ Data Analysis

1. Configure the Q.series DAQ system. Use GI.bench to configure sensors, channel names, units, sample rates, calculations, buffering and data logging on the Q.station controller.

2. Connect the Q.series system to GI.cloud. Pair the controller and define the required data streams. For intermittent connectivity, a local logging-and-forwarding strategy (skimming mode) can preserve data until the connection returns.

3. Open the project’s Python workspace. Start the JupyterLab environment provided for the deployment. Use a separate environment per project where practical and record package versions.

4. Authenticate securely. Use the approved GI.cloud API or service interface. Store credentials in a secret store or environment variables, not directly in the notebook.

5. Request a bounded dataset. Begin with named channels, a specific asset and an explicit time window. This improves performance and makes the query reproducible.

6. Validate before analysing. Check timestamps, time zone, units, channel metadata, missing values, sample spacing, clipping and sensor status.

7. Analyse and visualise. Apply filtering, resampling, feature extraction, statistics or machine learning appropriate to the measurement physics.

8. Operationalise the result. Move stable functions into a Python module, add tests and logging, schedule the job or deploy it through the approved GI.cloud/edge mechanism.

 Jupyter Notebook Best Practices for Reliable DAQ Analysis

• Keep raw data immutable and record the query, device, channels, units, time zone and time range.

• Separate acquisition, validation, analysis and presentation into clear functions or modules.

• Use UTC internally and convert to local time only for presentation.

• Derive filter settings and rolling windows from the real sampling rate, not from arbitrary row counts.

• Treat missing, duplicated, delayed and out-of-order samples explicitly.

• Pin dependencies with a requirements file or lock file and record the Python version.

• Never commit API tokens, passwords or private endpoints to notebooks or source control.

• Restart the kernel and run all cells before sharing to detect hidden execution-order dependencies.

• Add automated tests for engineering calculations, thresholds and unit conversions.

• For scale, query only required channels and intervals; push suitable pre-processing and data reduction to the edge.

 Jupyter Notebook vs. Python Script for DAQ Applications 

Frequently Asked Questions About JupyterLab, Python and DAQ

Is JupyterLab the same as Jupyter Notebook?

No. Both work with computational notebooks, but JupyterLab provides a broader, integrated workspace with notebooks, editors, terminals, consoles and multiple document types.

Can JupyterLab run Python in the cloud?

Yes. JupyterLab can run on a remote server or managed platform and is accessed through a browser. Code executes in the remote Python environment, close to authorised data and compute resources.

How does Python access Gantner Instruments measurement data?

The supported route depends on the task and deployment. GI.cloud exposes project-specific APIs and services for cloud data access. For direct Q.station streaming, Gantner also provides the GInsData library and GInsAPy Python wrapper.

Can Python analyse live and historical DAQ data?

Yes. Gantner’s Python interfaces support real-time streams and recorded data. GI.cloud is designed for distributed streaming, time-series storage and access to data at different sampling intervals.

Does cloud analysis replace edge computing?

No. Edge processing remains important for deterministic acquisition, buffering, local calculations, alarms, data reduction and control. Cloud Python complements the edge with scalable analytics, comparison and collaboration.

Which Python libraries are useful for DAQ analysis?

Common choices include NumPy for arrays, pandas for time series, SciPy for signal processing, Matplotlib or Plotly for visualisation, and scikit-learn for machine learning. Selection should follow the signal physics and validation requirements.

Can JupyterLab be used for teaching data acquisition?

Yes. A notebook can combine theory, code, plots and real measurement data in one shareable lesson. Access controls and curated datasets should be used when students work with operational systems.

Is JupyterLab suitable for safety-critical control?

Not by itself. Interactive notebooks are not deterministic control systems. Validate and deploy safety-related logic on the appropriate real-time controller or approved production runtime.

JupyterLab, Python and GI.cloud Sources and Further Reading

• JupyterLab Documentation — Project Jupyter
  Official JupyterLab documentation covering installation, notebooks, kernels, terminals, extensions and the browser-based interactive development environment used for Python data analysis.
  JupyterLab Documentation

• GI.cloud — Distributed Streaming and Data Platform
  Gantner Instruments platform for distributed measurement-data streaming, storage, visualisation and analysis, connecting remote DAQ systems with cloud-based engineering workflows
  GI.cloud Distributed Streaming Platform
• Python Data Acquisition from Q.station Controllers Using GInsData API
  Practical Gantner Instruments guide explaining how Python applications can access measurement data directly from Q.station controllers using the GInsData API.
  Python Data Acquisition from Q.station
• Python Integration — Automation and Data Analysis
  Gantner Instruments article exploring how Python integration extends measurement systems with automated workflows, custom data processing and advanced engineering analysis.
  Python Integration: Automation and Analysis
• Research with Jupyter Notebooks, GI.bench and GI.cloud
  Application example demonstrating how researchers can combine GI.bench, GI.cloud and Python Jupyter notebooks to manage measurement data and develop flexible analysis workflows.
  Research with Jupyter Notebooks and GI.cloud
• Pair a Q.station Controller with GI.cloud
  Step-by-step Gantner Instruments Knowledge Base guide for connecting and pairing a compatible measurement controller with GI.cloud for remote data access and monitoring.
  Pair a Controller with GI.cloud
• Configure Skimming Mode Data Logging
  Technical guide to configuring skimming mode for efficient measurement-data logging, providing useful context for managing data rates and historical measurement data in DAQ applications.
  Configure Skimming Mode Logging