Commit 4d3e3d6b authored by hrchilds's avatar hrchilds
Browse files

Update from April 18, 2004

git-svn-id: 18c085ea-50e0-402c-830e-de6fd14e8384
parent 536414b8
......@@ -67,6 +67,7 @@ the locked windows.
<li>VisIt now recognizes the ".mkf" extension for Master Kull Files.</li>
<li>The SAMRAI database reader plugin is now built on gps and mcr.</li>
<li>The Exodus database reader plugin is now build on white and S.</li>
<li>The Exodus reader can now correctly report simulation time.</li>
<li>Parallel compute engine arguments supplied on the command line are now applied to all compute engine launches when the viewer is run in -nowin mode.</li>
<li>The "Surface area" query has now been renamed to: "3D Surface area" and "2D area".</li>
<li>All host profiles now set a batch timeout if they use the psub parallel launcher.</li>
......@@ -83,7 +84,7 @@ the locked windows.
<li>Slicing point meshes does not work.</li>
<li>MPEG compression is set too high and causes movies generated using VisIt to have excessive compression artifacts.</li>
<li>VisIt relaunches the compute engine if you want to delete a plot.</li>
<li>Large datasets are sometimes returned to the viewer from the engine during scalable rendering.</li>
<li>Some cases for scalable rendering mode had a very high overhead, which has now been reduced.</li>
<li>The "Area between 2 curves" query crashes the viewer when the curves involved in the query are not from the same database.</li>
<li>Having an empty species list for a material variable can cause the compute engine to crash suring some queries.</li>
<li>The "Zone pick" query sometimes causes VisIt's viewer to crash.</li>
......@@ -91,41 +92,27 @@ the locked windows.
<li>Scalable rendering mode can cause multiple simultaneous compute engine launches.</li>
<li>VisIt tries to launch compute engines even after you tell it to stop trying.</li>
<li>Reopening a database can crash the compute engine in rare cases.</li>
<li>Saving an offscreen image can sometimes cause the compute engine to crash.</li>
<li>VisIt's viewer crashes when saving an offscreen image that does not contain any plots.</li>
<li>VisIt's Boxlib reader plugin has problems with vectors followed by scalar components because the Boxlib library has memory errors.</li>
<li>VisIt can't make a plot of Boxlib data on the gps machines.</li>
<li>The Verdict library, which is used for various mesh quality metrics, causes VisIt to abort in certain cases where there are ghost zones.</li>
<li>VisIt's viewer has some problems reading session files that create multiple vis windows that each have plots with different SIL restrictions.</li>
<li>The "World Pick" query crashes VisIt when it is executed over time to create a curve plot.</li>
<li>VisIt can display the wrong mesh for a plot in the Subset Window.</li>
<li>VisIt's viewer crashes when replacing databases.</li>
<li>Pick performance is very slow in some situations.</li>
<li>Pick over time crashes the compute engine when applied to a Pseudocolor plot.</li>
<li>VisIt can't create Curve plots of queries over time when vis window #2 is closed.</li>
<li>The MinMax query returns inconsistent results for some databases.</li>
<li>Material names should not be forced to have numbers.</li>
<li>VisIt is very slow to generate curves from queries over time.</li>
<li>VisIt's compactness query is not accurate.</li>
<li>Calling the "SetTimeSliderState" function in the command line interface causes it to crash in some cases.</li>
<li>VisIt's "Revolved surface area" query stopped working.</li>
<li>No curve plot is ever generated for time queries that work on FilledBoundary plots.</li>
<li>Keyframing is broken now that there are multiple time sliders in the viewer.</li>
<li>Right-clicking on the vis window's toolbar crashes the viewer on wicked.</li>
<li>The compute engine can sometimes use the wrong database reader plugin to read a database.</li>
<li>The variables menu contains the wrong variable list.</li>
<li>The LEOS database reader plugin should provide more friendly variable names.</li>
<li>The viewer kept trying to restart the compute engine even after the GUI told the viewer to quit.</li>
<li>Cancelling the launch of a compute engine can result in the launch of a serial compute engine.</li>
<li>PDB databases are opened as Silo databases if you've ever opened a Silo database.</li>
<li>Reopening a virtual database through the command line interface does not add new time states even when they are present.</li>
<li>Pick fails when using a compute engine that has been restarted.</li>
<li>The Slice operator's "Project to 2D" setting is not saved/restored correctly.</li>
<li>LD_LIBRARY_PATH should be set on the Suns.</li>
<li>VisIt did not use the correct active source when working with multiple vis windows.</li>
<li>The Vector plot displays NaNs in the legends in scalable rendering mode.</li>
<li>Reopen does not work if a database has been opened by double-clicking or if it was given on the command line.</li>
<li>Sending a ClearCache request to the compute engine does not free all of the memory that should be freed.</li>
<li>VisIt does not allow an invalid variable to be used for a plot but it does not issue a warning message either.</li>
<li>VisIt does not allow an invalid expression variable to be used for a plot but it does not issue a warning message either.</li>
<li>The error message issued when an invalid expression variable is used is not very informative.</li>
<li>The view gets messed up when scalable rendering mode kicks in after other plots have already been drawn in the vis window.</li>
<li>Plots from the curv3d database do not appear when you look at later time states from the wave database, which is a multiple time state database.</li>
......@@ -151,10 +138,7 @@ the locked windows.
<li>The viewer does not do the right thing when launching a compute engine.</li>
<li>Some bad Silo files can cause VisIt to hang when creating a Pseudocolor plot of the bad data.</li>
<li>Internal error messages are displayed for setting time sliders.</li>
<li>The "World pick" query refuses to work on the Pseudocolor plot.</li>
<li>VisIt keeps asking if you want to correlate the same files even if you say no.</li>
<li>The GetdatabaseNStates function in the CLI returns 0 for a single time state database.</li>
<li>The highlights in the selected files should not update when clicking the next frame button. There is now a check box to turn off this behavior but it is still the default.</li>
<li>Failure to launch a compute engine can result in an infinite number of attempts to restart the compute engine.</li>
<li>Some zonal expressions are identified as nodal.</li>
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment