Develope an extracttimeseries function for silo

Nobody has claimed this yet.

This is urgent for LLNL Engineering customers. The idea is a parallel tool that opens a slew of silo files teasing info for a handful of mesh nodes and/or zones out of the files and producing either csv text files or maybe Silo files with DBcurve objects indicating the mesh entities variation over the whole time history. Needed controls are open first timestep and search global ids for the specified entities specify which mesh variables to capture (or all) taking every nth point dealing with time series where mesh entities specified by a global id come and go must run in parallel, so it can divide the work among many processors make it a function in the Silo library (take care regarding parallel interface) output format (csv or silo curves) Note that doing similar for a specific geometric location probably requires interpolation of mesh variables to that specific location. It is not clear such is needed in the initial implementation here. Finally, what about doing same for an entire lineout (which again would require interpolation) and/or do we need to interpolate through time as well?

-----------------------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: 2603
Status: Pending
Project: VisIt
Tracker: Feature
Priority: High
Subject: Develope an extracttimeseries function for silo
Assigned to: Mark Miller
Category: -
Target version: 4.11.0
Author: Mark Miller
Start: 04/14/2016
Due date:
% Done: 0%
Estimated time:
Created: 04/14/2016 06:18 pm
Updated: 12/10/2016 12:18 am
Likelihood:
Severity:
Found in version:
Impact: 4 - High
Expected Use: 4 - Common
OS: All
Support Group: Any
Description:
This is urgent for LLNL Engineering customers. The idea is a parallel tool that opens a slew of silo files teasing info for a handful of mesh nodes and/or zones out of the files and producing either csv text files or maybe Silo files with DBcurve objects indicating the mesh entities variation over the whole time history. Needed controls are open first timestep and search global ids for the specified entities specify which mesh variables to capture (or all) taking every nth point dealing with time series where mesh entities specified by a global id come and go must run in parallel, so it can divide the work among many processors make it a function in the Silo library (take care regarding parallel interface) output format (csv or silo curves) Note that doing similar for a specific geometric location probably requires interpolation of mesh variables to that specific location. It is not clear such is needed in the initial implementation here. Finally, what about doing same for an entire lineout (which again would require interpolation) and/or do we need to interpolate through time as well?

Comments:

The issue names no source file, test, or entry point. Start by locating the Silo library's parallel interface and existing mesh, global-ID, and DBcurve APIs; first clarify whether the initial scope is entity IDs with CSV or DBcurve output, excluding interpolation. Done criteria should cover parallel behavior and entities that appear or disappear across time.

Written by the indexing model from the issue text.