Quick Start
This page walks through one complete first-use flow with the web UI.
Open the Analysis Task tab in the right drawer. Enter the path to the project you want to analyze, or click Browse... to pick it from the file system.
After the path is set, click Run Analysis.
For a predictable first run, you can try the built-in fixture package: test/fixtures/DebugFixturePkg. It is small, local, and intentionally covers common graph scenarios such as overloads, stdlib calls, package calls, and macro-related cases.
After analysis completes, if the node count is below 1000 and the edge count is below 5000, you should be able to see a function call graph in the canvas. It should look roughly like this.
Click one of the nodes, for example base_overloaded_length_demo, and all nodes along that node's path will be highlighted automatically.
Click the same node again. Its border will turn magenta, which means you have entered reachability mode.
In reachability mode, only the nodes on that node's path are shown. Reachability depth is controlled by Reachability Depth in the Graph Explorer panel, and the displayed call direction is controlled by Reachability Direction.
Click empty space to clear the current graph state. Double-click empty space to reset the canvas and viewport.
Troubleshooting
The backend or frontend port is already in use
If something is already listening on 8099 or 5174, stop the conflicting process or restart the relevant service with a different port in your local environment.
The UI rejects the analysis path
Analysis Path must point to a local absolute path on the same machine as the backend.
The UI cannot analyze anything
If you are using the default setup, make sure the backend is running and static serving is enabled.
If you are using the frontend development server, make sure both services are running:
- the Julia backend
- the web frontend
In both cases, analysis requests still go through the backend.
Need Help?
If you have questions, please open an issue on the project's issue page.