Is SciDAVis Safe to Download and Install?

Short answer: yes — as long as you download it from the right places. This page explains what “right places” means, why Windows flags the installer, and what you can and cannot verify. Nothing here asks you to take our word for anything you can check yourself.

Does SciDAVis contain viruses or malware?

SciDAVis is open-source software: its entire source code is published on GitHub (github.com/SciDAVis/scidavis), where anyone can read, audit, and build it. There is no bundled adware, no toolbar, no “optional offers” in the official installers — those tricks are a hallmark of shady download sites, not of this project. In years of distribution through SourceForge and community sites, no malware has ever been reported in an official SciDAVis build.

The real risk is not SciDAVis itself but where you get it. Download only from these sources:

• The official SourceForge project page (sourceforge.net/projects/scidavis)
• The upstream GitHub repository above
• This site’s download page, which links to those official sources

Avoid random “free download” mirrors you find through search ads — repackaged installers from third-party sites are the classic way malware gets attached to legitimate open-source software.

Why does Windows say “Unknown publisher”?

When you run the Windows installer, SmartScreen may warn that the publisher is unknown and ask whether you really want to run it. This is expected, and it does not mean the file is malicious.

Here’s why: Windows verifies software identity through code-signing certificates, and the trustworthy kind (EV certificates) cost a few hundred dollars every year. SciDAVis is maintained by volunteers with no commercial budget, so its installers are simply not signed — Windows is telling you “I can’t confirm who made this,” not “this is dangerous.”

To install anyway: on the SmartScreen warning, click More info, then Run anyway. If Windows Defender itself flags the file (distinct from SmartScreen), do not override it — re-download from one of the sources above and scan the file first (see below).

What about macOS Gatekeeper?

Same story on the Mac side: the app is not notarized by Apple, so Gatekeeper may refuse to open it on first launch. Right-click (or Control-click) the SciDAVis app and choose Open, then confirm — or open System Settings → Privacy & Security and click Open Anyway next to the SciDAVis entry. This is a one-time step.

Can I verify the download with a checksum?

Honestly: not against an official hash. We checked the public SourceForge file metadata for the current SciDAVis installers and could not find officially published SHA-256 checksums to compare against. Some projects publish them; this one currently does not, so any hash you see quoted on a forum is unverifiable — treat it accordingly.

What you can do instead:

• Upload the installer to VirusTotal before running it — it scans the file with dozens of antivirus engines and takes a minute.
• Download from the same source twice, or check the file size against the download page — a corrupted or tampered file rarely matches.
• Keep your antivirus definitions current, as you should anyway.

Do I need to disable my antivirus?

No — and you should be suspicious of any download guide that tells you to. SciDAVis installs cleanly with antivirus software running. The SmartScreen “Unknown publisher” prompt and a real antivirus detection are two different things: the first is about identity, the second is about content. Only ever override the first. If your antivirus quarantines the installer itself, stop, re-download from an official source, and scan the new file with VirusTotal before doing anything else.

You can check the signature yourself

On Windows, right-click the installer → Properties → Digital Signatures tab. You will find no signature listed — which is exactly what this page described, and it is the honest state of a volunteer-built installer. If a copy of “SciDAVis” you downloaded does show a signature from some company you have never heard of, that is a red flag: the official builds are unsigned, so a signed copy came from someone else’s repackaging. Delete it and download from the official sources.

The bottom line

SciDAVis is safe software from an open, auditable project — the warnings you see are about unsigned installers from a volunteer project, not about detected threats. Download from SourceForge, GitHub, or this site’s download page, scan the installer if you want extra peace of mind, and you’ll be fine.

How to Cite SciDAVis in a Paper

If SciDAVis helped you analyze data or prepare figures, citing it does two things: it gives credit to the volunteer developers who maintain it, and it makes your work reproducible — readers can see exactly which tool and version produced your results. Unlike some tools, SciDAVis has no journal paper with a DOI to point at, so you cite it as software.

Who wrote it?

According to the upstream repository’s README, the people who wrote parts of the SciDAVis source code are, in alphabetical order: Tilman Benkert, Knut Franke, Miquel Garriga, Arun Narayanankutty, and Russell Standish. If your style guide prefers a corporate author, “SciDAVis Development Team” is a reasonable substitute. The program is released under the GNU General Public License.

Which version and year?

Always cite the version you actually used — check Help → About in the program. The most recent upstream source release tag is 2.9.2 (April 2022), and the prebuilt packages on SourceForge are at version 2.8. The templates below use placeholders where they exist; replace them with your version, year, and URL before pasting into your manuscript.

APA (7th edition)

Template:

SciDAVis Development Team. (Year). SciDAVis (Version x.x) [Computer software]. URL

Filled example (adapt to your version):

SciDAVis Development Team. (2022). SciDAVis (Version 2.9.2) [Computer software]. https://github.com/SciDAVis/scidavis

If you prefer naming the developers:

Standish, R., Benkert, T., Franke, K., Garriga, M., & Narayanankutty, A. (2022). SciDAVis (Version 2.9.2) [Computer software]. https://github.com/SciDAVis/scidavis

BibTeX

Template:

@software{scidavis,
  author = {{SciDAVis Development Team}},
  title = {SciDAVis},
  version = {x.x},
  year = {Year},
  url = {URL},
}

Filled example (adapt to your version):

@software{scidavis,
  author = {{SciDAVis Development Team}},
  title = {SciDAVis},
  version = {2.9.2},
  year = {2022},
  url = {https://github.com/SciDAVis/scidavis},
}

If your bibliography style does not recognize @software, use @misc with the same fields — most styles accept it.

Plain text

For journals or repositories that want a plain-text citation:

SciDAVis Development Team. SciDAVis, version 2.9.2. 2022. Available at https://github.com/SciDAVis/scidavis

Which URL should you use?

Either of the two canonical addresses is fine — pick one and use it consistently:

• GitHub repository: github.com/SciDAVis/scidavis — the current home of the source code, issue tracker, and release tags.
• SourceForge project: sourceforge.net/projects/scidavis — hosts the prebuilt installers most people actually download.

If you used a prebuilt installer (the common case), the SourceForge URL is arguably the more precise pointer, since it leads a reader to the same binary you ran. If you built from source or want to reference the code itself, use GitHub.

What if your journal asks for a DOI?

Some journals and data repositories strongly prefer DOIs. SciDAVis has no registered software DOI that we could verify, so do not invent one. If your submission system requires a DOI field, leave it blank or write “none” rather than linking to an unrelated record — a fake DOI is worse than none. The URL plus version number fully identifies the software for reproducibility purposes.

One-line Methods section wording

If you just need a sentence for the Methods section:

Data analysis, curve fitting, and figure preparation were performed with SciDAVis version 2.9.2 (SciDAVis Development Team, 2022; https://github.com/SciDAVis/scidavis).

Replace the version number with the one from Help → About. For the official download sources, see our download page, which links the upstream GitHub repository and SourceForge project.

If you modified the code

If you patched SciDAVis itself — added a fit function, fixed a bug, changed the analysis — say so explicitly. Cite the base version as above, then add a sentence like: “The peak-fitting routine was modified from the 2.9.2 source; the modified source is archived at [your repository or supplementary materials link].” Readers need to know your results did not come from the stock build.

Every Plot Type in SciDAVis, at a Glance

SciDAVis can draw more than “a line through some points” — but the full list is scattered across the Plot menu, the 3D Plot submenu, and the scripting API. This page is the map: every plot type the official SciDAVis Handbook confirms, one sentence each, with links to the in-depth tutorials. Pick your type here, then go deep on the linked guide.

The key rule of thumb: the plot type follows the data container. Data in table columns gives you 2D plots from the Plot menu; three XYZ columns give you 3D scatter; a regular grid in a matrix gives you 3D surfaces and contours. Choose the container first, and the right plot types appear on their own.

2D plots from table columns (Plot menu)

Select X and Y columns in a table, then choose from the Plot menu (or the plot toolbar):

Logarithmic axes are a formatting choice, not a plot type

Any of the 2D types above can be drawn on log scales: double-click an axis (or Format → Scales) and switch the type to logarithmic. The log-scale guide covers when log axes help and when they mislead.

3D plots: scatter from tables, surfaces from matrices

3D data lives in two places, and the plot types follow: XYZ triplets in table columns give scatter-style plots; a regular Z grid in a matrix gives surface-style plots. The full walkthrough is in 3D Scatter and Surface Plots: A Complete Guide — here is the complete list:

From a table (Plot → 3D Plot)

From a matrix (3D Plot submenu, active when a matrix is selected)

How to choose: a 30-second decision table

New to the program? Work through importing data first, then come back here once your numbers are in a table.

SciDAVis Keyboard Shortcuts

Every shortcut below is taken from the official SciDAVis handbook’s toolbar reference. Memorize the dozen you use daily and you’ll rarely touch the menus. Shortcuts follow the active window: SciDAVis automatically enables the toolbar (and its keys) that matches the window you’re working in — a table, a graph, or a 3D plot.

File shortcuts — new windows and project management

Edit shortcuts — undo and clipboard

The Undo/Redo limitation matters: if you reformat a plot and don’t like it, Ctrl+Z won’t save you. Get in the habit of saving (Ctrl+S) before restyling a finished figure.

Graph shortcuts — zoom and data inspection

Lost your curve after zooming into empty space? Ctrl+Shift+R is the panic button — one press and the full data range is back.

Tips

• Toolbars can be dragged by their left handle and docked to any side of the main window — or floated on the desktop. Right-click the menu area to show or hide individual toolbars.
• If a shortcut seems dead, check which window is active: a graph shortcut won’t fire while a table has focus, and vice versa.

Now put the shortcuts to work — follow the SciDAVis tutorials to learn importing, plotting, fitting, and 3D surfaces step by step.

SciDAVis on Apple Silicon (M1, M2, M3): What Actually Works

The short answer: there is no native Apple Silicon (ARM) build of SciDAVis. What you can do — and what real users have confirmed works — is run the Intel macOS build through Apple’s Rosetta 2 translation layer. A SciDAVis 2.8 user on an M1 Max reported on the scidavis-users mailing list (2023) that it runs fine under Rosetta 2, with minor caveats around colors on dynamic desktops and weak dark-mode support. This page collects that honest state of affairs and the exact install steps.

Does SciDAVis run on M1 / M2 / M3 Macs?

Yes — via Rosetta 2. The official macOS package is an Intel (x86_64) application, and macOS transparently translates it on Apple Silicon machines. The reported experience from the community mailing list:

• Core functions work: tables, plots, curve fitting, and figure export all behave normally.
• Small cosmetic issues: one M1 Max user reported color/rendering quirks when macOS uses a dynamic desktop wallpaper — switching to a static desktop picture cleared it up.
• Dark mode is a known weak spot: poor dark-mode support is a long-standing SciDAVis issue, not specific to Apple Silicon. If panels or text look wrong in dark mode, switch macOS to Light appearance while you work in SciDAVis.

What this means in practice: for day-to-day data analysis and figure making, SciDAVis on an M-series Mac is a working setup. It is not, however, a native app — expect slightly slower first launch (translation) and the usual Rosetta caveats.

Install steps on Apple Silicon

1. Get the Mac build: download the DMG from our Mac download page — it is the same Intel build everyone uses on macOS.
2. Mount and install: open the DMG and drag SciDAVis to Applications, as with any Mac app.
3. Let Rosetta do its thing: the first time you launch an Intel app on Apple Silicon, macOS offers to install Rosetta 2. Accept it. (If the prompt never appears, install it manually from Terminal: softwareupdate --install-rosetta, then relaunch SciDAVis.)
4. First-launch security: if macOS blocks the app (“cannot be opened because the developer cannot be verified”), right-click the app and choose Open, then confirm. This is standard for apps distributed outside the App Store.
5. Set a static desktop picture: if you use a dynamic desktop and notice odd colors in the plot windows, switch to a static wallpaper — this fixed the rendering quirk reported by an M1 Max user.

What doesn’t work (honest list)

Tips for a smooth Rosetta setup

• Keep your data project portable: save your work as .sciprj project files — they open identically on Intel Macs, Apple Silicon Macs, Windows, and Linux, so you can move between machines.
• Report what you find: Apple Silicon specifics are under-documented because few users report back. If you hit a reproducible problem, the scidavis-users mailing list is where developers actually read feedback.
• Don’t chase fake native builds: any site offering “SciDAVis for M1/M2 native” outside the official project channels is not the real project. The official macOS build remains Intel-only.

Apple Silicon FAQ

Is Rosetta 2 noticeably slower for SciDAVis? For typical lab datasets — tables with thousands of rows, ordinary 2D plots — no. Rosetta’s overhead is most visible at launch and during heavy computation; interactive plotting feels the same as on Intel.

Can I compile a native ARM build myself? In principle, yes — SciDAVis is open source (GPL) and Qt builds for ARM64. In practice, that means wrestling with Qt dependencies and the Qwt plotting library on your own machine. Unless you enjoy that kind of project, Rosetta 2 is the pragmatic answer.

Does this affect Windows on ARM (Snapdragon) too? Same story: the official Windows build is x86_64 and runs under Microsoft’s Prism/x64 emulation on Copilot+ PCs. The guidance on this page applies by analogy, though the reported cosmetic issues above are from macOS users specifically.

This page is maintained by an independent community resource site and is not affiliated with the SciDAVis developers. Apple Silicon behavior described here comes from real user reports; your mileage may vary slightly by macOS version.