Error messages
Here you’ll find platform error messages with Cause that describes why you get this error message and Remedy that explains how you can solve the error message.
Dataset errors
The value in one cell (column; ${column}, row; ${row}) exceeds the max size (${limit}). Make the value shorter.
Cause /
This Message in GUI triggers the first time the value in one cell exceeds the limit for a cell value.
Note that you get this error for the first cell where the value is too large. There might be other cells in the file that have cell values that exceed the limit.
Example:
If a cell includes text from a book, the text can easily become too large.
Remedy /
Shorten the text in the cell before uploading the file.
It’s a good idea to take a look at all cells in the file simultaneously to make sure there aren’t other cells with too large values.
The file includes more columns than the max limit (${maxNumberOfColumnsAllowed}). Cut down on the columns and upload the file again.
Cause /
The number of columns in the file exceeds the max number of columns allowed.
This can happen if the platform has problems interpreting linebreak in the file, thus reading the whole file as one long row. Then the number of columns can be significant.
We support Microsoft Windows (CR LF, \r\n) and modern Linux/Unix like (LF, \n) systems.
We do sometimes have problems with older versions of OSX (especially older versions of Microsoft Excel) that only produce (CR, \r).
Remedy /
There are several ways to solve such problems by opening up the CSV in a text editor (such as Visual Studio Code) and just save it again. This will usually change the line endings to compatible ones.
There are several command-line tools to solve this problem too, such as dos2unix etc.
We failed to parse your file. Try again, and if it fails, contact support@peltarion.com.
Cause /
We failed to parse your file for some reason.
Remedy /
-
Try again to see if the error remains.
-
If this doesn’t help, make sure that the dataset fulfills our requirements.
-
As a last resort, feel free to contact support@peltarion.com.
We failed to read an image within the ZIP file. Make sure all images follow our requirements.
Cause /
We could not parse an image within the ZIP file. This may happen for many reasons.
Example:
The image header says that the image is a png, but it is actually another format, for example, jpg. When the platform tries to parse the image, it fails.
We failed to read an image within the ZIP file. Try to upload the file again.
Cause /
We could not read an image in the ZIP file that you tried to upload. This can happen for many different reasons.
Remedy /
Try to upload the file again. If the problem persists, please contact support.
A numpy file contain ${actualType} with width ${actualWidth bits. We only support ${allowedType} ${allowedWidth} with width ${allowedType} bits. Update the file.
Cause /
A NumPy file contains the wrong width of bits and/or the wrong encoding type.
Example:
The platform supports float-32, but the uploaded NumPy is a float-16.
Remedy /
Update the NumPy file with the correct type and width. Then upload the file again.
The platform only supports little-endian ('<') byte-order. The file has the '${endianness}' byte-order. Update the file and upload again.
Cause /
The platform only supports little-endian ('<') byte-order. The file has the wrong byte-order.
Column major order (Fortran order) is not supported. Change the order to row major order and upload again.
Cause /
The platform supports row major order when storing a matrix. If the file is stored in column major order it won’t work.
Remedy /
Change the order to row major and upload the file again.
The files have a different number of rows. The row count needs to match. Make sure the files have the same number of rows before you upload them.
Cause /
When you add more files, you add more columns to your dataset. If they have a mismatch in the number of rows, you will get rows with missing values that the platform doesn’t support. You can’t train a model with data that don’t exist.
Currently, it is not possible to add more rows to the dataset by importing another file.
Remedy /
Check your files before you upload them to the platform and make sure they have the same amount of rows.
Then upload the files again.
The file has the wrong encoding. The platform only supports ${expectedCharset} encoding.
Cause /
The platform only supports UTF-8 encoding. You get this error when you try to upload a file with another encoding.
Remedy /
Save your csv files using UTF-8 encoding.
There are fewer columns (${numberOfColumnsInSample} in row ${row} than expected (${numberOfColumnsInHeader}). Make sure all rows have as many columns as the header row.
Cause /
The platform expects that there are as many columns in each row as in the header row.
If one row in the dataset has fewer columns, the platform cannot use the dataset.
The error is shown on the first row this happens but there might be more rows that have too few columns.
Remedy /
Make sure all rows have the same number of columns as the header row before uploading the file.
There are more columns (${numberOfColumnsInSample}) in row ${row} than expected (${numberOfColumnsInHeader}). Make sure all rows have as many columns as the header row.
Cause /
The platform expects that there are as many columns in each row as in the header row.
If one row in the dataset has more columns, the platform cannot use the dataset.
The error is shown on the first row this happens but there might be more that have too many columns.
Remedy /
Make sure all rows have the same number of columns as the header row before uploading the file.