-
Notifications
You must be signed in to change notification settings - Fork 0
05_FAQ_Troubleshooting
BioPro CI Bot edited this page May 16, 2026
·
1 revision
Find answers to common questions and solutions to technical issues in BioPro.
Yes. BioPro Core is open-source. Some specialized high-performance plugins may require separate licensing depending on the author, but the platform itself is free for academic use.
No. BioPro is a "Privacy-First" local application. Your images, results, and project files never leave your machine unless you explicitly share them or sync them to your own cloud storage.
We recommend the following format:
"Analysis was performed using the BioPro Analysis Suite (v1.2.0), incorporating the [Plugin Name] module."
- Check for locks: Ensure another instance of BioPro isn't already using the folder.
- Permissions: Ensure you have write access to the directory.
- Chrome Compatibility: BioPro uses a Chromium-based engine. Ensure your system drivers are up to date.
- JavaScript Enabled: If you've modified internal settings, ensure JavaScript execution is not disabled.
- This usually means a required field is missing or invalid. Check for red highlights in the "Input" or "Parameters" screen.
Don't panic! BioPro has a built-in Diagnostic Engine that captures errors as they happen.
- View Logs: Click this in the error dialog to open your local log folder.
- Copy Details: Click this to copy a full technical report (including the "Black Box" history) to your clipboard.
- Contact Developer: Reach out to the project maintainers with the copied details for support.
- GitHub Issues: Report bugs on our GitHub Repository.
-
Log Files: You can find internal logs at
~/.biopro/biopro.log. - Diagnostic Reports: When reporting a bug, please use the "Copy Details" button in the error dialog to provide developers with the necessary context.