Filesystem Errors
This page contains information related to the various errors that can occur due to accessing the filesystem. Many of these issues may relate to the fact that MetriCal is often run inside of a Docker container. As such, be sure to check that the specific path related to the error is correctly mounted as a volume inside of MetriCal.
Error Codes
cal-io-001
🔍 Failed to locate any file at the provided path.
🔧 If you are operating MetriCal in a Docker instance, make sure you are using the mounted Docker
work directory, not your $HOME or local paths.
cal-io-002
🔍 Failed to memory map the provided data set.
🔧 This usually would fail if you do not have read permissions on the file in question (usually an MCAP file).
cal-io-003
🔍 The MCAP file provided could not be read.
🔧 Usually this indicates that while the file path looks like an MCAP file, the file itself does not conform to the MCAP specification (see https://mcap.dev/spec), or is corrupt in some way.
cal-io-004
🔍 The ROSbag file provided could not be read.
🔧 Similar to cal-io-003, the file path appears as a ROS 1 Bag v2.0, but does not conform to the ROS bag specification or is corrupt in some way.
cal-io-005
🔍 The provided path, when read, was not recognized as a valid plex.
🔧 The file that was provided was not recognized as a valid plex. See our schemata for the correct JSON Schema for plex files.
cal-io-006
🔍 The provided path, when read, was not recognized as a valid object space.
🔧 The file that was provided was not recognized as a valid object-space. See our schemata for the correct JSON Schema for object-space files.
cal-io-007
🔍 The provided pipeline file is malformed.
🔧 If you need help structuring your pipeline JSON, log in debug mode (-v). The JSON for the current mode will print to the console.
cal-io-008
🔍 The seed file provided could not be parsed as either a plex, results file, or URDF.
🔧 The file that was provided was not recognized as a valid plex, MetriCal results file, or ROS URDF. See our schemata for the correct JSON Schema for plex and result files, and check the ROS docs for whether or not you have a valid URDF.
cal-io-009
🔍 Failed to read any component folders in the data set.
🔧 The provided folders dataset did not contain any folders that match component names in the plex.
cal-io-010
🔍 Failed to interpret any filenames in any folders as timestamps.
🔧 The provided folders dataset had sub-directories that corresponded to components in the plex, but could not find any files in these sub-directories whose file names were valid timestamps.
cal-io-011
🔍 Failed to serialize a struct when reading in a file.
🔧 If this is a JSON file, make sure that you're not missing any commas. MetriCal can accept JSON with comments, so don't feel the need to modify your JSON heavily.
cal-io-012
🔍 Failed to serialize data as JSON.
🔧 This error is unrecoverable. Please submit a query to support@tangramvision.com with details of how you triggered this error.
cal-io-013
🔍 Failed to serialize tabular calibration as message pack.
🔧 This error is unrecoverable. Please submit a query to support@tangramvision.com with details of how you triggered this error.
cal-io-014
🔍 Failed to write file at path.
🔧 This error can often occur due to permissions errors in the path being written. Double check that your user has permission (and space left on the device) to write the file.
cal-io-015
🔍 The cached detections read in for this dataset did not match the component UUIDs in this plex.
🔧 This occurs when a plex has been changed or modified after detections have been cached for a particular data set. You can either verify that the UUIDs match the previous plex, or remove the cached detections and run MetriCal on the data anew.
cal-io-016
🔍 Failed to convert Plex to URDF.
🔧 This error is unrecoverable. Please submit a query to support@tangramvision.com with details of how you triggered this error.
cal-io-017
🔍 Failed to read metadata for file at a given path.
🔧 This error can occur for a number of reasons: either because the path is wrong, the inode for the file has been removed while querying for it, or because of some other block-device level fault in the system. Contact support@tangramvision.com if this error persists.
cal-io-018
🔍 Some other filesystem related error has occurred.
🔧 Contact support@tangramvision.com if this error persists.