svc-processing 0.1.3__tar.gz → 0.1.4__tar.gz

{svc_processing-0.1.3 → svc_processing-0.1.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: svc-processing
-Version: 0.1.3
+Version: 0.1.4
 Summary: Pure-Python SVC HR-1024i hyperspectral .sig processing pipeline
 Author: Gold Lab (GrapeSPEC project), Cornell University
 Author-email: Cole Regnier <nr466@cornell.edu>
@@ -77,14 +77,28 @@ svc-pipeline --init-config   # command name — different from the package name
 svc-pipeline
 ```
 
-**Working from a clone of this repo** (config/config.json already exists):
+**Working from a clone of this repo** (config/config.json already exists) — run the
+setup script once, then activate the environment it created:
+
+```bash
+./setup.sh            # creates .venv, installs everything, stages the demo data
+# ./setup.sh --dev    # add the test & lint tools for development
+
+source .venv/bin/activate          # macOS / Linux
+# .venv\Scripts\activate           # Windows PowerShell
+
+# Edit config/config.json — replace "<PATH_TO_SIG_INPUT_ROOT>" with your data path.
+svc-pipeline config.json
+```
+
+The script always installs into *this* repo's `.venv` no matter which folder you run
+it from, so it avoids the "Directory '.' is not installable" and "No module named …"
+errors that come from being in the wrong directory. Prefer to do it by hand?
 
 ```bash
 python3.11 -m venv .venv
 source .venv/bin/activate
 python -m pip install -e ".[dev,demo]"
-
-# Edit config/config.json — replace "<PATH_TO_SIG_INPUT_ROOT>" with your data path.
 svc-pipeline config.json
 ```
 

{svc_processing-0.1.3 → svc_processing-0.1.4}/README.md

@@ -44,14 +44,28 @@ svc-pipeline --init-config   # command name — different from the package name
 svc-pipeline
 ```
 
-**Working from a clone of this repo** (config/config.json already exists):
+**Working from a clone of this repo** (config/config.json already exists) — run the
+setup script once, then activate the environment it created:
+
+```bash
+./setup.sh            # creates .venv, installs everything, stages the demo data
+# ./setup.sh --dev    # add the test & lint tools for development
+
+source .venv/bin/activate          # macOS / Linux
+# .venv\Scripts\activate           # Windows PowerShell
+
+# Edit config/config.json — replace "<PATH_TO_SIG_INPUT_ROOT>" with your data path.
+svc-pipeline config.json
+```
+
+The script always installs into *this* repo's `.venv` no matter which folder you run
+it from, so it avoids the "Directory '.' is not installable" and "No module named …"
+errors that come from being in the wrong directory. Prefer to do it by hand?
 
 ```bash
 python3.11 -m venv .venv
 source .venv/bin/activate
 python -m pip install -e ".[dev,demo]"
-
-# Edit config/config.json — replace "<PATH_TO_SIG_INPUT_ROOT>" with your data path.
 svc-pipeline config.json
 ```
 

{svc_processing-0.1.3 → svc_processing-0.1.4}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "svc-processing"
-version = "0.1.3"
+version = "0.1.4"
 description = "Pure-Python SVC HR-1024i hyperspectral .sig processing pipeline"
 readme = "README.md"
 requires-python = ">=3.11"

{svc_processing-0.1.3 → svc_processing-0.1.4}/svc_processing.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: svc-processing
-Version: 0.1.3
+Version: 0.1.4
 Summary: Pure-Python SVC HR-1024i hyperspectral .sig processing pipeline
 Author: Gold Lab (GrapeSPEC project), Cornell University
 Author-email: Cole Regnier <nr466@cornell.edu>
@@ -77,14 +77,28 @@ svc-pipeline --init-config   # command name — different from the package name
 svc-pipeline
 ```
 
-**Working from a clone of this repo** (config/config.json already exists):
+**Working from a clone of this repo** (config/config.json already exists) — run the
+setup script once, then activate the environment it created:
+
+```bash
+./setup.sh            # creates .venv, installs everything, stages the demo data
+# ./setup.sh --dev    # add the test & lint tools for development
+
+source .venv/bin/activate          # macOS / Linux
+# .venv\Scripts\activate           # Windows PowerShell
+
+# Edit config/config.json — replace "<PATH_TO_SIG_INPUT_ROOT>" with your data path.
+svc-pipeline config.json
+```
+
+The script always installs into *this* repo's `.venv` no matter which folder you run
+it from, so it avoids the "Directory '.' is not installable" and "No module named …"
+errors that come from being in the wrong directory. Prefer to do it by hand?
 
 ```bash
 python3.11 -m venv .venv
 source .venv/bin/activate
 python -m pip install -e ".[dev,demo]"
-
-# Edit config/config.json — replace "<PATH_TO_SIG_INPUT_ROOT>" with your data path.
 svc-pipeline config.json
 ```