Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion .github/workflows/ci.yml
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,8 @@ jobs:
# the release and workflow checks (action pins, release permissions,
# zenodo metadata): stdlib only, seconds; this job runs on every pull
# request, so a workflow or Dependabot change is checked too
- run: pip install pytest
# the same pytest as requirements-dev.txt (8.185 c; a test checks it)
- run: pip install pytest==9.1.1
- run: python -m pytest tests/ci -q -p no:cacheprovider

backend:
Expand Down
6 changes: 3 additions & 3 deletions .zenodo.json
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
{
"title": "Catalog of Second Chances (CSC) - Digital Database and Corresponding Interfaces for ReUse of Architectural Components (v0.6.4.3)",
"version": "0.6.4.3",
"title": "Catalog of Second Chances (CSC) - Digital Database and Corresponding Interfaces for ReUse of Architectural Components (v0.6.4.4)",
"version": "0.6.4.4",
"upload_type": "software",
"description": "<p>The <em>Catalog of Second Chances (CSC)</em> is a prototypical digital component database. It catalogs digital representations of uniquely identifiable architectural components for reuse. Furthermore, it provides corresponding interfaces and tools to leverage them via a backend REST-API, a web-frontend as well as a interface for direct interaction within Rhino Grasshopper.</p><h2>Changes in v0.6.4.3 (2026-10-29)</h2><p>Photo controls that follow the permission rule. The Grasshopper fixes announced for 0.6.4.3 move to 0.6.4.4.</p><h3>Fixed</h3><ul><li><strong>Photos of a version:</strong> the \"Take photo\", \"Add from gallery\" and delete controls on the component page now follow the same rule as the server. Before publish, the author of a draft and the moderators of its dataset add and remove photos, and only moderators on a pending version. After publish, contributors and moderators of the dataset add photos and only moderators remove them. Until now only site admins saw these controls, and only before publish (#45).</li></ul><h3>Server notes</h3><ul><li>No server step needed.</li></ul><p>Full history: <a href=\"https://github.com/digitaldesignunit/csc/blob/v0.6.4.3/CHANGELOG.md\">CHANGELOG.md</a></p>",
"description": "<p>The <em>Catalog of Second Chances (CSC)</em> is a prototypical digital component database. It catalogs digital representations of uniquely identifiable architectural components for reuse. Furthermore, it provides corresponding interfaces and tools to leverage them via a backend REST-API, a web-frontend as well as a interface for direct interaction within Rhino Grasshopper.</p><h2>Changes in v0.6.4.4 (2026-11-03)</h2><p>Grasshopper hardening, and the beta notice takes its version from the release. Run <code>CSC_Update</code> in Grasshopper after the server is deployed.</p><h3>Fixed</h3><ul><li><strong>Grasshopper, missing inputs:</strong> a component with a missing or empty input shows a warning and waits for data, instead of an error. Real failures (bad counts, unreadable data, server errors) stay errors (#32, #40).</li><li><strong>Grasshopper, outputs without a result:</strong> an output with nothing to give is an empty Grasshopper tree, not <code>&lt;empty&gt;</code> or <code>&lt;null&gt;</code>, on every error path and when a component stops early. In a component that runs once per item, one missing, empty or failed item gives a null in its slot, so the outputs stay one to one with the input list; an input with no data at all gives empty outputs (#33, #40).</li><li>**Grasshopper, <code>ReadFromD2P</code>:** the <code>Component</code> output carries the D2P component itself, and a remark names its type. When the D2P component of an element cannot be resolved, a warning names the element; a plain tag of <code>BakeComponents</code> stays null without a warning (#36).</li><li><strong>Beta notice:</strong> the beta banner and the beta login notice take the version from the release. The text in the frontend settings writes <code>{version}</code> where the number goes (#52).</li></ul><h3>Changed</h3><ul><li><strong>Grasshopper, wording:</strong> the descriptions and messages of the components call a single building component an \"element\" instead of a \"piece\", as the web app does since 0.6.4.2.</li><li><strong>Grasshopper, frames:</strong> the description of <code>ApplyFrame</code> says that its <code>Frame</code> output is the frame used, in the stored coordinates, and points to <code>DisassembleComponent</code> for the frame where the moved element sits. The <code>Frame</code> and <code>BoundingBox</code> descriptions of <code>DisassembleComponent</code> now say that they give the element where it sits.</li><li>**Grasshopper, <code>ReinforcementLayout</code>:** the steel grade (<code>Spec</code>) is optional; bars without it are stored without a grade.</li><li>**Grasshopper, <code>AddEvidence</code>:** an invalid identity id or evidence text is an error, no longer a warning.</li><li>**Grasshopper, <code>CSC_Update</code>:** after it replaces the source of a component, the remark and the end of the run ask you to save the definition, close it and open it again before clicking Apply: until then Rhino 8 opens the script editor of that component read-only and the component reports \"Object reference not set to an instance of an object\".</li><li><strong>Grasshopper library:</strong> <code>csc_gh</code> 261102; <code>CSC_Update</code> brings it.</li><li><strong>Component map:</strong> the layout now starts from a PCA initialisation instead of the spectral one, which failed on groups of near-identical elements and fell back to a random start. All positions on the map shift once with the first nightly run after the release.</li><li><strong>Development:</strong> the development requirements are pinned exactly (pytest 9.1.1, pytest-xdist 3.8.0, coverage 7.16.2, flake8 7.4.1, invoke 3.0.3, requests 2.34.2, pyld 3.3.0, rdflib 7.6.0), and CI installs the same pytest. A cancelled sign-in in the Grasshopper tests no longer leaves an exception in a thread.</li></ul><h3>Server notes</h3><ul><li>In the server's frontend <code>.env</code>, take the version number out of <code>BETA_BANNER_TEXT</code> and <code>BETA_LOGIN_MESSAGE</code>, or write <code>{version}</code> in its place (for example <code>BETA_BANNER_TEXT=&quot;VERSION {version}&quot;</code>). Restart the frontend.</li></ul><p>Full history: <a href=\"https://github.com/digitaldesignunit/csc/blob/v0.6.4.4/CHANGELOG.md\">CHANGELOG.md</a></p>",
"creators": [
{
"name": "Eschenbach, Max Benjamin",
Expand Down
51 changes: 51 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,57 @@ All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [0.6.4.4] - 2026-11-03

Grasshopper hardening, and the beta notice takes its version from the release. Run `CSC_Update` in
Grasshopper after the server is deployed.

### Fixed

- **Grasshopper, missing inputs:** a component with a missing or empty input shows a warning and waits
for data, instead of an error. Real failures (bad counts, unreadable data, server errors) stay errors
(#32, #40).
- **Grasshopper, outputs without a result:** an output with nothing to give is an empty Grasshopper
tree, not `<empty>` or `<null>`, on every error path and when a component stops early. In a component
that runs once per item, one missing, empty or failed item gives a null in its slot, so the outputs
stay one to one with the input list; an input with no data at all gives empty outputs (#33, #40).
- **Grasshopper, `ReadFromD2P`:** the `Component` output carries the D2P component itself, and a remark
names its type. When the D2P component of an element cannot be resolved, a warning names the element;
a plain tag of `BakeComponents` stays null without a warning (#36).
- **Beta notice:** the beta banner and the beta login notice take the version from the release. The
text in the frontend settings writes `{version}` where the number goes (#52).

### Changed

- **Grasshopper, wording:** the descriptions and messages of the components call a single building
component an "element" instead of a "piece", as the web app does since 0.6.4.2.
- **Grasshopper, frames:** the description of `ApplyFrame` says that its `Frame` output is the frame
used, in the stored coordinates, and points to `DisassembleComponent` for the frame where the moved
element sits. The `Frame` and `BoundingBox` descriptions of `DisassembleComponent` now say that they
give the element where it sits.
- **Grasshopper, `ReinforcementLayout`:** the steel grade (`Spec`) is optional; bars without it are
stored without a grade.
- **Grasshopper, `AddEvidence`:** an invalid identity id or evidence text is an error, no longer a
warning.
- **Grasshopper, `CSC_Update`:** after it replaces the source of a component, the remark and the
end of the run ask you to save the definition, close it and open it again before clicking Apply:
until then Rhino 8 opens the script editor of that component read-only and the component
reports "Object reference not set to an instance of an object".
- **Grasshopper library:** `csc_gh` 261102; `CSC_Update` brings it.
- **Component map:** the layout now starts from a PCA initialisation instead of the spectral one,
which failed on groups of near-identical elements and fell back to a random start. All positions
on the map shift once with the first nightly run after the release.
- **Development:** the development requirements are pinned exactly (pytest 9.1.1, pytest-xdist
3.8.0, coverage 7.16.2, flake8 7.4.1, invoke 3.0.3, requests 2.34.2, pyld 3.3.0, rdflib 7.6.0), and
CI installs the same pytest. A cancelled sign-in in the Grasshopper tests no longer leaves an
exception in a thread.

### Server notes

- In the server's frontend `.env`, take the version number out of `BETA_BANNER_TEXT` and
`BETA_LOGIN_MESSAGE`, or write `{version}` in its place (for example
`BETA_BANNER_TEXT="VERSION {version}"`). Restart the frontend.

## [0.6.4.3] - 2026-10-29

Photo controls that follow the permission rule. The Grasshopper fixes announced for 0.6.4.3 move to
Expand Down
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,8 +29,8 @@ framework

## Current Versions

- **CSC**: 0.6.4.3 --- backend, web frontend and Grasshopper interface are released together
under one version (tag `v0.6.4.3`); the single source is the `VERSION` file.
- **CSC**: 0.6.4.4 --- backend, web frontend and Grasshopper interface are released together
under one version (tag `v0.6.4.4`); the single source is the `VERSION` file.

See `CHANGELOG.md` for release notes.

Expand Down
2 changes: 1 addition & 1 deletion VERSION
Original file line number Diff line number Diff line change
@@ -1 +1 @@
0.6.4.3
0.6.4.4
Loading
Loading