Distributed Analysis Initiative
Field Array -- Frequently Asked
The questions we are asked most often about contributing your machine.
The Field Array is treated as public laboratory software, not a casual download. The questions below cover the checks contributors should perform before first run, what the worker is allowed to do, what it is not allowed to do, and what support will ask for if something looks wrong.
Will it slow down my computer?
No. The client starts work only after the machine is idle, checks keyboard, pointer, session, and power-state activity before every work window, and yields immediately when you return. The public stable channel is capped below five percent CPU while idle.
What is my computer actually doing?
It receives a narrow work unit from the Laboratories' signal record, performs numerical cross-correlation and candidate scoring, then returns the result for replay checks and staff review. Your machine never receives the complete field record.
What publisher should Windows show?
Windows should report a Valid Authenticode signature from CN="Ademero, Inc.", O="Ademero, Inc.", L=Lakeland, S=Florida, C=US. The installer was timestamped by Microsoft while the signing certificate was valid, so the signature remains verifiable after the signing certificate's issuance window closes. Also verify the SHA-256, file size, and object generation before installation.
What if the hash or signature does not match?
Do not run the installer. Delete that copy and send support the file name, SHA-256 output, download time, browser used, and the warning text you saw. Support compares those fields against the published artifact and records a disposition. Obtain the installer only from the Laboratories' download endpoint, never from mirrors or third-party download sites.
Will antivirus or SmartScreen warn me?
Some security tools warn on new or uncommon signed installers. Treat that as a reason to verify, not as a step to bypass. Run the published PowerShell hash and signature checks, confirm Windows reports a Valid signature from the expected signer, and stop if the warning names a different publisher or altered file.
What network access does it use?
The client uses outbound HTTPS to request assigned work, return numerical results, and check the signed stable-channel manifest. It does not open inbound ports, scan your network, advertise on the local network, or accept work from another host.
What diagnostics are retained?
Returned records include the assigned work-unit identifier, client version, broad platform class, timing, result shape, and health state needed to detect replay, drift, and faulty clients. They do not include your documents, screen contents, keystrokes, microphone, camera, browsing history, or file names.
How are updates handled?
Updates are accepted only from the signed stable channel. A new build must pass Authenticode validation, manifest checks, and the published release-control process before it can replace the local worker.
How do I remove it completely?
Use Windows Apps & Features. Removal unregisters the worker, screensaver, and local work cache. If removal does not complete, send only the platform and installer version so support can confirm the removal disposition.
Can I stop?
At any time. Pause or uninstall the client and the machine stops contributing. There is no account closure step and no hidden service you need to contact the Laboratories to remove.
What should I send support?
Send the smallest set of facts needed to verify the problem. Do not send private documents, screenshots of unrelated windows, raw system logs, or any file the worker did not create.
| Issue | Send | Stored | Response |
|---|---|---|---|
| Signature or hash mismatch | Installer file name, SHA-256 output, download time, and browser used. | Support case, published artifact fields, and mismatch disposition. | Do not run the installer; wait for the next stable manifest if the public channel is paused. |
| Client never starts work | Client version, Windows version, power settings, and whether the machine reaches idle. | Client version, broad OS family, and support notes. | Confirm idle and power settings; the client intentionally remains quiet during active use. |
| High CPU or fan activity | Approximate time, client version, and whether input activity resumed. | Case note and any client health telemetry already returned by the worker. | Pause or uninstall if needed; support reviews the idle-governor log before asking for more. |
| Renderer does not display | GPU model, driver date, and OpenGL capability if available. | Renderer compatibility note and platform class. | The analysis worker can continue without visuals when graphics capability is insufficient. |
| Uninstall or removal question | Only the platform and installer version if removal did not complete. | Support case and removal disposition. | Use Windows Apps & Features; removal clears the worker, screensaver registration, and local cache. |
What should I check before running the installer?
- File name: FundamentalAcoustics-stable-Setup.exe
- SHA-256: 1D759C11AE780F4F7BD60D647CD994DF78908198EBC38F9D13A19F67553C7E44
- Signature: Authenticode signature and Microsoft timestamp verified
- Signer: CN="Ademero, Inc.", O="Ademero, Inc.", L=Lakeland, S=Florida, C=US
- Object generation: 1784141267646682
- Signing timestamp: 2026-07-15T18:45:38Z
- Signer certificate window: 2026-07-14T07:02:43Z to 2026-07-17T07:02:43Z