| design-concepts | ||
| docs | ||
| src | ||
| tests | ||
| tools | ||
| .gitignore | ||
| Build.ps1 | ||
| NuGet.Config | ||
| Open NGC 7000.cmd | ||
| Open Sample Survey.cmd | ||
| README.md | ||
AstroFrame
An independent Windows/Linux desktop application for selecting astrophotography light frames before Siril. The spatial-reference engine uses deterministic image measurements, aligned session background models and forced stellar photometry. It is experimental: general classification accuracy and stack parity have not been established.
Run on Windows
Open artifacts/AstroFrame/AstroFrame.Desktop.exe. This self-contained build does not require Python, a GPU, or a separate .NET installation. Keep the entire application folder together.
Windows enforces a 6 GiB process allocation limit and a 3 GiB managed-heap limit. Only one desktop instance can run at a time. Analysis uses up to four workers, leaving at least two logical processors unused where available. It rejects images exceeding a 256 MiB per-frame budget and pauses when it cannot leave roughly 25% of physical RAM free (up to 8 GiB). If pressure persists for 20 seconds, completed measurements are saved for resuming. The page file is not counted as available physical RAM. Windows software rendering is used during this release. The larger limit provides headroom; it does not allocate 6 GiB in advance.
Open Sample Survey.cmd opens all supplied datasets, including NGC 7000. Open NGC 7000.cmd opens its separate project. Normal launches reopen the last project automatically. Reopening a completed project uses saved measurements. New display caches are generated on demand for older projects without recomputing classifications; subsequent previews use cached linear thumbnails. An explicit project can also be opened with AstroFrame.Desktop.exe --project "project folder".
To analyze another dataset, choose Analyze lights, select the folder containing original .fit, .fits, or .fts files, and wait for analysis. Subfolders are included. New projects are saved separately under %LOCALAPPDATA%/AstroFrame/Projects/ on Windows (the equivalent local application-data location on Linux). The input folder is not used for project storage.
Review
- Select an observing session from the selector above the workspace. The Graphite palette uses neutral charcoal and silver with muted decision colors. The Atlas layout puts exposures on the left, a large preview in the center, and quality graphs and evidence on the right. Baselines never mix targets, exposure settings, gain, filter, camera, dimensions, or Bayer patterns. Gaps over two hours and coordinate changes split sessions.
- Select a quality measurement and click the graph to inspect an exposure. One graph shows the selected metric, including stellar flux when selected. Capture order uses UTC timestamps; gaps between sessions are marked rather than drawn to elapsed-time scale.
- Filter REVIEW or REJECT, and sort by concern, star count, stellar flux, or FWHM.
- Toggle Compare nearby and Spatial overlay. Red fill shows transient sky structure in the aligned reference grid. Region outlines show forced stellar flux loss. Previews have independent display stretches; use measured flux to compare transparency.
- Use Frame view for an area-averaged exposure preview, or Nebula view for additional averaging of faint diffuse structure. Adjust Stretch to brighten the display. These controls never affect measurements, classifications or original files.
- Press 1, 2, 3 for KEEP, REVIEW, REJECT. Decisions save and advance. J/K navigates. Reset restores the automatic decision. Ctrl+Z undoes a manual decision.
- Decision evidence and measurements remain visible below the quality graph. Hover over an evidence line to read its full technical detail, and scroll the panel for additional measurements. Preview stretch and manual decisions sit below the image. Existing notes remain in saved projects and exports; the note editor has been removed. Automatic decisions and human overrides remain separate.
KEEP means consistent measurements; it does not certify a perfect frame. REVIEW means a substantial deviation or measurement uncertainty. REJECT requires strong, coherent transient sky structure, agreement between cloud/flux/star-loss measurements, severe combined morphology degradation, or catastrophic star disappearance. Small ellipticity variations alone do not trigger review.
The earlier engine missed obvious clouds and falsely reviewed a clear frame. Its rolling background baselines and detection-only flux measurements have been replaced. Analysis-version changes request reanalysis while preserving manual decisions. Display changes have their own cache version, so preview upgrades do not invalidate quality measurements.
Export to Siril
Export accepted writes sequentially named original FITS files into an empty output directory outside the source tree. KEEP frames are included by default; unresolved REVIEW frames are an explicit option. Hardlinks avoid duplicate image storage on compatible filesystems; otherwise a byte-for-byte copy is used. Copies are available as an explicit choice.
Choose the current session, one target across all sessions, or the entire project. A multi-target export uses separate target directories, preventing unrelated fields from being mixed into a single Siril input folder.
Hardlinks share file contents with originals. AstroFrame never writes FITS pixels. Process exported inputs into separate outputs in Siril; use copies for tools that overwrite their inputs. Cancellation retains completed exported files and removes incomplete copy files. Choose a new empty directory for another export.
Exports include accepted.txt with accepted output paths and decisions.csv with all decisions, timestamps, exposure durations, and review notes. Siril can load the exported FITS directory normally. The CSV is an audit manifest, not a native Siril sequence.
Build and validate
Requires a .NET 8 SDK. Build.ps1 uses the workspace-local SDK if present, otherwise dotnet from PATH:
./Build.ps1 -Test
./Build.ps1 -Publish
Standard builds on Windows or Linux:
dotnet build src/AstroFrame.Desktop -c Release
dotnet run --project tests/AstroFrame.Validation -c Release
dotnet publish src/AstroFrame.Desktop -c Release -r linux-x64 --self-contained true -o artifacts/AstroFrame-linux
The Windows build and rendered layout were tested here. Linux uses Avalonia's X11 backend and bundled Skia/Harfbuzz binaries; actual Linux execution remains untested. A Linux desktop with the usual X11/font libraries is required.
Prebuilt Linux files are in artifacts/AstroFrame-linux. On Linux, run chmod +x AstroFrame.Desktop before launching if executable permissions were lost during transfer. The managed-heap limit and RAM-pressure monitoring also apply on Linux; the Windows kernel job limit does not.
Batch analysis and review-label summaries:
dotnet run --project tests/AstroFrame.Validation -c Release -- analyze "Sample Data" "projects/Sample Survey"
dotnet run --project tests/AstroFrame.Validation -c Release -- labels "projects/Sample Survey"
See desktop layout, analysis design, observed dataset findings, NGC 7000 preview and performance findings, and stack validation protocol.
Real-image regression commands (NumPy is needed only for the diagnostic experiment, not these checks):
python tools/check_real_frames.py "projects/Sample Survey/project.json"
python tools/check_visual_holdout.py "projects/Sample Survey/project.json"
The first check covers the five exposures explicitly identified by the owner. The second is a provisional cloud-only screen of 56 fixed time samples, selected before the new decisions. Neither establishes stack parity.