TODO WIKI - ISET/isetcam GitHub Wiki

ISETCam wiki update plan

Status: paused (2026-08-24). The core navigation and documentation infrastructure are in place. The next active section is Related Projects; wording, script, and link refinements remain an editorial follow-up.

Implementation tracking (2026-08-23 / 2026-08-24):

  • 1. Inventory and link baseline — recorded in Wiki Inventory and Link Baseline.
  • 2. Home and History — Home.md rewritten with the new isetcam-overview-1.png diagram, device and spectral scene data overview, and dual foundational/validation citations; History.md added.
  • 3. Getting Started — Getting-Started.md consolidated with all Installation.md content into a single entry point; Installation.md retained as a moved stub; _Sidebar.md updated.
  • 7. Spectral Scene Data — Spectral-Scene-Data.md created with comprehensive documentation of SDR hyperspectral, multispectral, HDR, and 3D rendered datasets, ieWebGet, sceneSDR, and physical units; older legacy data pages merged/redirected.
  • 8. Programming — Programming.md rewritten as an overview page; Programming-Conventions.md added covering the noun-verb architecture, get/set philosophy, physical units, and style rules; Programming-Examples.md added with code walkthroughs from t_sceneIntroduction, t_introduction2ISET, and t_SystemSimulate plus iePublish documentation; testing referenced with full details deferred to developer section.
  • 8. Testing — Testing.md added with the current ieUnitTest, ieTutorialTest, ieExampleTest, focused component runners, % SkipFile, and ieTestReport workflow; Programming pages and sidebar link to it.
  • 4. Tutorials and Examples — landing pages and the five topic tutorial pages are in place and linked from _Sidebar.md.
  • 5. Core Pipeline — Core-Pipeline.md and the scene, optical-image, sensor, image-processing, and display pages form the main pipeline route.
  • 6. Supporting Concepts — Color Science, Metrics, and Camera Systems pages are grouped under their sidebar landing page.
  • 9. Related Projects — review and revise Related-projects.md and its ISETBio/ ISET3D links next.
  • Deferred editorial pass — refine wording, scripts, and links throughout the completed pages. The originally proposed Resources.md and Legacy-Reference.md landing pages have not been created; decide later whether the existing topic pages make either additional landing page worthwhile. The 29 non-instruction pages with no incoming current-wiki links have been moved to Unlinked-Pages/ for review; decide later whether each should return as a linked child, a moved-page stub, or a legacy-page entry. Sensor-models-built-in.md is already linked from Sensor.md, Sensor-color-filter-array.md, and Sensor-noise-model.md.

Scope: reorganize the ISETCam wiki around a concise, welcoming Home page; a single new-user route; the current ISETCam computational pipeline; curated tutorials and examples; and clearly separated historical or retired material. The result should use the same basic organization as the ISETBio and ISET3D wikis and should become the shared foundation those wikis can reference for general scene, optics, sensor, image-processing, display, color, and metric computations. This is a software dependency as well as a documentation relationship: neither ISETBio nor ISET3D can run unless ISETCam is installed and on the MATLAB path.

This plan was prepared by reviewing the three wiki repositories, the current ../isetcam source tree, and the online Foundations of Image Systems Engineering (FISE) resource on 2026-08-23.

Goals

  1. Give a new visitor an inspiring explanation of why image systems engineering matters and what ISETCam makes possible.

  2. Provide a short, reliable route from installation to a first complete camera simulation.

  3. Organize the main documentation around the physical and computational pipeline:

    scene radiance -> optical image -> sensor -> image processing -> display

  4. Make ISETCam the canonical documentation source for shared computations; ISETBio and ISET3D should link here instead of duplicating generic ISETCam material. Their Getting Started pages should identify ISETCam as a required dependency, not merely a related toolbox.

  5. Connect principles to runnable software by linking FISE concepts, curated tutorials, iePublish-generated HTML output, and adaptable examples.

  6. Preserve the project's scientific and institutional history without making dated release notes the first thing a new user sees.

  7. Clearly label supported, advanced, experimental, historical, and retired workflows.

Working principles

  • Treat ../isetcam as the source of truth for APIs, tutorials, examples, data loading, repository layout, and tests. Its default branch is main.
  • Keep the Home page and sidebar concise, current, and task-oriented.
  • Keep durable user guidance in the wiki. Link to repository skills or source documentation for developer procedures that change with the implementation.
  • Verify every source link and cited filename before publishing. Use blob/main for files and tree/main for directories.
  • Treat iePublish-generated, self-contained tutorial HTML as a first-class documentation layer. Each recommended tutorial should lead to rendered prose, figures, and output, with its .m source link alongside it.
  • Keep the published HTML synchronized with its source tutorial. Regenerate and visually inspect it whenever a documented tutorial changes; do not link stale or unverified output.
  • Preserve useful edit history with git mv and short “moved to” stubs when a widely linked page changes name. GitHub Wikis do not provide native redirects.
  • Do not silently delete historical scientific explanations. Move them to History.md or index them from a clearly marked Legacy-Reference.md page.
  • Keep the wiki flat, as GitHub Wikis are, while using _Sidebar.md to express hierarchy and a learning path.
  • Use the repository's existing distinction between tutorials (short, instructional t_*.m files) and examples (longer, adaptable s_*.m analyses). Do not merge them into one undifferentiated list.

Evidence from the current repositories

  • The ISETCam wiki has 57 Markdown pages after excluding the three agent instruction files. It contains valuable scientific explanations, but also many tiny stubs, overlapping pages, and old operational instructions.
  • The ISETCam source has 44 t_*.m tutorial scripts, 41 committed tutorial HTML files, and 135 s_*.m examples. These are a much better basis for current tutorial indexes than the wiki's older handwritten lists.
  • Current repository-wide test entry points are ieUnitTest, ieTutorialTest, and ieExampleTest, with ieTestReport for reporting. ISETValidate remains relevant for broader validation, but the retired external UnitTestToolbox/ExampleTestToolbox workflow is not the current first-run path.
  • The current source pipeline is scene, optical image, sensor, image processing, and display, with supporting color, camera, human, metrics, utility, and GUI areas.
  • ISETBio requires ISETCam on the MATLAB path and has explicitly identified general scene and optical-image mechanics as ISETCam-owned documentation.
  • ISET3D also requires ISETCam on the MATLAB path. It returns ISETCam scene or optical-image representations and now has a concise Getting Started page, workflow page, tutorial landing page, and topic indexes that ISETCam can link to rather than duplicating 3D rendering setup.
  • FISE follows a compatible conceptual arc: scenes and light measurement, optics, sensors and complete systems, human vision, displays, image processing, and image-quality metrics. It also uses code snippets and links to runnable scripts. This makes it a natural conceptual companion to the task-oriented wiki, not a replacement for software documentation.

Current wiki assessment

Highest-priority issues

  • Home.md mixes a good statement of purpose with commercial/open-source history, user statistics, old branch policy, and dated download notes. The current branch note still describes master as stable even though the source repository's default branch is main.
  • Installation.md points to the old imageval/isetcam repository and lists retired validation dependencies. It also describes ISET3d-tiny as a future replacement even though the current ISET3D rewrite has replaced it.
  • Programming.md mixes useful object conventions with retired runners (ieRunTutorialsAll, ieRunScriptsAll), old external example-test tools, and a dated plan to move tutorials elsewhere by early 2025.
  • Tutorials-and-scripts.md and its seven topic pages are hand-maintained inventories that do not reflect the current tutorials/ and examples/ organization or their different purposes.
  • Scene-radiance.md, Scene-creation.md, OI-(optical-image).md, and Optics-Models.md point to ISET3d-tiny and describe its status as of 2024.
  • Spectral-scene-database.md begins with an unresolved TODO to document ieWebGet and current data sources.
  • Related-software.md lists both ISET3D and ISET3D-tiny as active and contains detailed Python setup that is unrelated to the main ISETCam learning path.
  • A number of pages are empty or almost empty (Intro-to-Computational- Photography.md, Optics-and-the-slanted-bar.md, Scene-creation.md, and several model stubs). They add navigation and maintenance cost without providing a useful destination.
  • Internal-link and naming issues are already visible: Metrics.md targets a nonexistent Spatial-cielab page, and Optics-Models.md targets a nonexistent Zemax-CodeV-Macros page. Parentheses in the optical-image page name also make automated link checking need special care.
  • Image and repository URLs use several historical organizations (imageval, isetcam, and ISET). Each link must be checked rather than mechanically rewritten, especially for wiki-hosted images.

Content worth preserving

  • The concise explanation of radiometric scene and optical-image representations and their physical units.
  • The create/get/set/compute/plot/window programming pattern.
  • Scientific explanations of optics models, sensor noise and CFA sampling, color, metrics, displays, and spectral scene data.
  • The open-source motivation, the ImageVal origin, worldwide user community, Stanford teaching context, contributors, and the story of ISETCam's evolution.
  • Citations, publications, datasets, and technical/teaching videos after link verification.
  • Useful figures and screenshots after moving essential images to stable, locally versioned wiki paths where practical.

Proposed information architecture

The three wikis do not need identical page names, but they should share the same recognizable pattern: inspiration -> getting started -> tutorials -> core topics -> resources -> developers/history.

Home
Getting Started
Tutorials
  First camera simulation
  Scenes and light
  Optics and optical images
  Sensors and camera systems
  Image processing, color, metrics, and displays
Examples
Core Pipeline
  Scene Radiance
  Optics and Optical Images
  Sensors
  Image Processing
  Displays
Supporting Concepts
  Color Science
  Image Quality Metrics
  Camera Systems
Spectral Scene Data
Videos and Resources
Related ISET Projects
For Developers
  Programming Conventions
  Testing
History
Legacy Reference
License and Citations

Some headings may link directly to a landing page and some may only group sidebar entries. Keep the first screen of the sidebar focused on the new-user route and core pipeline; do not expose every retained archival page there.

Page plans

1. Home: make the front door inspirational

Rewrite Home.md closer in tone and structure to the ISETBio Home page. Proposed outline:

  1. A strong image and a short statement that ISETCam models the complete imaging pipeline in physical units.
  2. A prominent New to ISETCam? Start with Getting Started link.
  3. Why image systems engineering? Explain that cameras connect light, optics, electronics, computation, perception, and inference. Draw on FISE's welcoming account of the field's scientific beauty and broad impact in consumer imaging, medicine, robotics, automotive systems, and science.
  4. What can ISETCam compute? Show the scene -> optical image -> sensor -> image processing -> display pipeline with links to the five core pages.
  5. Learn the ideas and use the software. Introduce FISE prominently as the evolving online conceptual resource, then point to the wiki's published HTML tutorials as the practical, illustrated software route. State clearly that FISE is a work in progress.
  6. A foundation for the ISET ecosystem. State that ISETCam is a required MATLAB-path dependency for both ISET3D and ISETBio, then link ISET3D for physics-based 3D rendering and ISETBio for human visual encoding.
  7. A short reproducibility/open-source invitation and preferred citation.

Move the ImageVal story, user statistics, open-sourcing rationale, branch and release chronology, and contributor history to History.md. Keep only a two-sentence origin statement on Home if it strengthens the narrative.

2. History: preserve context without dating the landing page

Create History.md and move or adapt:

  • the commercial ImageVal period and academic sharing;
  • the user/community statistics, with the date/context made explicit;
  • the decision to open source ISETCam and the reproducibility motivation;
  • the relationship to the Stanford Image Systems Engineering course and the development of FISE;
  • the evolution from “virtual camera”/vc* names to ISET/ie* conventions;
  • the structure-based programming design that predates MATLAB's modern class system;
  • major release and repository transitions, including the 2024 ISETCam/ ISETBio refactor and the later move to current built-in testing;
  • Joyce Farrell, Brian Wandell, contributors, and collaborating institutions.

Do not copy every old download note verbatim. Turn the timeline into a stable historical narrative, and link to GitHub releases or commit history for fine-grained chronology.

3. Getting Started: one reliable first-run route

Rename and rewrite Installation.md as Getting-Started.md; add a short Installation.md moved-page stub if preserving incoming links is important. The new page should contain:

  1. Current MATLAB and toolbox prerequisites, verified against source policy.
  2. Clone/download from https://github.com/ISET/isetcam and add ISETCam to the MATLAB path.
  3. Initialize the toolbox with the current supported entry point.
  4. Run one fast installation check using an existing current tutorial.
  5. Run one small end-to-end camera calculation that creates a scene, computes an optical image and sensor response, processes the result, and displays it. t_cameraIntroduction.m and t_SystemSimulate.m are candidates, but they must be reviewed and run before selection.
  6. Explain where to go next: Tutorials for learning, Examples for adaptable analyses, the core pipeline pages for concepts, and FISE for foundations.
  7. Put optional ISET3D/ISETBio installation for ISETCam users in a short “extend the system” section, linking to those projects' current Getting Started pages. Make the direction of dependency unambiguous: those extensions require ISETCam; ISETCam does not require them.

Keep contributor testing and external validation setup out of the new-user path.

4. Tutorials and examples: curate from current source

Replace Tutorials-and-scripts.md with separate Tutorials.md and Examples.md landing pages.

For Tutorials.md:

  • Begin with a short, ordered opening path: ISET introduction -> complete camera -> scene -> optical image/optics -> sensor -> image processing -> display/metrics.
  • Build topic lists from files that exist in ../isetcam/tutorials/.
  • Publish every recommended tutorial with iePublish and make the rendered HTML the primary link, with the .m source link alongside it. Existing HTML is a starting inventory, not proof that the output is current.
  • Review the script header, run status, dependencies, and pedagogical fit before calling any tutorial “recommended” or “first.”
  • Use FISE chapter/section links selectively beside tutorials when they offer the most useful conceptual preparation; avoid mirroring the entire FISE table of contents.
  • Keep GUI and specialized material below the primary learning path.

For Examples.md:

  • Explain that examples are longer workflows intended to be adapted.
  • Curate representative examples for scenes, optics, sensors, color, image processing, displays, metrics, human factors, and full camera systems.
  • Check ieExampleTest status and % SkipFile before recommending an example.
  • Label scripts requiring external data, optional hardware/toolboxes, manual interaction, or long runtimes.
  • Link the complete source directory for discovery without reproducing all 135 filenames in the wiki.

Once the new indexes exist, either redirect or archive the old seven *-tutorials-and-scripts.md pages. Do not maintain two competing catalogues.

4a. Published tutorial HTML contract

The HTML tutorial layer is part of the wiki experience and should have an explicit maintenance contract:

  1. The .m tutorial remains the executable source of truth in ../isetcam/tutorials/.
  2. iePublish generates a self-contained HTML counterpart with inline figures and captured output. Use the repository's publishing helpers for consistent settings.
  3. Run the tutorial through ieTutorialTest and inspect the generated HTML visually before presenting it as a recommended wiki tutorial.
  4. Commit source and generated HTML together when a tutorial changes.
  5. Link the rendered HTML as the main learning experience and place a clearly labeled source link beside it.
  6. Establish one stable serving URL convention for all three wikis; do not mix raw GitHub blobs, temporary preview links, and unrelated personal web locations.
  7. Add a freshness check to the wiki-maintenance audit so an HTML file older than its source, missing its source, or failing publication review is flagged.

ISETBio and ISET3D may link directly to these published ISETCam tutorials for shared foundations. They should create their own published tutorials only for computations specific to their repositories.

5. Core pipeline pages

Retain the five-stage conceptual organization, but give each stage a consistent page shape:

  1. What the representation means physically, including units.
  2. Where it sits in the full pipeline and what comes before/after.
  3. The basic create/get/set/compute/plot/window calls.
  4. One small current code example.
  5. Recommended tutorials and examples.
  6. Related FISE concepts.
  7. Boundaries and integrations (for example, when to move from a planar ISETCam scene to ISET3D).

Proposed consolidation:

Target page Current material to merge/review
Scene-Radiance.md Scene-radiance.md, Scene-creation.md, Scenes-from-files.md, scene-programming.md, Scene-test-targets.md, Scene-basis-functions.md
Optics-and-Optical-Images.md OI-(optical-image).md, Optics-Models.md, Optics-shift-invariant.md, Optics-diffractionlimited.md, Optics-raytrace.md, ISETCam-PSF-representations.md, Lightfield.md, Zemax-and-Code-V.md
Sensors.md Sensor.md, Sensor-Model.md, Sensor-models-built-in.md, Sensor-color-filter-array.md, Sensor-noise-model.md
Image-Processing.md Image-processing.md, Image-Processing-Methods.md, relevant GUI material
Displays.md Display.md, Display-Model.md

This is a consolidation proposal, not an instruction to discard all detail. During implementation, decide whether a long, scientifically useful topic (wavefronts, ray tracing, light fields, sensor noise, CFA design) deserves a child page. Child pages should be linked from their parent rather than added as peers in the top-level sidebar.

Replace ISET3d-tiny descriptions with a concise boundary statement and links to the current ISET3D wiki. General scene/OI representation stays here; 3D recipe, Docker, asset, and rendering instructions stay in ISET3D.

6. Supporting concepts

  • Add a short Color-Science.md landing page. The current wiki has tutorial links but no coherent conceptual entry point despite color being central to ISETCam and FISE.
  • Expand Metrics.md into a useful image-quality entry point, consolidating valid spatial, color, and noise metric material and fixing the missing Spatial-cielab target.
  • Add or repurpose a Camera-Systems.md page for full-pipeline simulation, exposure/control, computational photography, and camera design. Use it to connect component models without turning Home into an API manual.
  • Decide whether cp-toolbox.md describes a supported current surface. If so, update it and link it under Camera Systems; otherwise move it to Legacy Reference.
  • Keep human-vision material in ISETCam only where it supports camera/display engineering. Link to ISETBio for detailed biological modeling.

7. Spectral scene data

Rewrite Spectral-scene-database.md as Spectral-Scene-Data.md or a similarly clear title:

  • document current ieWebGet discovery/download behavior from source;
  • retain the scientifically valuable hyperspectral, multispectral, face, and HDR dataset descriptions and permanent Stanford Digital Repository links;
  • explain data formats, wavelength ranges, calibration limits, and suitable uses at a user level;
  • merge or redirect the separate 2004/2008/2009 data pages and the awkwardly named Spectral-Scene-Database:-2D-multispectral-scene-data.md where their content is not unique;
  • link ISET3D's current scene/asset data page for rendered 3D sources rather than mixing rendering infrastructure into this page.
  • Expand Home's integrated-data paragraph during this pass. Its current high-level description omits the largest Stanford Digital Repository collections discoverable through ieWebGet, including the ISET multispectral, hyperspectral, and HDR scene collections and the rendered ISETCam scene resources. Keep the Home summary concise, link to the rewritten data page for detail, and preserve the ISET3D boundary for 3D rendering workflows.

8. Programming and testing

Split the current Programming.md into two focused pages:

  • Programming-Conventions.md: pipeline organization, noun-verb function names, create/get/set/compute/plot/window conventions, object database and visualization patterns, and links to current source guidance.
  • Testing.md: contributor-facing summary of ieUnitTest, ieTutorialTest, ieExampleTest, focused _tests_ runners, % SkipFile, and ieTestReport. Link to the repository's testing-workflow skill for detailed operational guidance.

Move the pre-class design story to History. Remove retired runner names and external toolbox requirements. Keep ISETValidate clearly described as broader system/regression validation rather than a prerequisite for ordinary users.

9. Resources, videos, publications, license, and related projects

  • Create one concise Resources.md landing page for videos, publications, datasets, FISE, related software, and community/support links.
  • Refresh ISETCam-Videos.md; label historical methods as historical and remove promises of future videos unless there is a tracked deliverable.
  • Consolidate Related-projects.md and Related-software.md. Make ISETBio and ISET3D prominent; verify the status of satellite projects before calling them active or supported.
  • Move generic Python environment setup out of the main wiki unless a current supported ISETCam workflow requires it. Project-specific Python setup belongs with that project.
  • Keep a short preferred citation on Home and maintain detailed references on a Citations-and-Publications.md page. Verify publication URLs and separate ISETCam work from ISETBio-only work.
  • Replace the long quotation on License.md with a concise explanation and a direct link to the repository's authoritative license file. Verify the actual current license before stating copyleft obligations.
  • Fix _Footer.md's incomplete Stanford URL and check whether the footer adds information not already present on Home/History.

10. Legacy and orphan-page triage

Create Legacy-Reference.md before removing obsolete pages from navigation. For every current page, choose one disposition:

  • Keep/rewrite — still part of a supported user workflow.
  • Merge/redirect — useful content belongs on a stronger parent page.
  • Archive/index — historically useful but no longer supported.
  • Drop — empty or near-empty page with no unique content.

Likely early drop candidates after checking git history are Intro-to-Computational-Photography.md and Optics-and-the-slanted-bar.md. Likely merge candidates include the tiny scene, sensor, display, and image-processing model pages. Scratch-Notes.md, old web GUI pages, camera-design GUI material, upload instructions, and the computational-photography toolbox require explicit supported/legacy decisions.

Do not put legacy pages in the main sidebar. Preserve a moved-page stub when external inbound links are likely.

Cross-wiki dependency, ownership, and linking contract

ISETCam is a required runtime dependency of both ISETBio and ISET3D: users of either repository must have ISETCam on the MATLAB path. Their documentation should say this early and consistently. The wiki update should also make it easy to simplify both dependent wikis without creating documentation gaps:

Subject Canonical wiki What the other wikis should do
Scene radiance, optical-image irradiance, 2D optics, sensors, image processing, displays, color, general metrics ISETCam Link to the relevant ISETCam concept/tutorial page
3D scene recipes, assets, PBRT, local/remote rendering, multi-element rendering workflow ISET3D ISETCam gives a short boundary explanation and links out
Human optics, cone mosaics, eye movements, retinal current and RGC mosaics ISETBio ISETCam keeps only camera/display-relevant human computations and links out
Foundational scientific concepts and historical narrative of image systems engineering FISE All wikis link selectively; none copy the book wholesale

Use stable page names for these cross-wiki targets. Once the ISETCam pages are published, update ISETBio's pending generic scene/OI links and audit ISET3D's ISETCam links. The dependent wikis should link directly to ISETCam's published HTML tutorials when those tutorials teach the shared prerequisite concepts.

Suggested implementation sequence

Keep changes reviewable and avoid breaking cross-wiki links mid-reorganization:

  1. Inventory and link baseline — classify all 57 user-facing Markdown pages; record exact internal-link failures, source-link branch errors, image locations, and externally linked page names.
  2. Home and History — rewrite Home, create History, move dated narrative, add FISE and Getting Started invitations.
  3. Getting Started — rewrite/rename Installation and verify the complete first-run route in a clean MATLAB session.
  4. Sidebar skeleton — expose only pages that now exist; add future entries incrementally rather than linking placeholders.
  5. Published tutorials — create the curated opening path and topic lists; run, publish, visually inspect, and verify every linked source/HTML pair.
  6. Examples — build the separate applied-workflow index from tested current examples.
  7. Core pipeline — update in dependency order: Scene -> Optics/OI -> Sensor -> Image Processing -> Display.
  8. Supporting concepts — Color -> Metrics -> Camera Systems.
  9. Data — update ieWebGet, SDR datasets, and consolidate legacy dataset pages.
  10. Developers — split and update Programming/Testing against current repository instructions and runners.
  11. Resources — videos, projects/software, publications/citations, license, footer.
  12. Legacy triage — add redirects/archive entries, then remove obsolete pages from navigation.
  13. Cross-wiki pass — update ISETBio and ISET3D to state their required ISETCam dependency prominently, link to the new stable ISETCam pages and published tutorials, and remove generic duplication where appropriate.
  14. Final validation — check exact internal links, blob/main/tree/main source links, images, anchors, page-name case, tutorial/example status, and sidebar reachability.

Decisions to make during implementation

  • Which image should anchor the new Home page: the existing pipeline graphic, a refreshed version, or a more inspiring image-system/application montage?
  • Which current tutorial is the most reliable first end-to-end camera run? Decide only after reviewing and running the strongest candidates.
  • Should the preferred publication citation stay on Home in full, or should Home carry one short citation plus a detailed publications page?
  • Which specialist optics and sensor pages merit remaining standalone after the core-page consolidation?
  • Should old page names receive permanent moved-page stubs, or only those with known inbound links?
  • Is the computational photography toolbox a current supported ISETCam surface or historical material?
  • Which satellite ISET projects are active enough to present as recommended extensions rather than archived research repositories?
  • What stable serving URL convention should all iePublish HTML use? Resolve this before rewriting tutorial indexes so every wiki uses the same pattern.

Completion criteria

The first major wiki-upgrade pass is complete when:

  • Home is concise, inspirational, and links prominently to Getting Started and FISE; historical material lives on History.md.
  • A new user can install ISETCam and complete one verified end-to-end camera computation from Getting-Started.md.
  • Tutorials and Examples are separate and curated; every recommended tutorial has verified, visually inspected iePublish HTML linked as the primary experience, with executable source beside it.
  • The five pipeline stages have consistent, current pages with physical units, minimal code, and clear next steps.
  • No active page presents master, ISET3d-tiny, retired test toolboxes, or old runners as the current supported path.
  • The scene-data page documents current access while preserving dataset provenance and permanent links.
  • Every sidebar target and internal wiki link resolves with exact filename case; every source link uses the correct branch and file/directory URL form.
  • Historical and unsupported material is labeled and reachable through History or Legacy Reference, not mixed into the new-user path.
  • ISETBio and ISET3D state clearly that ISETCam is required on the MATLAB path and link to stable ISETCam pages and published tutorials for shared concepts without duplicating generic pipeline documentation.