Silo
Silo copied to clipboard
ndims member of ucdmesh/var objects handled incorrectly
cqid: VisIt00009009cqsubmitter: Mark Millercqsubmitdate: 01/22/10 Silo does a bunch of stuff behind the scenes 'remembering' metadata from mesh calls to attach it to succeeding var calls; 'ndims' of a ucdmesh is an example. And, it gets it wrong and its value can change based on order of calls to silo. This can lead to false alarams for apps codes regression tests when diffing files as 'ndims' changes value solely because of a change in order of ops. In addition, I don't even think Silo is handling 'ndims' correctly nor is VisIt even using it on ucdvar objects.
-----------------------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: 329 Status: Pending Project: VisIt Tracker: Bug Priority: Normal Subject: ndims member of ucdmesh/var objects handled incorrectly Assigned to: - Category: - Target version: - Author: Mark Miller Start: Due date: % Done: 0% Estimated time: Created: 08/04/2010 01:26 pm Updated: 12/05/2013 01:33 pm Likelihood: 3 - Occasional Severity: 3 - Major Irritation Found in version: 4.7.2 Impact: Expected Use: OS: All Support Group: DOE/ASC Description: cqid: VisIt00009009cqsubmitter: Mark Millercqsubmitdate: 01/22/10 Silo does a bunch of stuff behind the scenes 'remembering' metadata from mesh calls to attach it to succeeding var calls; 'ndims' of a ucdmesh is an example. And, it gets it wrong and its value can change based on order of calls to silo. This can lead to false alarams for apps codes regression tests when diffing files as 'ndims' changes value solely because of a change in order of ops. In addition, I don't even think Silo is handling 'ndims' correctly nor is VisIt even using it on ucdvar objects.
Comments: The ndims members of various Silo DBxxxvar objects seems unnecessary and poorly handled in the drivers relying upon previous calls to DBPutxxxmesh to set it. Nonetheless, VisIt plugin does not appear to ever use the 'ndims' member of a DBxxxvar object.