Skip to content

Volunteer participation

RoTab supports browser-based research calculations using fixed Rosetta protocols. Participation, resource settings, and scientific interpretation have distinct controls and limits.

Start volunteering authorizes compatible future assignments under the saved local resource budget. Contribute accepts one offered model. Discovery can remain enabled without authorizing computation.

Pause new tasks stops later acceptance while allowing the active model to finish. Pausing or stopping the calculation itself terminates its worker. Completed models remain saved; unfinished models can replay from their recorded seeds. Closing the last RoTab stops browser execution.

Worker count and intensity are local preferences. A publisher cannot raise them remotely. Calculations use CPU, memory, battery, and network bandwidth. Startup is not fully governed by the cooperative intensity target, and temperature/fan behavior varies by device. Completion time and network availability are not guaranteed.

Submitted research

A submitted campaign shares its target with assigned participants and can display its title and description in their dashboards. Submission therefore requires authority to share and compute the supplied data. Confidential research and personal information require appropriate handling outside this public volunteer workflow.

The submitting browser coordinates assignments and collects results. Its availability and local database are part of the campaign's recovery boundary. Browser storage is not a permanent research archive; exported records provide a separate copy.

Recipients can retain data delivered to them. Removing a local campaign does not erase copies already received by volunteers. Data and privacy.

Scientific interpretation

Energy is reported in Rosetta Energy Units. It is not a clinical measurement or an experimental observation. Optimization snapshots are not a physical molecular-dynamics time series. The Pomodoro chain graphic is a timer illustration and does not run a scientific trajectory.

A signature identifies provenance; a receipt confirms matching delivery. Neither establishes independent scientific correctness. Native rescoring and task-specific validation remain separate from ordinary network admission.

RoTab supplies no diagnosis, treatment recommendation, payment, cryptocurrency mining, official Rosetta@home result acceptance, or BOINC credit. The project is independent of endorsement by RosettaCommons, Rosetta@home, and BOINC.

Services and rights

Rosetta, its database, and third-party services have terms separate from original RoTab application code. Licensing and availability describes the component boundaries. Relay, STUN/TURN, weather, and Google services retain their own availability and data practices.