DalaDocs
A practical guide to the current DalaDose workflow: importing CT and dose files, reviewing slices and 3D views, drawing regions of interest, running DVH/analysis, building beam models, launching TOPAS, and exporting results.
Intended Use
DalaDose is a research workspace for CT, dose, ROI, beam model, TOPAS, and analysis workflows. It is intended for radiation research review and development, not clinical treatment decisions.
Getting Started
Web App
The web app runs in the browser at app.daladose.com. It can open browser-selected files and folders, but it cannot directly run a local TOPAS executable.
Desktop Client
The desktop client can access local files more naturally and can point to a local TOPAS installation. For Linux, download the Debian package from the downloads page.
Basic Workflow
- Add a CT DICOM folder.
- Add or import dose files.
- Link dose files to the DICOM folder if needed.
- Adjust CT and dose display settings.
- Create ROIs and draw contours.
- Review DVH or other analysis outputs.
- Export workspace data, images, reports, or dose outputs.
Workspace Model
A workspace is the container for everything you are reviewing: DICOM folders, dose files, beam models, reusable clipping presets, ROIs, analysis artifacts, TOPAS run history, and display settings.
| Concept | What It Means |
|---|---|
| DICOM folder | A folder of CT DICOM slices that DalaDose groups into a CT volume. |
| Dose file | A dose dataset from RT Dose, TOPAS, NumPy, or supported scorer output. |
| ROI | A region of interest, such as a target, organ, tumor, or custom research region. |
| Contour | A drawn 2D outline on a slice. Multiple contours can belong to one ROI. |
| Beam model | A beamline configuration that can be represented visually and exported/run through TOPAS. |
Left File Tree
The left sidebar behaves like a file explorer for the workspace. Parent rows expand and collapse; child rows usually select or inspect a specific item.
| Section | Purpose |
|---|---|
| DICOM Folders | Imported CT folders. Expanding a folder can show linked dose files. |
| Dose Files | Dose files added to the workspace but not necessarily linked to a CT folder. |
| View Presets | Reusable 3D clipping/crop presets that can be applied to DICOM folders. |
| Regions Of Interest | ROIs created inside the workspace. Contours appear under their parent ROI. |
| Beam Models | Beamline models and their run history. |
Dose Linking
Dose files can be kept in the general Dose Files section or linked to a DICOM folder. Linked dose files appear under that DICOM folder with a checkbox. The checkbox controls whether the dose is displayed over the CT slices and in the 3D view.
Center Viewer
The center area shows CT slices, dose overlays, DVH, 3D views, or beam model views depending on the selected mode.
| Button | What It Shows |
|---|---|
| View All | Axial, sagittal, coronal, and DVH panels together. |
| Axial | Single axial slice view. |
| Sagittal | Single sagittal slice view. |
| Coronal | Single coronal slice view. |
| DVH | Dose Volume Histogram panel. |
| 3D View | Volume-rendered CT/dose view with camera controls. |
Crosshairs And Slices
Crosshairs mark the current point in the CT volume. Dragging in a 2D view updates the crosshair and corresponding slice positions. Slice controls move through the active plane.
Regions Of Interest And Contours
ROIs are the named research regions you care about. Contours are the drawn outlines that define an ROI on individual CT slices.
| Action | What Happens |
|---|---|
| Add ROI | Creates a new ROI, selects it, and adds it to the file tree. |
| Add Contour | Starts drawing a contour for the selected ROI. |
| Right-click ROI | Shows context actions such as rename, delete, or delete all contours. |
| Finish drawing | Saves the contour to the ROI and makes it available for analysis. |
For analysis, a flat-looking contour on one CT slice is treated as occupying that slice thickness. Multiple contours across slices become a 3D region for volume and dose calculations.
Dose Volume Histogram (DVH)
A DVH summarizes how much dose is delivered to an ROI volume. The dropdown can show all regions or a single selected region.
| Metric | Meaning |
|---|---|
| Minimum dose | The lowest dose found inside the ROI. |
| Mean dose | The average dose across the ROI. |
| Maximum dose | The highest dose found inside the ROI. |
| Volume | The physical ROI volume estimated from CT spacing and slice thickness. |
DalaDose displays very small doses in compact units when possible so values are easier to read than long scientific notation.
Beam Models
Beam Models is a separate workspace area for building and running TOPAS-style beamline configurations. Selecting Beam Models in the left sidebar switches the center and right panels away from CT review and into beam model editing.
| Item | Purpose |
|---|---|
| Components | Sources, filters, collimators, phantoms, scorers, and other beamline pieces. |
| 3D pipeline view | A visual left-to-right representation of the beam model components. |
| Selected component panel | Shows editable parameters for the component selected in the 3D view or file tree. |
| Run History | Stores TOPAS run attempts, status, progress, stdout, output folder, and artifacts. |
Beam model files should remain editable as structured DalaDose data. TOPAS text files are generated outputs, not the only source of truth.
TOPAS Runs
TOPAS is a Monte Carlo simulation tool used by medical physics and radiation research teams. In DalaDose, a TOPAS job means: take a beam model or TOPAS input file, run TOPAS, collect logs and output files, and attach the results back to the workspace.
Run Targets
| Target | What It Means |
|---|---|
| Local machine | Runs TOPAS on the current desktop client using the configured local TOPAS path. |
| Remote worker | Runs on another signed-in desktop worker connected to the same account/org. |
| Cloud worker | Future hosted or BYO-cloud compute target for larger jobs. |
Threads
The TOPAS run panel can choose how many CPU threads to use. More threads can finish faster, but will use more of the computer while the job runs.
Progress
DalaDose reads TOPAS history progress from stdout when available. Some TOPAS jobs spend time finalizing output after the last reported history, so 99% can mean it is merging threads or writing result files.
Settings
Settings contains account controls, sync choices, TOPAS installation setup, worker service controls, and activity logs.
| Setting | What It Does |
|---|---|
| Account | Sign in or sign out. Signing in does not automatically upload local files. |
| Workspace Sync | Controls whether workspace data stays local or syncs to the cloud. |
| TOPAS Installation Path | Sets the local TOPAS executable used by the desktop client. |
| TOPAS Worker Service | Allows signed-in web/desktop clients to send TOPAS jobs to this computer while DalaDose is open. |
| Activity | Shows recent app, import, export, worker, and job events. |
Exports
Export commands are collected under the Export menu. Depending on the active workspace and available data, DalaDose can export workspace files, ROI data, masks, reports, images, DVH CSVs, dose profiles, gamma reports, and TOPAS outputs.
Local workspace exports should not require a server connection. Cloud exports are only used for explicitly synced or hosted data.