User:Jcreer/SMS:Corrupt Project Data: Difference between revisions

From XMS Wiki
Jump to navigationJump to search
No edit summary
No edit summary
 
(12 intermediate revisions by the same user not shown)
Line 1: Line 1:
Occassionally, files used in SMS become corrupted. This can happen for a few reasons:
__NOINDEX__
Occasionally, files used in SMS become corrupted. This can happen for a few reasons:
* A file was blocked from saving correctly by system security
* A file was blocked from saving correctly by system security
* The save process was terminated early
* The save process was terminated early
* Project files were copied incorrectly or without all necessary files
* Project files were copied incorrectly
* An unknown error occured
* Project files were stored incorrectly
* An unknown error occurred


When files become corrupted, contact Aquaveo technical support to report the issue.  
When files become corrupted, contact Aquaveo technical support (support@aquaveo.com) to report the issue.  


==Rebuilding a Corrupted Project==
==Rebuilding a Corrupted Project==


In the meantime, the component pieces of the project can be reassembled in SMS and saved out as part of a new project file. We've listed an example of the file types to reassemble below.
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: The Map Module coverages saved to the project. The model-specific boundary conditions will likely need to be entered again.  
*[project name].map: 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 your project. You will need to load this before loading any of the datasets saved in the [project name]_datasets folder. Although not pictured in the example screenshot below, you may have a similar file for scatter sets.
*[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: Contains scatter sets that were in the project.
*Any GIS layers, such as rasters or shapefiles, will need to be loaded again.
*Any GIS layers, such as rasters or shapefiles, will need to be loaded again.
*Similar to loading in the *.map file, you can reload SRH simulations (including the coverages linked to them) by loading the SRHHYDRO file, found under the [project name]\SRH-2D\[simulation name] folder(s).  
 
*To load solutions for SRH simulations that were already run, import the XMDF.h5 file from the same directory as the SRHHYDRO file.
For ADCRIC models, use the following files to import the ADCIRC simulations:
* Use the fort.14 or fort .15 to immport 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:
* [project name].cmcards file will import the UGrid and create the CMS-Flow simulation.
* To load solultions 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.
 
==Related Topics==
* [[SMS:Native SMS Files|Native SMS Files]]
* [[SMS:Importing Non-native SMS Files|Importing Non-Native SMS Files]]
 


{{Navbox SMS}}
{{Navbox SMS}}
[[Category:SMS General Information]]
[[Category:SMS General Information]]

Latest revision as of 15:33, 27 May 2021

Occasionally, files used in SMS become corrupted. This can happen for a few reasons:

  • 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

When files become corrupted, contact Aquaveo technical support (support@aquaveo.com) to report the issue.

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: 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: Contains scatter sets that were in the project.
  • Any GIS layers, such as rasters or shapefiles, will need to be loaded again.

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

  • Use the fort.14 or fort .15 to immport 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:

  • [project name].cmcards file will import the UGrid and create the CMS-Flow simulation.
  • To load solultions 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.

Related Topics