Description
Occasionally, a particular raw dataset may trigger errors when included in a bulk import, while other files import correctly. This can indicate corruption in the vendor file or edge‑case conditions in the import filter.
Solution
- Isolate the problematic file:
- From your bulk set, try importing half the files.
- If the error occurs, narrow further until you find the specific file that consistently fails.
- Once identified, attempt to:
- Import that file alone, using the same settings.
- Open the file in the original vendor software to check for warnings or corruption.
- If the vendor software also fails or shows warnings:
- Treat the raw file as corrupted.
- Re‑acquire the data if possible.
- If vendor software opens the file but Spectrus fails:
- Note instrument type, software version, and specific file path.
- Test with the latest Spectrus version to see if the issue has been resolved in a newer import filter.
- For persistent, reproducible issues in a supported vendor format:
- Save an anonymized copy of the dataset if internal investigation is required.
- Log the problem with sufficient details (instrument, vendor software version, approximate file size, Spectrus version, and steps taken).
- While the specific file is under investigation:
- Exclude it from bulk imports to avoid halting routine processing of other datasets.
Comments
0 comments
Article is closed for comments.