ParaView 3 Telecon 08-13-2009: Difference between revisions
No edit summary |
No edit summary |
||
| Line 26: | Line 26: | ||
As an action, someone at Sandia needs to work with someone in 1500 to get some reasonable scaling numbers. | As an action, someone at Sandia needs to work with someone in 1500 to get some reasonable scaling numbers. | ||
''This Week:'' | |||
Nathan has some new inputs that need at least 200 processors and should scale better. | |||
== Stronger Dashboard == | == Stronger Dashboard == | ||
| Line 34: | Line 38: | ||
Utkarsh is still going to think about how to run more tests faster. | Utkarsh is still going to think about how to run more tests faster. | ||
''This Week:'' | |||
In Utkarsh's branding branch, allows you to run multiple tests in one invocation and have each have their own result images. Between tests, the GUI resets but the connection remains. You can also isolate tests that could effect others (like the color palette tests). | |||
Latest revision as of 13:12, 13 August 2009
| Item | People | Description |
|---|---|---|
| 1 | Ice | MARS/V&V Milestone issues |
| 2 | Loring | Remote interactivity coordination (bugs 9408 & 9409) |
| 3 | Moreland | Stronger Dashboard
|
| 4 | Thompson | Statistics Update |
| 5 | Bauer | In-situ paper |
| 6 | Moreland | Plugin interface discussion |
MARS Milestone
Last Week:
The scaling studies have stalled. Kitware does not have any CTH simulation that makes sense to scale past about 500 processors. Thus, the fraction of time spent in fragment analysis is not representative (the entire dataset is replicated in ghost cells.
As an action, someone at Sandia needs to work with someone in 1500 to get some reasonable scaling numbers.
This Week:
Nathan has some new inputs that need at least 200 processors and should scale better.
Stronger Dashboard
Last Week:
Dave P. is now monitoring the dashboard.
Utkarsh is still going to think about how to run more tests faster.
This Week:
In Utkarsh's branding branch, allows you to run multiple tests in one invocation and have each have their own result images. Between tests, the GUI resets but the connection remains. You can also isolate tests that could effect others (like the color palette tests).
