nanoHUB is a research project, based at nanoHUB.org, that uses Internet-connected computers to do research in nanoscience and nanotechnology. You can contribute to our research by running a free program on your computer.
In order to participate, you will need the following programs installed on your computer
This project supports over 200 simulation tools deployed at nanoHUB.org. These tools are used for both education and research, and they enable simulations that can run in a few minutes or over several hours. The memory requirements can also vary widely, depending on the input parameters to the simulation.
The recent problem has been cleaned up. A nanoHUB machine that handled results returned from the BONIC server froze, stranding 100k successfully completed results, along with some live nanoHUB sessions. We saved all the results and set up a new dedicated machine to handle that part of the work flow. We will ramp up WU production again.
9 May 2019, 14:28:36 UTC · Discuss
We're having trouble with a nanoHUB server that sends jobs to the BOINC server for WU production. We had to temporarily halt WU production while we fix the other machine.
30 Apr 2019, 11:36:09 UTC · Discuss
Another round of upgrades complete
We are back up again. The BOINC server for this project is connected to several other key parts of the nanoHUB infrastructure. We had to upgrade the BOINC server in January to support the volume of WUs our crunchers consume. The WU's are created from nanoHUB input files by another server, and we had to do significant upgrades to that server. The database of in-progress jobs (via BOINC and other venues) was consuming all the memory on that machine, leading to swapping. That server is critical for all nanoHUB jobs, including courses at several universities, so the DB upgrade had to be thoroughly tested before rolling it out. We are tiptoeing back into the creation of WUs. TLDR: our crunchers consume jobs at a rate at least one order of magnitude higher than our other computing venues, so it stresses all the infrastructure. We're watching everything closely.
20 Mar 2019, 16:38:35 UTC · Discuss
Request for feedback
While examining the BOINC job records we noticed that some jobs are failing with the exit code EXIT_ABORTED_VIA_GUI. If you have aborted a nanoHUB@Home job in your client, what was the reason?
In the same analysis we are working to improve the time and disk estimates for nanoHUB tools that produce WUs that fail often.
21 Feb 2019, 14:56:33 UTC · Discuss
©2019 COPYRIGHT 2017-2018 NCN