Did You Know that AcuConsole uses a hierarchical data format for it’s database. The specific format that we use is called HDF5. This has a number of implications. Here are some capabilities/characteristics that are associated with this:
1.) When a new database is created, all default parameters associated with the simulation are initialized and saved into it. This is the reason that a newly created database has a non-zero size on disk (even before the user has made any changes to it or loaded any data).
2.) All user actions/changes are saved immediately into the database (i.e. the .acs file). This means that the user should NEVER lose data (in theory, anyhow) if the code crashes, machine crashes, etc. When the save button is clicked, the current database is simply copied to the .acs.bak file. When the user exits, they have the option of not saving the changes to the database. If the user chooses not to save the changes, the .acs.bak file is moved to .acs and the uncommitted changes from the current session are not retained.
3.) Every action that the user performs is saved to the database. When users 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 released by toggling on the “Compress the database” option when closing a database. It is good practice to use this option. If you would like to compress the database even further, be sure that the following option is turned on: File—>Preferences–>Data Base–>Database compression option=”Gzip=1,shuf”. Note that this will slow down the time it takes to open the database initially, but greatly reduce its size on disk.

Browse 20+ free eBooks.
Browse 20+ free eBooks.

Have a question or comment?

Post your comment/question on our user forum.