NanoHUB@Home: Difference between revisions

Line 3:

| logo = Nanohub.png

| logo caption = nanoHUB@Home logo

| screenshot = ~~NanoHUB_tool_example.jpg~~

| screenshot =

| caption = ~~Example of nanoHUB simulation tools~~

| caption =

| status = Inactive

Line 58:

== Methods ==

[[File:BOINC logo.png|left|frameless|220x220px]]

nanoHUB@Home used the [[wikipedia:BOINC|BOINC]] middleware platform developed at the [[wikipedia:University of California, Berkeley|University of California, Berkeley]]. BOINC distributes computational work units to volunteers and validates returned results using redundancy and cross-checking techniques.<ref>{{cite web |url=https://en.wikipedia.org/wiki/Berkeley_Open_Infrastructure_for_Network_Computing |title=Berkeley Open Infrastructure for Network Computing |website=Wikipedia |access-date=2026-05-21}}</ref>

nanoHUB@Home used the [[wikipedia:BOINC|BOINC]] middleware platform developed at the [[wikipedia:University of California, Berkeley|University of California, Berkeley]]. BOINC distributes computational work units to volunteers and validates returned results using redundancy and cross-checking techniques.<ref>{{cite web |url=https://en.wikipedia.org/wiki/Berkeley_Open_Infrastructure_for_Network_Computing |title=Berkeley Open Infrastructure for Network Computing |website=Wikipedia |access-date=2026-05-21}}</ref> Unlike many traditional BOINC projects, nanoHUB@Home required [[wikipedia:VirtualBox|VirtualBox]] in addition to the BOINC client.<ref>{{cite web |url=https://boinc.nanohub.org/ |title=What is nanoHUB@Home? |publisher=nanoHUB@Home |access-date=2026-05-21}}</ref> Virtual machines were used because nanoHUB simulation tools often required complex scientific software environments and dependencies that would have been difficult to deploy natively across many operating systems and hardware combinations.

~~[[File:Boinc_logo_black.jpg|thumb|left|220px|The BOINC distributed computing platform used by nanoHUB@Home.]]~~

Unlike many traditional BOINC projects, nanoHUB@Home required [[wikipedia:VirtualBox|VirtualBox]] in addition to the BOINC client.<ref>{{cite web |url=https://boinc.nanohub.org/ |title=What is nanoHUB@Home? |publisher=nanoHUB@Home |access-date=2026-05-21}}</ref> Virtual machines were used because nanoHUB simulation tools often required complex scientific software environments and dependencies that would have been difficult to deploy natively across many operating systems and hardware combinations.

The project supported over 200 simulation tools deployed through nanoHUB.org.<ref>{{cite web |url=https://boinc.nanohub.org/ |title=What is nanoHUB@Home? |publisher=nanoHUB@Home |access-date=2026-05-21}}</ref> These applications covered a broad range of topics including:

@@ Line 3: / Line 3: @@
 | logo                 = Nanohub.png
 | logo caption         = nanoHUB@Home logo
-| screenshot           = NanoHUB_tool_example.jpg
+| screenshot           =
-| caption              = Example of nanoHUB simulation tools
+| caption              =
 | status               = Inactive
@@ Line 58: / Line 58: @@
 == Methods ==
+[[File:BOINC logo.png|left|frameless|220x220px]]
-nanoHUB@Home used the [[wikipedia:BOINC|BOINC]] middleware platform developed at the [[wikipedia:University of California, Berkeley|University of California, Berkeley]]. BOINC distributes computational work units to volunteers and validates returned results using redundancy and cross-checking techniques.<ref>{{cite web |url=https://en.wikipedia.org/wiki/Berkeley_Open_Infrastructure_for_Network_Computing |title=Berkeley Open Infrastructure for Network Computing |website=Wikipedia |access-date=2026-05-21}}</ref>
+nanoHUB@Home used the [[wikipedia:BOINC|BOINC]] middleware platform developed at the [[wikipedia:University of California, Berkeley|University of California, Berkeley]]. BOINC distributes computational work units to volunteers and validates returned results using redundancy and cross-checking techniques.<ref>{{cite web |url=https://en.wikipedia.org/wiki/Berkeley_Open_Infrastructure_for_Network_Computing |title=Berkeley Open Infrastructure for Network Computing |website=Wikipedia |access-date=2026-05-21}}</ref> Unlike many traditional BOINC projects, nanoHUB@Home required [[wikipedia:VirtualBox|VirtualBox]] in addition to the BOINC client.<ref>{{cite web |url=https://boinc.nanohub.org/ |title=What is nanoHUB@Home? |publisher=nanoHUB@Home |access-date=2026-05-21}}</ref> Virtual machines were used because nanoHUB simulation tools often required complex scientific software environments and dependencies that would have been difficult to deploy natively across many operating systems and hardware combinations.
-[[File:Boinc_logo_black.jpg|thumb|left|220px|The BOINC distributed computing platform used by nanoHUB@Home.]]
-Unlike many traditional BOINC projects, nanoHUB@Home required [[wikipedia:VirtualBox|VirtualBox]] in addition to the BOINC client.<ref>{{cite web |url=https://boinc.nanohub.org/ |title=What is nanoHUB@Home? |publisher=nanoHUB@Home |access-date=2026-05-21}}</ref> Virtual machines were used because nanoHUB simulation tools often required complex scientific software environments and dependencies that would have been difficult to deploy natively across many operating systems and hardware combinations.
 The project supported over 200 simulation tools deployed through nanoHUB.org.<ref>{{cite web |url=https://boinc.nanohub.org/ |title=What is nanoHUB@Home? |publisher=nanoHUB@Home |access-date=2026-05-21}}</ref> These applications covered a broad range of topics including: