STATEMENT OF WORK
Brian Zachary Abel
ICERT REU
Objective
Why are you performing the work?
I am writing support scripts to enable scientific visualizations of large data sets. These are tools that enable researchers to analyze data to detect potential problems and produce insight, as well as communicate their results.
Scope
What is being done?
The script I am currently working on, following settings that the user specifies in a number of well documented global variables at the top of the script:
- loads data from input files, turns on and off a bunch of paraview settings/widgets
- rotates the model/sets the viewpoint
- makes “clips” at a user defined location to show what’s going on inside
- sets and scales a color bar to the specified cell data scalar values
- and writes output files to the local directory,
My mentor can then stitch together into an animation. These animations can be used for analysis of the data set and presenting research results at conferences and in papers. After that I’ll be working on trying to smooth the input data to improve the accuracy of results associated with the model utilizing Amira on the Maverick visualization cluster
How will it be done (A list of the tasks describing the process for completing the work )?
1. Collect project requirements, figure out use cases, that type of stuff (finished, more or less, for the first script)
2. Read Documentation
3. Write script
4. Encounter problem/challenge/bug, go back to step 2
5. Give to user
6. Listen to user complaint/feedback and go back to step 1
Assumptions associated with each task.
1. Project requirements are well defined and won’t change, addressed by step 6
2. There is documentation and the documentation makes sense and is comprehensive. If not experimentation/source code analysis are alternative options.
3. The development environment is properly set up. I can handle this.
4. There will be a problem. No need to worry about that.
5. The user receives the task, we work in close geographic proximity so it shouldn’t be a problem
Deliverables that will be handed off to the client for review and approval
Scripts/subroutines that will run in the TACC supercomputers.
Schedule
Timeline to complete the project.
Expected ~2 weeks for the first script, ~June 23
with the rest of the time until August 1st or 2nd spent on input data smoothing
or similar tasks.
Additional or Key Assumptions
Assumptions NOT associated with the tasks.
An example of an assumption directly related to the project that isn’t directly task related might be:
-Will the example datasets I use to write my scripts still be relevant when I’m done? I’ll try/need to incorporate a degree of generalization into my scripts.
Brian Zachary Abel
ICERT REU
Objective
Why are you performing the work?
I am writing support scripts to enable scientific visualizations of large data sets. These are tools that enable researchers to analyze data to detect potential problems and produce insight, as well as communicate their results.
Scope
What is being done?
The script I am currently working on, following settings that the user specifies in a number of well documented global variables at the top of the script:
- loads data from input files, turns on and off a bunch of paraview settings/widgets
- rotates the model/sets the viewpoint
- makes “clips” at a user defined location to show what’s going on inside
- sets and scales a color bar to the specified cell data scalar values
- and writes output files to the local directory,
My mentor can then stitch together into an animation. These animations can be used for analysis of the data set and presenting research results at conferences and in papers. After that I’ll be working on trying to smooth the input data to improve the accuracy of results associated with the model utilizing Amira on the Maverick visualization cluster
How will it be done (A list of the tasks describing the process for completing the work )?
1. Collect project requirements, figure out use cases, that type of stuff (finished, more or less, for the first script)
2. Read Documentation
3. Write script
4. Encounter problem/challenge/bug, go back to step 2
5. Give to user
6. Listen to user complaint/feedback and go back to step 1
Assumptions associated with each task.
1. Project requirements are well defined and won’t change, addressed by step 6
2. There is documentation and the documentation makes sense and is comprehensive. If not experimentation/source code analysis are alternative options.
3. The development environment is properly set up. I can handle this.
4. There will be a problem. No need to worry about that.
5. The user receives the task, we work in close geographic proximity so it shouldn’t be a problem
Deliverables that will be handed off to the client for review and approval
Scripts/subroutines that will run in the TACC supercomputers.
Schedule
Timeline to complete the project.
Expected ~2 weeks for the first script, ~June 23
with the rest of the time until August 1st or 2nd spent on input data smoothing
or similar tasks.
Additional or Key Assumptions
Assumptions NOT associated with the tasks.
An example of an assumption directly related to the project that isn’t directly task related might be:
-Will the example datasets I use to write my scripts still be relevant when I’m done? I’ll try/need to incorporate a degree of generalization into my scripts.