SciStack
pip install scistack # Installs tools for Python and MATLAB
Better Research Tools, Better Research Outcomes
SciStack is a suite of tools built by scientists for scientists of nearly any discipline to enhance data analysis pipelines. SciStack focuses on the common case of embarrassingly parallel workflows used to process nested datasets. It has three core goals:
- Minimalism: Minimize wasted time and effort, with a focus on reducing boilerplate code and offering advanced capabilities.
- Reusability: With a near-zero boilerplate format and support for cookie-cutter pipelines, SciStack pipelines are highly interoperable between projects. Thus, SciStack encourages scientific code reuse, an essential yet underutilized scientific work product.
- Openness: Minimize lock-in to the SciStack framework. SciStack code never touches scientific code, so you can easily change your data processing pipeline architecture at any time.
Minimal Example
Imagine that I am running a study involving a dataset containing Subjects each performing multiple Conditions, and each Condition contains multiple Trials (a common setup in my home field of biomechanics). Below is an example minimal data processing pipeline showcasing SciStack's features.
import scifor
import numpy as np
import pandas as pd
schema = ["subject", "condition", "trial"] # The structure of the dataset
scifor.set_schema(schema) # Tell SciStack about the schema
def example_loading_function(filepath: str) -> np.ndarray:
"""Data loading logic here."""
return np.ndarray(pd.read_csv(filepath))
def example_processing_function(val: np.ndarray, const: float) -> np.ndarray:
"""Do some processing on some inputs."""
return val + const
# Load every file matching "path/to/{subject}/{condition}/{trial}_data.ext"
# Returns a df with columns ["subject", "condition", "trial", "loaded_variable"]
loaded_df = scifor.for_each(example_loading_function,
filepath=scifor.PathInput("path/to/{subject}/{condition}/{trial}_data.ext", name="trial_data"),
outputs=["loaded_variable"]
)
# Process every subject, condition, & trial combination.
# Returns a df with columns ["subject", "condition", "trial", "procesed_variable"]
processed_df = scifor.for_each(example_processing_function,
val=scifor.ColumnSelection(loaded_df, "variable_to_process"), const=5,
subject=[], condition=[], trial=[], # Tell SciStack that `my_processing_function` should receive only one trial's data at a time.
outputs=["processed_variable"]
)
SciStack Design
For any project, it's essential to pick the right tool for the job. SciStack - as the name implies - contains a suite of tools in a "stack" of increasing complexity and weight. There are three main tools in this stack:
scifor: The lightest-weight level. Syntactical sugar around nestedforloops. Operates on in-memory variables only (no file IO) just like standard functions.scidb: Wrapsscifor, adds a SQL database for data save/load and an auditable data processing historyscistackGUI: Wrapsscidb, adds a GUI to manage complex pipelines.
scifor: syntactic sugar around for loops
Imagine you are conducting a study of human subjects walking. Each Subject comes in to the lab for multiple Sessions, and in each Session they perform multiple Trials of walking. During each Trial, you measure their speed every 0.1 seconds and store that data to one .csv file for each trial.
Example scifor Pipeline Data Loading Step
import scifor
import pandas as pd
# Tell `scifor` about the structure of this dataset
scifor.set_schema(["subject", "session", "trial"]) # ordered one-to-many
def load_data(file_path: str) -> pd.DataFrame:
"""Example logic to load the data"""
return pd.read_csv(file_path)
path_template = scifor.PathInput("path/to/data/{subject}/{session}/{trial}.csv", name="trial_data")
loaded_df = scifor.for_each(load_data,
file_path=path_template,
subject=[], session=[], trial=[],
output_names=["Loaded"]
)
In this example step, after defining a basic load_data() function, we:
- Defined a
scifor.PathInput, providing a template to load all of the files of interest. - Invoked the main command
scifor.for_each(), providingload_dataas the function,file_pathas the input variable, and specifying to runload_dataonce over every combination ofsubject,session, andtrialthat match thescifor.PathInputpath template. loaded_dfis apd.DataFramewith one row persubject,session, andtrialcombination. The data is stored into the"Loaded"field specified in the optionaloutput_namesparameter (default output name:"value").
Example scifor Pipeline Data Processing Step
import numpy as np
def process_data(speed: np.ndarray) -> np.ndarray:
"""Square every data point"""
return np.square(speed)
squared_df = scifor.for_each(process_data,
speed=loaded_df,
subject=[], session=[], trial=[]
)
scifor.for_each automatically parses loaded_df, repeatedly inputting only the speed values for one combination of subject, session, trial, allowing process_data() to remain very simple and ignore the structure of this project's dataset.
To see more, refer to the scifor docs.
scidb
scistack GUI
Metadata
Release files for scistack 0.1.35
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| scistack-0.1.35.tar.gz | 19.9 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| scistack-0.1.35-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 36.6 kB
Release files / scistack-0.1.35.tar.gz
| Download URL | scistack-0.1.35.tar.gz |
|---|---|
| Size | 19.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b813b3de8da4576ecc568171f83f1bc6a8bad6436277ef0b0242c3d305e355f1
|
|
BLAKE2b-256 checksum How to use checksums |
578447133344880283fdd6f765508917670443be62d7e67b99bfa979a259577f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 15, 2026.
Transparency logRelease files / scistack-0.1.35-py3-none-any.whl
| Download URL | scistack-0.1.35-py3-none-any.whl |
|---|---|
| Size | 16.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9d45bb0e1b2076300cae471a08102dcfb7cee1da83d00c4e6c5d7fa6305d5ab1
|
|
BLAKE2b-256 checksum How to use checksums |
b5730920304a097634c1c0bfd35b1f70270a520cbc99ca70fbf602dd18c05b0e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 15, 2026.
Transparency logSecurity for scistack 0.1.35
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for scistack-0.1.35.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 15, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.