Welcome to the Rocstar multiphysics simulation application!
For information on building and installing Rocstar see the Rocstar Quickstart Guide.
For further details about the requirements of building Rocstar, click here.
For more details on how to run Rocstar including information regarding its build structure, click here.
Historically, there have been many challenges involved with rocket simulation. There was a need to handle challenges such as:
Development for Rocstar was started at the Center for Simulation of Advanced Rockets with the overarching goal of simulating solid propellant rockets. The Simulation Suite aimed to do several things:
The entire Rocstar Simuation Suite is laid out as such:
Here are quick links to access the userguides for some of the various Roc-modules. These guides include information for the user and/or the developer.
Modules | User Guides | Developer Guides | Combined Guides |
---|---|---|---|
Misc. | Rocstar Suite | ||
Rocblas | X | X | |
Rocburn2D | X | ||
Roccom | X | ||
Rocface | X | ||
RocfluMP | X | ||
Rocfrac | X | X | |
Rocin/Rocout | X | ||
Rocketeer | X | ||
Rocman | X | ||
Rocmap | X | ||
Rocmop | X | X | |
Rocpart | X | X | |
Rocrad | X | X | |
Rocsolid | X | X | |
Rocturb | X | X |
The table show gives additional guides that aren't necesarily user or developer guides. Click Here for more information about each document.
Modules | Extra Guides | |
---|---|---|
Rocstar | Service Components | Time Zooming |
Rocman | Rocman Orchestration | Rocman Paper |
Roccom | Integration Interface | FileFormats |
Rocface | Surfdiver |
Developers at Illinois Rocstar attempt to adhere to a set of semi-flexible guidelines for documentation and coding standards when developing new code. It is not guaranteed that existing code meets these guidelines; however, every effort should be made to follow them for new code. We also suggest that developers working in areas of older code attempt to "spruce things up a bit" so that the code is in better shape than when they found it. For more details on our coding and documentation standards, see the following pages: