Move stringtodriver utility used in tests to main silo library
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 45
- Forks
- 27
- Avg merge
- 12h 34m
- Merged PRs (30d)
- 4
Description
The tests have the ability to manipulate the HDF5 driver in many details using some special code there to convert a command line argument string to a Driver id specification. However, that should really be moved to the main library so anyone using Silo can take advantage of it.
-----------------------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: 1399
Status: New
Project: VisIt
Tracker: Feature
Priority: Normal
Subject: Move stringtodriver utility used in tests to main silo library
Assigned to: -
Category: -
Target version: -
Author: Mark Miller
Start: 03/28/2013
Due date:
% Done: 0%
Estimated time:
Created: 03/28/2013 01:06 pm
Updated:
Likelihood:
Severity:
Found in version:
Impact: 3 - Medium
Expected Use: 3 - Occasional
OS: All
Support Group: Any
Description:
The tests have the ability to manipulate the HDF5 driver in many details using some special code there to convert a command line argument string to a Driver id specification. However, that should really be moved to the main library so anyone using Silo can take advantage of it.
Comments:
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the test code that converts command-line strings to HDF5 driver ID specifications, then trace how the main Silo library exposes driver functionality. Move that utility into the public library area so Silo users can access it, and verify that the existing tests still manipulate drivers successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100