Scripting:Requirements

Requirement: Ability to apply a script to multiple different input files and save an image/movie of the visualization from each input file

Requirement: Scripting language is backwards compatible. Scripts written in a previous version of ParaQ must work in newer versions.

Requirement: Script files saved from ParaQ must work in the batch/command line program

Requirement: Script files must be understandable by humans without needing 2 Tylenol.

Requirement: Either the scripting language or the pvCommandLine application must provide looping and flow-of-control.

Optional?: When a user determines that they like a set of scripted operations, they can attach the script to a button in ParaQ.

Use Case: A user makes a visualization in ParaQ and saves out a script file. The user then open the script file in pvCommandLine, twiddles some values and saves the image/movie of the visualization. Some values include filenames, variable names, values of variables.

Use Case: A user opens a toy dataset that models an extremely large dataset. The user creates a visualization and saves a script. The user then opens pvCommandLine and applies the script to the extremely large dataset

Use Case: (Optional) A user opens a saved script file with ParaQ and steps through, visualizing what each command actually does to their data.

Use Case: An expert user can copy and paste from their scripts to new scripts to add steps.