Frequently Asked Questions (scroll down to submit your question)
If you can't find the answer to your question below, you can contact us at email@example.com
Q: What are the goals of the experiment?
A: To identify, test and document potential solutions to the known roadblocks in high performance computing as a service.
Q: Who can participate in the experiment?
A: The experiment is open to the entire community including international participants. Please fill in the registration form to participate.
We are looking forward to working with:
The industry end users: A typical example is a small or medium size manufacturer in the process of designing and prototyping its next product
The resource providers: This pertains to anyone who owns HPC resources, computers, and storage, and is networked to the outside world.
The application software providers: This includes software owners of all stripes, including ISVs, public domain organizations and individual developers.
The HPC experts: This group includes individuals or companies with HPC expertise, especially in areas like cluster management.
Q: I can't provide resources at this time, can I still participate in the experiment?
A: Yes. If you are interested but can't actively participate, please select the option to "receive reports at the conclusion of the experiment".
Q: Are there participation fees?
A: No, there are no fees for participation. Each active participant will be expected to contribute the necessary time and effort. Resource providers are expected to offer needed software licenses, compute resources and expert help to other active participants free of charge during the experiment. The resource providers will define their own level of participation and the limits of the resources provided.
Q: How much time will I be expected to spend on the experiment?
A: Each participant is free to define their own level of participation.
Q: I would like to participate, but can I remain anonymous?
A: Yes. Please check the related box as you fill in the registration form.
Q: When will the experiment start and end?
A: The experiment is conducted in 3 month long "rounds".
Round 4 of the Experiment starts in July 2013.
Q: I am researcher, can I participate in the experiment?
A: The Experiment focuses on industry projects, where the commercial benefit to the end-user is clearly defined. As a researcher, if you have an industry partner, a company that you are working together with, they would join the Experiment as an end-user. Depending on the resource requirements, you personally may be one of the experts in the team.
Q: Can projects extend beyond a 3-month round?
A: We strongly encourage projects to be defined in a way they can produce meaningful results and complete in one 3 month round. However, it is acceptable that the same project team decides to create another project in the next round to achieve further goals.
Q: Will you send this Kickoff PPT to me?
A: Yes, every experiment participant (including those who could not participate in the GoToWebinar) will receive the updated kick off meeting packet, the slides, the link to the recorded webinar, and the link to a new CAE article (just appeared in HPC in the Cloud) which highlights especially the benefits for industry end-users and for ISVs.
Q: Where can I get more information from about HPC in the Cloud?
A: For more information about please HPC in the Cloud links page.
Q: Can you give examples of the types of projects you are working on?
A: We have teams actively working on a diverse set of industry end-user projects ranging anywhere from car acoustics to turbine dynamics, from fastening capacity of anchor bolts to simulation of blood flow inside rotating micro-channels.
The collection of 25 case studies which was published in June 2013 is available for download at:
Q: What type of computing resources are available in the UberCloud HPC Experiment for projects?
A: With over 40 resource providers participating in the HPC Experiment we can find almost any specific computing resource which is requested from the end-user. There are tightly and loosely coupled systems, with Ethernet or Infiniband interconnect, with or without GPGPUs, etc. As soon as the end-user provides his or her profile, including the application software, we are usually able to match the best suited resource.
Q: Is the software selection limited to what's available on the UberCloud Exhibit?
A: No. We have currently 47 software providers participating in the HPC Experiment. Although they represent some of the largest ISVs, we still often have end-users with application software not present in the experiment. Then we identify a resource provider who is willing to implement this software on his resource, and then the team can run their jobs. For example, on Amazon AWS you can upload your software yourself, and then run.
Q: How are you transferring the data across for running the experiment?
A: Most common solution is FTP (and secure FTP when needed). We also know other solutions, such as sending a USB drive, can be an option where necessary. We encourage end-users to submit their projects and we will work through the project specific details such as file transfers.
Q: If the file size of results is around 100 GB, then how the files would be transferred back to the user?
A: Indeed, several of the past teams faced this challenge, for example with results from their Abaqus runs. Then we recommend remote visualization, and in case the final data is needed internally, some teams just shipped the result file(s)
Team 26 for example found that data transfer via the network was too slow; so they suggest that final results might be better transferred through an external USB hard drive via FedEx.
Q: What is the maximum number of cores that an end user can request for an experiment?
A: The experiment projects usually have an upper bound of 1000 cpucore hours, for good reasons free (experiment; not competing with our services partners), exceptions are possible if more cpucore hours are needed. But, experiment jobs shouldn't be production jobs. Then, the number of cores just depends on the application. If the application software is highly scalable, you can use 1000 cores if this makes sens, and you still can run the job for one hour. If the application software is not scalable and runs best on 8 cores, you could do one long run for 120 hours, or e.g. 12 runs each for 10 hours.