llnl / llnl/Silo

ensure silo library handles 64 bit integers correctly

Open
#59 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
45
Forks
27
Avg merge
12h 34m
Merged PRs (30d)
4

Description

cqid: VisIt00008819cqsubmitter: Mark Millercqsubmitdate: 12/01/08 We need to make sure Silo will handle DB_INTEGER data that is 64 bit integers. More precisely, if sizeof(int) returns 8, we need to make sure Silo will read/write that correctly via HDF5 driver. Also, resole what DB_LONG versus DB_INTEGER means in this context.

-----------------------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: 327
Status: Pending
Project: VisIt
Tracker: Feature
Priority: Normal
Subject: ensure silo library handles 64 bit integers correctly
Assigned to: -
Category: -
Target version: -
Author: Mark Miller
Start:
Due date:
% Done: 0%
Estimated time:
Created: 08/04/2010 01:26 pm
Updated:
Likelihood:
Severity:
Found in version:
Impact: 5 - Very High
Expected Use: 2 - Rare
OS: All
Support Group: DOE/ASC
Description:
cqid: VisIt00008819cqsubmitter: Mark Millercqsubmitdate: 12/01/08 We need to make sure Silo will handle DB_INTEGER data that is 64 bit integers. More precisely, if sizeof(int) returns 8, we need to make sure Silo will read/write that correctly via HDF5 driver. Also, resole what DB_LONG versus DB_INTEGER means in this context.

Comments:

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating Silo's definitions and handling for DB_INTEGER and DB_LONG, then trace the HDF5 driver's integer read/write paths. Determine the intended distinction between the two types and verify behavior when sizeof(int) is 8. Done means 64-bit DB_INTEGER data is read and written correctly through HDF5 with the type semantics documented by the implementation or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
databases
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.