EIO - INPUTOUTPUT

Cannot find Casefile S1

The solver is not able to find the cfg file. Please check the path in your launch command.

Found non-empty output data directory at S1 when "cleandir_opt" is set to BREAK.

The solver encountered a non-empty output data directory when "cleandir_opt" has been set to BREAK. Either remove the output data directory and run again or change "cleandir_opt" to MODIFY or PURGE. When set to MODIFY, the solver creates a new output data directory by appending simulation start time to the original output data directory name. When set to PURGE, the contents of the output data directory are removed.

Failed to create case directory.

The solver encountered an issue while creating the case directory. The path may not be accessible. Retrying the simulation or changing the case path may resolve this issue.

Failed to create case directory.

The solver encountered an issue while creating the case directory. The path may not be accessible. Retrying the simulation or changing the case path may resolve this issue.

Cannot find Casefile S1

The solver is not able to find the cfg file. Please check the path in your launch command.

Failed to empty OUTPUT directory.

The solver failed to remove the contents of OUTPUT directory. The files may be in use by another process.

Failed to empty PREVIEW directory.

The solver failed to remove the contents of PREVIEW directory. The files may be in use by another process.

Failed to empty RECON directory.

The solver failed to remove the contents of RECON directory. The files may be in use by another process.

Failed to empty LOG directory.

The solver failed to remove the contents of LOG directory. The files may be in use by another process.

Failed to empty PHASEINFO directory.

The solver failed to remove the contents of PHASEINFO directory. The files may be in use by another process.

Failed to empty PROBE directory.

The solver failed to remove the contents of PROBE directory. The files may be in use by another process.

Failed to empty MOTION directory.

The solver failed to remove the contents of MOTION directory. The files may be in use by another process.

Failed to empty STL directory.

The solver failed to remove the contents of UTM directory. The files may be in use by another process.

Failed to empty STL directory.

The solver failed to remove the contents of STL directory. The files may be in use by another process.

Failed to empty PVSTATE directory.

The solver failed to remove the contents of PVSTATE directory. The files may be in use by another process.

Failed to empty EXTRACT directory.

The solver failed to remove the contents of EXTRACT directory. The files may be in use by another process.

Failed to create OUTPUT directory.

The solver encountered an issue while creating the OUTPUT directory. The path may not be accessible. Retrying the simulation or changing the case path may resolve this issue. If this happens in a multi-node run, the filesystem topology might not have been determined correctly. In this case, the filesystem topology can be set manually by setting the parameter "filesys_topo" in "simulationParameters" to SHARED if all nodes share the same output filesystem or DISTRIBUTED if every node writes to a separate filesystem.

Failed to create PREVIEW directory.

The solver encountered an issue while creating the PREVIEW directory. The path may not be accessible. Retrying the simulation or changing the case path may resolve this issue. If this happens in a multi-node run, the filesystem topology might not have been determined correctly. In this case, the filesystem topology can be set manually by setting the parameter "filesys_topo" in "simulationParameters" to SHARED if all nodes share the same output filesystem or DISTRIBUTED if every node writes to a separate filesystem.

Failed to create RECON directory.

The solver encountered an issue while creating the RECON directory. The path may not be accessible. Retrying the simulation or changing the case path may resolve this issue. If this happens in a multi-node run, the filesystem topology might not have been determined correctly. In this case, the filesystem topology can be set manually by setting the parameter "filesys_topo" in "simulationParameters" to SHARED if all nodes share the same output filesystem or DISTRIBUTED if every node writes to a separate filesystem.

Failed to create LOG directory.

The solver encountered an issue while creating the LOG directory. The path may not be accessible. Retrying the simulation or changing the case path may resolve this issue. If this happens in a multi-node run, the filesystem topology might not have been determined correctly. In this case, the filesystem topology can be set manually by setting the parameter "filesys_topo" in "simulationParameters" to SHARED if all nodes share the same output filesystem or DISTRIBUTED if every node writes to a separate filesystem.

Failed to create PHASEINFO directory.

The solver encountered an issue while creating the PHASEINFO directory. The path may not be accessible. Retrying the simulation or changing the case path may resolve this issue. If this happens in a multi-node run, the filesystem topology might not have been determined correctly. In this case, the filesystem topology can be set manually by setting the parameter "filesys_topo" in "simulationParameters" to SHARED if all nodes share the same output filesystem or DISTRIBUTED if every node writes to a separate filesystem.

Failed to create PROBE directory.

The solver encountered an issue while creating the PROBE directory. The path may not be accessible. Retrying the simulation or changing the case path may resolve this issue. If this happens in a multi-node run, the filesystem topology might not have been determined correctly. In this case, the filesystem topology can be set manually by setting the parameter "filesys_topo" in "simulationParameters" to SHARED if all nodes share the same output filesystem or DISTRIBUTED if every node writes to a separate filesystem.

Failed to create MOTION directory.

The solver encountered an issue while creating the MOTION directory. The path may not be accessible. Retrying the simulation or changing the case path may resolve this issue. If this happens in a multi-node run, the correct filesystem topology might not have been determined correctly. In this case, the filesystem topology can be set manually by setting the parameter "filesys_topo" in "simulationParameters" to SHARED if all nodes share the same output filesystem or DISTRIBUTED if every node writes to a separate filesystem.

Failed to create UTM directory.

The solver encountered an issue while creating the UTM directory. The path may not be accessible. Retrying the simulation or changing the case path may resolve this issue. If this happens in a multi-node run, the correct filesystem topology might not have been determined correctly. In this case, the filesystem topology can be set manually by setting the parameter "filesys_topo" in "simulationParameters" to SHARED if all nodes share the same output filesystem or DISTRIBUTED if every node writes to a separate filesystem.

Failed to create STL directory.

The solver encountered an issue while creating the STL directory. The path may not be accessible. Retrying the simulation or changing the case path may resolve this issue. If this happens in a multi-node run, the correct filesystem topology might not have been determined correctly. In this case, the filesystem topology can be set manually by setting the parameter "filesys_topo" in "simulationParameters" to SHARED if all nodes share the same output filesystem or DISTRIBUTED if every node writes to a separate filesystem.

Failed to create PVSTATE directory.

The solver encountered an issue while creating the PVSTATE directory. The path may not be accessible. Retrying the simulation or changing the case path may resolve this issue. If this happens in a multi-node run, the filesystem topology might not have been determined correctly. In this case, the filesystem topology can be set manually by setting the parameter "filesys_topo" in "simulationParameters" to SHARED if all nodes share the same output filesystem or DISTRIBUTED if every node writes to a separate filesystem.

Failed to create EXTRACT directory.

The solver encountered an issue while creating the EXTRACT directory. The path may not be accessible. Retrying the simulation or changing the case path may resolve this issue. If this happens in a multi-node run, the filesystem topology might not have been determined correctly. In this case, the filesystem topology can be set manually by setting the parameter "filesys_topo" in "simulationParameters" to SHARED if all nodes share the same output filesystem or DISTRIBUTED if every node writes to a separate filesystem.

Failed to create output rank directories.

The solver encountered an issue while creating the rank# directory(ies) in OUTPUT directory. The path may not be accessible. Retrying the simulation or changing the case path may resolve this issue.

Failed to create preview rank directories.

The solver encountered an issue while creating the rank# directory(ies) in PREVIEW directory. The path may not be accessible. Retrying the simulation or changing the case path may resolve this issue.

Failed to create restart/continue rank directories.

The solver encountered an issue while creating the rank# directory(ies) in RECON directory. The path may not be accessible. Retrying the simulation or changing the case path may resolve this issue.

Cannot find or failed to open input archive S1.

The solver is not able to find or open the input archive file. Please check the path in your launch command and make sure the archive file is accessible.

Failed to open S1 of input archive S2.

The solver has encountered a problem when trying to access the contents of input archive file. The archive may be corrupt or inaccessible.

Encountered an error while reading S1 of input archive S2.

The solver has encountered a problem while reading the contents of input archive file. The archive may be corrupt or inaccessible.

Cannot find inputfile S1

The solver is not able to find/access the inputfile or copy the inputfile into "Used_inputfile.prtl". Please make sure both the inputfile and "Used_inputfile.prtl" are accessible to the solver.

Cannot find Inputfile S1

The solver is not able to access the input file containing the discretized geometry. Either the file does not exist or the path is incorrect.

Unexpected number of columns in the inputfile.

Each row of inputfile must contain 4 or 7 columns.

Unexpected number of columns in the inputfile.

Each row of inputfile must contain 4 or 7 columns.

Unexpected number of columns in the inputfile.

Each row of inputfile must contain 4 or 7 columns.

Problem opening the bodyforce file

The solver is not able to find the acceleration field file specified for "bodyforce" in "domain" section. Please make sure the file exists and/or the path to the file in cfg is correct.

Empty line in bodyforce file S1

The solver encountered an empty line while reading the acceleration field from "bodyforce" in "domain" section. Please remove the empty line from the file and try again. The file should be in plain ASCII with Unix like line endings (LF).

Problem reading the bodyforce file

The solver encountered a problem while reading the acceleration field from "bodyforce" in "domain" section. A likely reason is incorrect number of columns. Please make sure all rows have four columns. The file should be in plain ASCII with Unix like line endings (LF).

Problem opening the road path file S1.

The solver is not able to find the road path file specified for "frame_road_path_file_name" in "framesuite" section. Please make sure the file exists and/or the path to the file in cfg is correct.

Empty line in the road path file S1.

The solver encountered an empty line while reading the road path from "frame_road_path_file_name" in "framesuite" section. Please remove the empty line from the file and try again. The file should be in plain ASCII with Unix like line endings (LF).

Problem reading the road path file S1.

The solver encountered a problem while reading the road path from "frame_road_path_file_name" in "framesuite" section. A likely reason is incorrect number of columns. Please make sure all rows have four columns. The file should be in plain ASCII with Unix like line endings (LF).

Problem opening the road profile file S1.

The solver is not able to find the road profile file specified for "frame_road_profile_file_name" in "framesuite" section. Please make sure the file exists and/or the path to the file in cfg is correct.

Empty line in the road profile file S1.

The solver encountered an empty line while reading the road profile from "frame_road_profile_file_name" in "framesuite" section. Please remove the empty line from the file and try again. The file should be in plain ASCII with Unix like line endings (LF).

Problem reading the road profile file S1.

The solver encountered a problem while reading the road profile from "frame_road_profile_file_name" in "framesuite" section. A likely reason is incorrect number of columns. Please make sure all rows have four columns. The file should be in plain ASCII with Unix like line endings (LF).

Unable to access case directory S1

The solver encountered an issue while accessing the case directory during file system topology identification. The case directory having been deleted, being inaccessible or having other unknown file system issues may lead to this message.

Root path S1 is not a directory.

The path to the case directory points to a file instead. The reason is unknown.

Cannot write to case directory S1

The solver encountered an issue while writing to the case directory during file system topology identification. This may be due to inadequate permissions.

Cannot read from case directory S1

The solver encountered an issue while reading from the case directory during file system topology identification. This may be due to inadequate permissions.

Could not determine file system topology.

The solver was not able to determine the file system topology due to an unknown error. Please specify the file system topology explicitly through the cfg file.

File system topology is ambiguous. Only one file system for all nodes or one file system per node is supported.

The solver was not able to determine the file system topology. This error indicates that there were no clear patterns of file system accessibility. Only one shared file system for all nodes or one local file system per node are supported. If your file system meets either of these criteria, please specify the file system topology explicitly through the cfg file.

File system topology is ambiguous. Only one file system for all nodes or one file system per node is supported.

The solver was not able to determine the file system topology. This error indicates that there were no clear patterns of file system accessibility. Only one shared file system for all nodes or one local file system per node are supported. If your file system meets either of these criteria, please specify the file system topology explicitly through the cfg file.

Cannot find/open the time-velocity series file S1 for a PARALLELEPIPEDVEL impose region #1.

The solver is not able to find the time-velocity series file specified for "parallelepipedvel_tvs_file" in "imposeRegions" section. Please make sure the file exists and/or the path to the file in cfg is correct.

Empty line in time-velocity series file S1 for a PARALLELEPIPEDVEL impose region #1.

The solver encountered an empty line while reading the time-velocity series from "parallelepipedvel_tvs_file" in "imposeRegions" section. Please remove the empty line from the file and try again. The file should be in plain ASCII with Unix like line endings (LF).

Encountered a problem while reading time-velocity series file S1 for PARALLELEPIPEDVEL impose region #1.

The solver encountered a problem while reading the time-velocity series from "parallelepipedvel_tvs_file" in "imposeRegions" section. A likely reason is incorrect number of columns. Please make sure all rows have two columns. The file should be in plain ASCII with Unix like line endings (LF).

Cannot find/open the time-velocity series file S1 for CYLINDERVEL impose region #1.

The solver is not able to find the time-velocity series file specified for "cylindervel_tvs_file" in "imposeRegions" section. Please make sure the file exists and/or the path to the file in cfg is correct.

Empty line in time-velocity series file S1 for CYLINDERVEL impose region #1.

The solver encountered an empty line while reading the time-velocity series from "cylindervel_tvs_file" in "imposeRegions" section. Please remove the empty line from the file and try again. The file should be in plain ASCII with Unix like line endings (LF).

Encountered a problem while reading time-velocity series file S1 for CYLINDERVEL impose region #1.

The solver encountered a problem while reading the time-velocity series from "cylindervel_tvs_file" in "imposeRegions" section. A likely reason is incorrect number of columns. Please make sure all rows have two columns. The file should be in plain ASCII with Unix like line endings (LF).

Cannot find/open the time-acceleration series file S1 for a PARALLELEPIPEDACC impose region #1.

The solver is not able to find the time-acceleration series file specified for "parallelepipedacc_tas_file" in "imposeRegions" section. Please make sure the file exists and/or the path to the file in cfg is correct.

Empty line in time-acceleration series file S1 for a PARALLELEPIPEDACC impose region #1.

The solver encountered an empty line while reading the time-acceleration series from "parallelepipedacc_tas_file" in "imposeRegions" section. Please remove the empty line from the file and try again. The file should be in plain ASCII with Unix like line endings (LF).

Encountered a problem while reading time-acceleration series file S1 for PARALLELEPIPEDACC impose region #1.

The solver encountered a problem while reading the time-acceleration series from "parallelepipedacc_tas_file" in "imposeRegions" section. A likely reason is incorrect number of columns. Please make sure all rows have two columns. The file should be in plain ASCII with Unix like line endings (LF).

Cannot find/open the time-acceleration series file S1 for a CYLINDERACC impose region #1.

The solver is not able to find the time-acceleration series file specified for "cylinderacc_tas_file" in "imposeRegions" section. Please make sure the file exists and/or the path to the file in cfg is correct.

Empty line in time-acceleration series file S1 for a CYLINDERACC impose region #1.

The solver encountered an empty line while reading the time-acceleration series from "cylinderacc_tas_file" in "imposeRegions" section. Please remove the empty line from the file and try again. The file should be in plain ASCII with Unix like line endings (LF).

Encountered a problem while reading time-acceleration series file S1 for CYLINDERACC impose region #1.

The solver encountered a problem while reading the time-acceleration series from "cylinderacc_tas_file" in "imposeRegions" section. A likely reason is incorrect number of columns. Please make sure all rows have two columns. The file should be in plain ASCII with Unix like line endings (LF).

Cannot find/open the time-temperature series file S1 for a PARALLELEPIPEDTEMP impose region #1.

The solver is not able to find the time-temperature series file specified for "parallelepipedtemp_tts_file" in "imposeRegions" section. Please make sure the file exists and/or the path to the file in cfg is correct.

Empty line in time-temperature series file S1 for a PARALLELEPIPEDTEMP impose region #1.

The solver encountered an empty line while reading the time-temperature series from "parallelepipedtemp_tts_file" in "imposeRegions" section. Please remove the empty line from the file and try again. The file should be in plain ASCII with Unix like line endings (LF).

Encountered a problem while reading time-temperature series file S1 for PARALLELEPIPEDTEMP impose region #1.

The solver encountered a problem while reading the time-temperature series from "parallelepipedtemp_tts_file" in "imposeRegions" section. A likely reason is incorrect number of columns. Please make sure all rows have two columns. The file should be in plain ASCII with Unix like line endings (LF).

Cannot find/open the time-temperature series file S1 for a CYLINDERTEMP impose region #1.

The solver is not able to find the time-temperature series file specified for "cylindertemp_tts_file" in "imposeRegions" section. Please make sure the file exists and/or the path to the file in cfg is correct.

Empty line in time-temperature series file S1 for a CYLINDERTEMP impose region #1.

The solver encountered an empty line while reading the time-temperature series from "cylindertemp_tts_file" in "imposeRegions" section. Please remove the empty line from the file and try again. The file should be in plain ASCII with Unix like line endings (LF).

Encountered a problem while reading time-temperature series file S1 for CYLINDERTEMP impose region #1.

The solver encountered a problem while reading the time-temperature series from "cylindertemp_tts_file" in "imposeRegions" section. A likely reason is incorrect number of columns. Please make sure all rows have two columns. The file should be in plain ASCII with Unix like line endings (LF).

Cannot find/open the stencil file S1 for inlet region #1.

The solver is not able to find the inlet region stencil file specified for "inletregion_stf_file" in "inletregions" section. Please make sure the file exists and/or the path to the file in cfg is correct.

Empty line in stencil file S1 for inlet region #1.

The solver encountered an empty line while reading the inlet region stencil from "inletregion_stf_file" in "inletreginos" section. Please remove the empty line from the file and try again. The file should be in plain ASCII with Unix like line endings (LF).

Encountered a problem while reading stencil file S1 for inlet region #1.

The solver encountered a problem while reading the inlet reigon stencil from "inletregion_stf_file" in "inletreginos" section. A likely reason is incorrect number of columns. Please make sure all rows of single-phase stencil file have 3 columns and all rows of multi-phase stencil files have 4 columns. The file should be in plain ASCII with Unix like line endings (LF).

Not all phases mentioned in "inletregion_stf_phaselist" for inlet region #1 were found in file S1.

A 4-column (multi-phase) inlet region stencil files must include all phases mentioned in "inletregion_stf_phaselist".

Encountered a negative state magnitude while reading time-state series file S1 for inlet region #1.

The solver encountered a negative number while reading the time-state series from "inletregion_tss_file" in "inletregions" section. All state magnitudes must be non-negative. Please change "inletregion_nrm" to change state direction.

Cannot find/open the time-state series file S1 for inlet region #1.

The solver is not able to find the time-state series file specified for "inletregion_tss_file" in "inletregions" section. Please make sure the file exists and/or the path to the file in cfg is correct.

Empty line in time-state series file S1 for inlet region #1.

The solver encountered an empty line while reading the time-state series from "inletregion_tss_file" in "inletregions" section. Please remove the empty line from the file and try again. The file should be in plain ASCII with Unix like line endings (LF).

Encountered a problem while reading time-state series file S1 for inlet region #1.

The solver encountered a problem while reading the time-state series from "inletregion_tss_file" in "inletregions" section. A likely reason is incorrect number of columns. Please make sure all rows have two columns. The file should be in plain ASCII with Unix like line endings (LF).

Cannot find prescribed motion file S1

The solver is not able to find the prescribed motion file specified for "motion_type" in "motions" section. Please make sure the file exists and/or the path to the file in cfg is correct.

Encountered an empty line while reading the header of prescribed motion file S1

The solver encountered an empty line while reading the header of the prescribed motion file. Please remove the empty line from the file and try again. The file should be in plain ASCII with Unix like line endings (LF).

Encountered a problem while reading the header of prescribed motion file S1

The solver encountered a problem while reading the header of the prescribed motion file. A likely reason is the incorrect number of columns. The file should be in plain ASCII with Unix like line endings (LF).

Encountered an empty line while reading prescribed motion file S1

The solver encountered an empty line while reading the prescribed motion file. Please remove the empty line from the file and try again. The file should be in plain ASCII with Unix like line endings (LF).

Encountered a problem while reading the prescribed motion file S1

The solver encountered a problem while reading the prescribed motion file. A likely reason is the incorrect number of columns. Please make sure that all lines have 8 columns for axis-angle mode (isOrientation true) and 7 columns for angular velocity mode (isOrientation false). The file should be in plain ASCII with Unix like line endings (LF).

Cannot find/open the road path file S1 for motion #1.

The solver is not able to find the road path file specified for "dr1dof_rd_pth_file" in "motions" section. Please make sure the file exists and/or the path to the file in cfg is correct.

Empty line in road path file S1 for motion #1.

The solver encountered an empty line while reading the road path from "dr1dof_rd_pth_file" in "motions" section. Please remove the empty line from the file and try again. The file should be in plain ASCII with Unix like line endings (LF).

Encountered a problem while reading road path file S1 for motion #1.

The solver encountered a problem while reading the road path from "dr1dof_rd_pth_file" in "motions" section. A likely reason is incorrect number of columns. Please make sure all rows have two columns. The file should be in plain ASCII with Unix like line endings (LF).

Cannot find/open the preset time dependent linear velocity file (prbcon_linvel_f_c) S1 for passive rigid body motion #1.

The solver is not able to find the preset time dependent linear velocity file specified for "prbcon_linvel_f_c" in "motions" section for a passive rigid body. Please make sure the "prbcon_linvel_f_c" keyword is present, the specified file name/path is correct and the file pointed to exists.

Empty line in preset time dependent linear velocity file (prbcon_linvel_f_c) S1 for passive rigid body motion #1.

The solver encountered an empty line while reading the preset time dependent linear velocity from "prbcon_linvel_f_c" in "motions" section for a passive rigid body. Please remove the empty line from the file and try again. The file should be in plain ASCII with Unix like line endings (LF).

Encountered a problem while reading time dependent linear velocity file (prbcon_linvel_f_c) S1 for passive rigid body motion #1.

The solver encountered a problem while reading the time dependent linear velocity from "prbcon_linvel_f_c" in "motions" section for a passive rigid body. A likely reason is incorrect number of columns. Please make sure all rows have four columns. The file should be in plain ASCII with Unix like line endings (LF).

Cannot find/open the preset time dependent angular velocity file (prbcon_angvel_f_c) S1 for passive rigid body motion #1.

The solver is not able to find the preset time dependent angular velocity file specified for "prbcon_angvel_f_c" in "motions" section for a passive rigid body. Please make sure the "prbcon_angvel_f_c" keyword is present, the specified file name/path is correct and the file pointed to exists.

Empty line in preset time dependent angular velocity file (prbcon_angvel_f_c) S1 for passive rigid body motion #1.

The solver encountered an empty line while reading the preset time dependent angular velocity from "prbcon_angvel_f_c" in "motions" section for a passive rigid body. Please remove the empty line from the file and try again. The file should be in plain ASCII with Unix like line endings (LF).

Encountered a problem while reading time dependent angular velocity file (prbcon_angvel_f_c) S1 for passive rigid body motion #1.

The solver encountered a problem while reading the time dependent angular velocity from "prbcon_angvel_f_c" in "motions" section for a passive rigid body. A likely reason is incorrect number of columns. Please make sure all rows have four columns. The file should be in plain ASCII with Unix like line endings (LF).

Encountered a negative state magnitude while reading time-state series file S1 for outlet region #1.

The solver encountered a negative number while reading the velocity from time-state series file "outletregion_tss_file" in "outletregions" section. All velocity magnitudes must be non-negative. Please change "outletregion_nrm" to change velocity direction.

Cannot find/open the time-state series file S1 for outlet region #1.

The solver is not able to find the time-state series file specified for "outletregion_tss_file" in "outletregions" section. Please make sure the file exists and/or the path to the file in cfg is correct.

Empty line in time-state series file S1 for outlet region #1.

The solver encountered an empty line while reading the time-state series from "outletregion_tss_file" in "outletregions" section. Please remove the empty line from the file and try again. The file should be in plain ASCII with Unix like line endings (LF).

Encountered a problem while reading time-state series file S1 for outlet region #1.

The solver encountered a problem while reading the time-state series from "outletregion_tss_file" in "outletregions" section. A likely reason is incorrect number of columns. Please make sure all rows have two columns. The file should be in plain ASCII with Unix like line endings (LF).

The probe points file S1 specified for probe S2 contains less than two points.

A flowrate probe requires at least two points to function. This error may point to possible errors in probe points file specified for "probe_points_file" in "probes" section or typographical errors in the cfg file.

Cannot find/open the probe points file S1 specified for probe S2.

The solver is not able to find the probe points file specified for "probe_points_file" in "probes" section. Please make sure the file exists and/or the path to the file in cfg is correct.

Empty line in the probe points file S1 specified for probe S2.

The solver encountered an empty line while reading the probe points from "probe_points_file" in "probes" section. Please remove the empty line from the file and try again. The file should be in plain ASCII with Unix like line endings (LF).

Encountered a problem while reading the probe points file S1 specified for probe S2.

The solver encountered a problem while reading the probe points file from "probe_points_file" in "probes" section. A likely reason is incorrect number of columns. Please make sure all rows have three columns. The file should be in plain ASCII with Unix like line endings (LF).

Bounding Box needs to be read from the restart/continue (recon) file.

A restart/continue (recon) run must use the bounding box values stored in the recon file.

Encountered a problem while reading the inputfile (for BB).

This error suggests that there has been a problem in the input discretized geometry file. This may be due to wrong number of columns or empty lines in the file. The file should be in plain ASCII with Unix like line endings (LF). Exporting the discretized geometry again may resolve this problem.

Domain Dimensions need to be read from the restart/continue (recon) file.

A restart/continue (recon) run must use the domain dimension values stored in the recon file.

Could not determine the latest restart/continue (recon) file. Please use \"restart_from_step\" keyword to specify the timestep explicitly.

The solver was not able to determine the latest restart/continue (recon) file available. At least one recon file must be present. The error may be due to wrong "restart_from_dir", "output_data_dir" or a change in the cfg file name that leads the solver to search a directory without any recon files. The recon timesteps available for a specific simulation are listed in the "restart.txt" file.

Unable to find restart/continue (recon) file S1

The solver is unable to find or access the restart/continue (recon) file. Please make sure the file exists. This may be due to typographical errors in defining "restart_from_dir" or "restart_from_step" keywords.

Incompatible restart/continue (recon) file version (supplied/required): #1/#2

The restart/continue (recon) file version is not compatible with the solver version. The supplied recon file version and required recon file version by the solver are given in the error message.

Encountered a problem while reading restart/continue (recon) file S1

The solver encountered a problem while reading a restart/continue (recon) file.

Unable to find restart/continue (recon) file S1

The solver is unable to find or access the restart/continue (recon) file. Please make sure the file exists. This may be due to typographical errors in defining "restart_from_dir" or "restart_from_step" keywords.

Problem opening the particle output times file S1

The solver is not able to find the particle output times file specified for "t_output_file" in "simulationParameters" section. Please make sure the file exists and/or the path to the file in cfg is correct.

Empty line in particle output times file S1

The solver encountered an empty line while reading the particle output times from "t_output_file" in "simulationParameters" section. Please remove the empty line from the file and try again. The file should be in plain ASCII with Unix like line endings (LF).

Problem reading the particle output times file S1

The solver encountered a problem while reading the particle output times from "t_output_file" in "simulationParameters" section. Please make sure the file contains exactly one number per line. The file should be in plain ASCII with Unix like line endings (LF).

Problem opening the restart output times file S1

The solver is not able to find the restart output times file specified for "t_output_restart_file" in "simulationParameters" section. Please make sure the file exists and/or the path to the file in cfg is correct.

Empty line in restart output times file S1

The solver encountered an empty line while reading the restart output times from "t_output_restart_file" in "simulationParameters" section. Please remove the empty line from the file and try again. The file should be in plain ASCII with Unix like line endings (LF).

Problem reading the restart output times file S1

The solver encountered a problem while reading the restart output times from "t_output_restart_file" in "simulationParameters" section. Please make sure the file contains exactly one number per line. The file should be in plain ASCII with Unix like line endings (LF).

Cannot find/open the stl file S1 for extractor S2.

The solver is not able to find the stl file specified for "extractor_stlfile" in "extractors" section. Please make sure the file exists and/or the path to the file in cfg is correct.

Encountered a problem while reading the input geometry file.

This error suggests that there has been a problem in the input discretized geometry file. This may be due to wrong number of columns or empty lines in the file. The file should be in plain ASCII with Unix like line endings (LF). Exporting the discretized geometry again may resolve this problem.

Encountered a problem with the (restart/continue) recon file (nonexistent or unreadable) S1

The solver is not able to access a restart/continue (recon) file. The file may not exist or the path is incorrect. Please make sure the chosen timestep to restart/continue the simulation from corresponds to an available recon file.

Encountered a problem while reading restart/continue (recon) file S1

The solver is not able to read a restart/continue (recon) file. The file may be corrupt or in an incorrect format.

Failed to create EXTRACT sub directory for vtp output of extractor S1.

The solver encountered an issue while creating a subdirectory under EXTRACT directory. The path may not be accessible. Retrying the simulation or changing the case path may resolve this issue. If this happens in a multi-node run, the filesystem topology might not have been determined correctly. In this case, the filesystem topology can be set manually by setting the parameter "filesys_topo" in "simulationParameters" to SHARED if all nodes share the same output filesystem or DISTRIBUTED if every node writes to a separate filesystem.

Failed to create EXTRACT sub directory for synchronized output S1.

The solver encountered an issue while creating a subdirectory under EXTRACT directory. The path may not be accessible. Retrying the simulation or changing the case path may resolve this issue. If this happens in a multi-node run, the filesystem topology might not have been determined correctly. In this case, the filesystem topology can be set manually by setting the parameter "filesys_topo" in "simulationParameters" to SHARED if all nodes share the same output filesystem or DISTRIBUTED if every node writes to a separate filesystem.

Failed to create EXTRACT sub directory for txt output of extractor S1.

The solver encountered an issue while creating a subdirectory under EXTRACT directory. The path may not be accessible. Retrying the simulation or changing the case path may resolve this issue. If this happens in a multi-node run, the filesystem topology might not have been determined correctly. In this case, the filesystem topology can be set manually by setting the parameter "filesys_topo" in "simulationParameters" to SHARED if all nodes share the same output filesystem or DISTRIBUTED if every node writes to a separate filesystem.

Failed to create EXTRACT sub directory for info output of extractor S1.

The solver encountered an issue while creating a subdirectory under EXTRACT directory. The path may not be accessible. Retrying the simulation or changing the case path may resolve this issue. If this happens in a multi-node run, the filesystem topology might not have been determined correctly. In this case, the filesystem topology can be set manually by setting the parameter "filesys_topo" in "simulationParameters" to SHARED if all nodes share the same output filesystem or DISTRIBUTED if every node writes to a separate filesystem.

Failed to create EXTRACT sub directory for synchronized info output of extractor S1.

The solver encountered an issue while creating a subdirectory under EXTRACT directory. The path may not be accessible. Retrying the simulation or changing the case path may resolve this issue. If this happens in a multi-node run, the filesystem topology might not have been determined correctly. In this case, the filesystem topology can be set manually by setting the parameter "filesys_topo" in "simulationParameters" to SHARED if all nodes share the same output filesystem or DISTRIBUTED if every node writes to a separate filesystem.

Encountered a problem while opening stl file S1 for extractor S2.

The solver encountered a problem while opening the stl file specified for "extractor_stlfile" in "extractors" section. The file name or path may be wrong or the file may not exist, lack required permissions, be corrupt or be inaccessible due to other reasons.

Encountered a problem while reading stl file S1 for extractor S2.

The solver encountered a problem while reading the stl file from "extractor_stlfile" in "extractors" section. The file may be corrupt, contain ill formated data, have become inaccessible during the read operation or be unreadable due to other reasons.