AcuConsole Database (*.acs)
| .acs | |
|---|---|
| Description | AcuConsole Database file - contains problem definition, mesh settings, solution strategy, and other settings related to the CFD problem |
| Location | Specified by you |
| Name | <problem>.acs, where you specify <problem> |
| File type | Binary, HDF5 |
The AcuConsole database file, with file extension .acs, stores all of the contents associated with an AcuSolve simulation. The .acs file is initially created by AcuConsole as an empty template that will be populated at various stages of the simulation definition. Once complete, the database stores the model geometry, mesh settings, finite element mesh, initial conditions, boundary conditions, solution strategy and other settings needed to solve a CFD problem.
All user actions/changes are saved immediately into the database (that is, the
.acs file). This means that you should
never lose data if the code crashes, machine crashes, or the like. When the database is
saved ( or 
on the toolbar), the existing database is copied to the
.acs.bak file and a new .acs is written to disk .
When you exit, you will be asked if you want to save changes. If you decide to not save the changes, the .acs.bak file is moved to .acs and the uncommitted changes from the current session are overwritten. Every action that you perform is saved to the database.
When you create multiple meshes in the same session of AcuConsole, this can lead to large database sizes. The disk space associated with the “old” meshes can be freed up by enabling the Compress the database option when closing a database. It is good practice to use this option. If you want to compress the database even further, be sure that the following option is set: compression option to Gzip=1,shuf. Note that this will cause the initial opening of the database to take longer, but greatly reduce its size on disk.