SMS:Missing Project Data

After the official release of SMS 13.1 a cluster of bugs was identified. These bugs could result in corrupt SMS projects being saved from SMS 13.1. Specifically causes for this issue have been identified as:

• A file was blocked from saving correctly by system security
• The save process was terminated early
• Project files were copied incorrectly
• Project files were stored incorrectly
• An unknown error occurred

Aquaveo recognized that this was an extremely serious issue and is committed to minimizing the damage done to user files. Starting with version 13.1.11, a check is performed whenever a project is loaded to ensure that there is no corruption. If corruption is detected, an error message appears for the users review. In addition, whenever SMS 13.1.11 or later, a check is made whenever the project is saved to ensure the validity of the new project. A warning is provided if the save did not result in a complete project.

It should be noted that these warnings are not an indication of an error created in at the time of loading the project. Rather it is a diagnostic that a corruption already exists and needs to be rectified.

When corrupted files are encountered, please feel free to contact Aquaveo technical support (support@aquaveo.com) to get assistance in data recovery if needed.

Rebuilding a Corrupted Project

While the corrupted project file itself cannot be restored, the component pieces of the project can be reassembled in SMS and saved out as part of a new project file. Below is a list of the file types to reassemble:

• [project name].map: These are the Map Module coverages saved to the project. The model-specific boundary conditions will likely need to be entered again.
• [project name]_meshes.h5: These are the meshes that were in the project. Load this before loading any of the datasets saved in the [project name]_datasets folder.
• [project name]_grds.h5: These are the grids that were in the project. Load this before loading any of the datasets saved in the [project name]_datasets folder.
• [project name].h5: This contains scatter sets that were in the project.
• Any GIS layers, such as rasters or shapefiles, will need to be loaded again.

For ADCIRC models, use the following files to import the ADCIRC simulations:

• Use the fort.14 or fort.15 files to import the mesh and create the simulation.
• Import solution files such as fort.63, fort.64, maxele.63, and maxvel.63

For CMS-Flow, use the following files to import the CMS-Flow simulations:

• Use the [project name].cmcards file to import the UGrid and create the CMS-Flow simulation.
• To load solutions for the CMS-Flow simulation, import the [project name].h5 files.

For SRH-2D models, use the following files to import the SRH-2D simulations:

• Reload SRH-2D simulations (including the coverages linked to them) by loading the SRHHYDRO file, found under the [project name]\SRH-2D\[simulation name] folder.
• To load solutions for SRH-2D simulations that were already run, import the XMDF.h5 file from the same directory as the SRHHYDRO file.

For STWAVE models, use the following files to import the SRH-2D simulations:

• Reload STWAVE simulations (including the coverages linked to them) by loading the [simulation name].sim file, found under the simulation folder.

It is strongly recommended that a thorough review of the project be completed before continuing working with the rebuilt project.

Related Topics

• Native SMS Files
• Importing Non-Native SMS Files