Skip to content

Releases: isoverse/isoreader2

Release of isosolfs version 0.1.0

Choose a tag to compare

@sebkopf sebkopf released this 23 Feb 05:39

UPDATE: a new release of isosolf runs cross-platform on Windows, OS X, and Linux

Implements first version of SolFS extractor for Qtegra notebooks. Due to the dependencies of the SolFS library, this only works on Windows. The attached executable is compiled for x64 architectures and should run on all modern Windows operating systems. To use, copy the isosolfs.exe into a directory with .imexp notebook files and extract them with the following command:

Usage

.\isosolfs.exe "<path>" [--version] [--help] [--list] [--extract] [--create]

For example (assuming testfile.imexp is in the current directory):

  • to get the isosolfs version: .\isosolfs.exe --version
  • to get the usage information: .\isosolfs.exe --help
  • to get just info about a test file: .\isosolfs.exe testfile.imexp
  • to list all contents of the test file: .\isosolfs.exe testfile.imexp --list
  • to extract all contents of the test file: .\isosolfs.exe testfile.imexp --extract

Corrupted files

Sometimes imexp notebooks get corrupted. Depending on what the problem is, isosolfs can help fix it. If you extract using e.g. .\isosolfs.exe testfile.imexp --extract and get a warning like this:

WARNING: notebook has 1 problematic folder(s) that cannot be accessed:
 20260226-001349-777\Entry_8dc7cd5a-fb74-4683-b591-b64d6f859eb1 - SolFS Error: Storage file corrupted

It means that the analysis stored in Entry_8dc7cd5a-fb74-4683-b591-b64d6f859eb1 got corrupted. The extracted notebook (here in testfile) now has all contents of the notebook except the corrupted data, which cannot be recovered. Unfortunately, just recreating an imexp notebook from the extracted data without the corrupted folders does not fix the issue because other files reference this analysis as well (e.g. entries in the guids subfolder). As these are all binary files, it is not straight-forward to excise all references to the corrupted analysis. However, analyses stored in other analytical sessions in the notebook can usually be recovered pretty easily. To do so, try this:

  • make a backup of your original imexp notebook (just in case)
  • delete the entire session folder from the extracted notebook that the corrupted analysis was in (in this example, that's 20260226-001349-777)
  • remove the session record (example here: 20260226-001349-777) from the entries.txt file in the extracted notebook (this one is actually just plaintext) and save the changes
  • change the entry in the latest.txt file to another one of the sessions listed in entries.txt and save the changes
  • use the create command from isosolfs to make a new imexp notebook from the cleaned up folder: .\isosolfs.exe testfile --create
  • hope that worked! otherwise (or anyways ;), just use isoreader2 instead to process your data