Silo is compressing datasets that it shouldn't (matnos array)

Nobody has claimed this yet.

Olivier Cessenat ran into this problem. Silo library appears to be trying to compress datasets it explicitly should NOT (at leaest it is designed that way). My first glance at the code is that it is NOT honoring the 'flags=0' when setting up compression in db_hdf5_set_compression. An attached c code demonstrates the problem.

-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. As such, not all
information was able to be captured in the transition. Below is
a complete record of the original redmine ticket.

Ticket number: 460
Status: New
Project: VisIt
Tracker: Bug
Priority: Normal
Subject: Silo is compressing datasets that it shouldn't (matnos array)
Assigned to: -
Category: -
Target version: -
Author: Mark Miller
Start: 11/01/2010
Due date:
% Done: 0%
Estimated time:
Created: 11/01/2010 08:04 pm
Updated:
Likelihood: 2 - Rare
Severity: 2 - Minor Irritation
Found in version: trunk
Impact:
Expected Use:
OS: All
Support Group: Any
Description:
Olivier Cessenat ran into this problem. Silo library appears to be trying to compress datasets it explicitly should NOT (at leaest it is designed that way). My first glance at the code is that it is NOT honoring the 'flags=0' when setting up compression in db_hdf5_set_compression. An attached c code demonstrates the problem.

Comments:

Start in db_hdf5_set_compression and inspect how a flags=0 argument is handled when configuring dataset compression. Reproduce the behavior with the attached C example, then verify that datasets such as the matnos array are not compressed when compression is explicitly disabled.

Written by the indexing model from the issue text.