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
2 changes: 1 addition & 1 deletion .github/ISSUE_TEMPLATE/bug_report.yml
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ body:
attributes:
label: Version
description: Shown in the app's About window. For a source build, give the commit.
placeholder: "0.5.1"
placeholder: "0.6.0"
validations:
required: true
- type: dropdown
Expand Down
2 changes: 1 addition & 1 deletion Cargo.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion Cargo.toml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
[package]
name = "intersection-lab"
default-run = "intersection-lab"
version = "0.5.1"
version = "0.6.0"
edition = "2024"
description = "Microscopic traffic-intersection simulator for comparing signal control, sensing and AI"
authors = ["Jim Schreckengast"]
Expand Down
2 changes: 1 addition & 1 deletion THIRD_PARTY_LICENSES.md
Original file line number Diff line number Diff line change
Expand Up @@ -4806,7 +4806,7 @@ SOFTWARE.

Used by:

* intersection-lab 0.5.1 (https://github.com/schreck61/intersection-lab)
* intersection-lab 0.6.0 (https://github.com/schreck61/intersection-lab)

```text
MIT License
Expand Down
20 changes: 10 additions & 10 deletions docs/architecture.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
This document describes how Intersection Lab is put together. It covers what each Rust
source file does, how the code is split into layers, and how those layers work together
during a simulation step, a corridor run, a cooperative crossing, a benchmark and a
training run. It describes the code on `main`: version 0.5.1 and the fixes made since.
training run. It describes the code on `main`: version 0.6.0.
Section 9.4 is an illustrated tour of the app's window, and Appendix A says how the
screenshots were made.

Expand Down Expand Up @@ -1626,8 +1626,8 @@ trained to lower delay on every layout (§8.6). Version 0.4.0 changed training i
ways: the reward counts every delayed person; checkpoints are chosen on a validation set
and must pass a pedestrian check; a separate test set reports the result. Deep RL's
shield also gained a maximum pedestrian wait, because the reward alone did not protect
pedestrians. Both controllers were retrained this way, and version 0.5.1 ships those
networks. Version 0.5.1 added the checks on weights files (§8.7).
pedestrians. Both controllers were retrained this way, and every version since has
shipped those networks. Version 0.5.1 added the checks on weights files (§8.7).

### 8.1 At a glance

Expand Down Expand Up @@ -2319,13 +2319,13 @@ arrivals, and hand-spawned vehicles and pedestrians are added to both.
### 9.4 A tour of the window

This section goes through every part of the window: what it shows, how to read it and
which code produces it. The screenshots come from the desktop app of version 0.5.1 in
its default 1600 × 1000 window (the smallest it allows is 1100 × 700), except the
close-up of the signal timing chart in part 5, which comes from `main` and shows the
yellow and all-red drawn since. They were taken with the scripted-screenshot settings
of Appendix A, two simulated minutes into the default scenario unless a caption says
otherwise. The browser version looks the same, without the *Save weights* buttons and
training commands of the learning panels.
which code produces it. The screenshots come from the desktop app in its default
1600 × 1000 window (the smallest it allows is 1100 × 700). Most show version 0.5.1;
those of parts that changed since, such as the signal timing chart, which now draws
yellow and all-red, were retaken with the code released as 0.6.0. They were taken with
the scripted-screenshot settings of Appendix A, two simulated minutes into the default
scenario unless a caption says otherwise. The browser version looks the same, without
the *Save weights* buttons and training commands of the learning panels.

#### The window at a glance

Expand Down
8 changes: 4 additions & 4 deletions packaging/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,12 +15,12 @@ Every release also carries `SHA256SUMS.txt` and a signed build-provenance attest
for each file. Users can verify a download with:

```bash
gh attestation verify IntersectionLab-0.5.1-macos-universal.dmg --repo schreck61/intersection-lab
gh attestation verify IntersectionLab-0.6.0-macos-universal.dmg --repo schreck61/intersection-lab
```

The signed attestation is also attached to the release as
`IntersectionLab-<version>.sigstore.json`, so a download can be checked without fetching
it from GitHub's attestation store: add `--bundle IntersectionLab-0.5.1.sigstore.json`.
it from GitHub's attestation store: add `--bundle IntersectionLab-0.6.0.sigstore.json`.

## Making a release

Expand All @@ -31,8 +31,8 @@ it from GitHub's attestation store: add `--bundle IntersectionLab-0.5.1.sigstore
commit on `main` afterward and push the tag:
```bash
git switch main && git pull
git tag v0.5.1
git push origin v0.5.1
git tag v0.6.0
git push origin v0.6.0
```
3. The workflow checks that the tag matches `Cargo.toml`, verifies licenses and
attributions, builds and signs every package, and creates a **draft** release with
Expand Down
Loading