Troubleshooting Guide¶
Browser and Performance¶
Construct requires Google Chrome to ensure a consistent experience across all tools. While other browsers might seem to work, you may encounter unexpected behavior or missing features. If you're experiencing issues, first verify you're using Chrome.
Performance issues often stem from browser-related factors. If Construct feels sluggish, start by closing unnecessary tabs and clearing your browser cache. To do this, open Chrome Settings, navigate to Privacy and Security, and clear your cached images and files. This often resolves visual glitches and performance problems.
Certain Chrome extensions, such as ad blockers, can interfere with Construct's functionality. If you encounter unusual behavior, try temporarily disabling your extensions to identify if they're the source of the problem.
Finding Your Files¶
One of the most common questions we receive is about missing or outdated files. Since Construct uses Git-based storage, your files might be on a different branch than you expect. When you can't find a file, check the branch selector in the header. Remember that while 'main' is the default branch, your organization might use different branches for development work.
Files you recently created or modified might not appear immediately in someone else's view. This is normal Git behavior – they may need to refresh their browser or switch to your branch to see the changes. If you're working in QDE, make sure to save your files and check the Git status in the terminal.
Memory and Simulation¶
Understanding memory requirements is crucial when working with quantum circuits. The simulator's memory usage follows a clear pattern – each additional qubit doubles the required memory. With 10GB of available RAM, you can comfortably simulate up to 29 qubits, which needs 8GB (leaving 2GB for system use). Need to simulate 30 qubits? You'll need 16GB of RAM. This doubling continues: 31 qubits requires 32GB, and so on.
If you're running up against memory limits, consider breaking your circuit into smaller components or using incremental testing. Resource estimation before full simulation can help you plan your approach effectively.
Memory Requirements Reference¶
| Qubit Count | Required RAM | Typical Use Case |
|---|---|---|
| 28 qubits | 4 GB | Standard development and testing |
| 29 qubits | 8 GB | Standard development and testing |
| 30 qubits | 16 GB | Complex algorithm development |
| 31 qubits | 32 GB | Advanced research scenarios |
| 32 qubits | 64 GB | Specialized research applications |
Info
Remember that these requirements assume you're keeping at least an additional 2GB free for system use.
Tip
The standard instances in QDE will either come with 8GB or 16GB RAM, supporting 28 or 29 qubits.
QRE Analysis Challenges¶
When working with QRE analysis, you might encounter situations where the analysis won't start or produces unexpected results. Often, this comes down to the circuit's validity or input parameters. Start by verifying your circuit and checking for any error messages in the logs.
Getting Help¶
When you need help, providing context is crucial. Before reaching out to support, try to gather relevant information about your issue. What were you doing when the problem occurred? What changed recently in your workflow? Have you tried clearing your browser cache or restarting Chrome?
When contacting support, include your organization name and project context. Screenshots of error messages are particularly helpful, as are the steps to reproduce the issue. This helps us identify and resolve your problem more quickly.
Tip
Please click the Bug report icon in the bottom left of the Construct page to submit a bug report.
A Note About Future Updates¶
Construct is constantly evolving, and with new features come new challenges and solutions. We'll continue to update this guide as the platform grows and changes. Keep an eye on project announcements for updates about new capabilities and known issues.