2016.01.25 18:21 "[Tiff] checkit_tiff, fixit_tiff - question about memmapped I/O, and invitation for quality checks", by Andreas Romeyke
Because we need some validation and repair tools for TIFFs by reasons of digital preservation, we developed
- fixit_tiff to repair broken baseline TIFFs (see https://github.com/SLUB-digitalpreservation/fixit_tiff)
- checkit_tiff to validate baseline TIFFs against fine granular rules (see https://github.com/SLUB-digitalpreservation/checkit_tiff)
To ensure that we does not have (a lot of) bugs included, we invite you to test both tools and verify stability of checkit_tiff against your TIFF collection.
Additional I have a question about the flag "rm"/"rM" of the TIFFOpen() function. I am right, that the "rM" uses memmapped I/O? But with my tests, it does not differ in speed with "rm"-mode. Could you explain, how it works in detail?
Thanks in advance.
Mit freundlichen Grüßen
With best regards,
team member "long-term preservation"
Saxon State- and University Library Dresden (SLUB)
Department 2 (IT), Division 2.3 (infrastructure and digital long-term preservation)
Zellescher Weg 18 | 01069 Dresden
phone: +49 351 4677 216
http://www.slub-dresden.de/ | @slubdresden