SpectraPLOT: if results were run on a different computer than the one running SpectraPLOT, drill-down and ionization plots may not work. This is because it accesses the hydro file and atomic data. While it will prompt you to search for the hydro file, unless the atomic data paths are the same as on the other computer, it will fail to find the atomic data.
Visualizer: drill-down in version 20.0.0 and beyond may produce inconsistent results when done on calculations that include new line width models. This is not an issue for SpectraPLOT.
SpectraPLOT: drill-down and ionization plots in version 20.0.0 may produce inconsistent results if SpectraPLOT workspace includes more than one hydro run. This limitation will be addressed in the future releases .
When SpectraPLOT is opened the runs window and drilldown window will not initial raise above plot windows. This can be resolved by selecting the runs or drilldown windows from the windows list. This only need be done once and then the window ordering issue will resolve.
When changing plot units in SpectraPLOT, plot ranges may get corrupted. Users may need to click "rescale" button to produce plots in default ranges or manually adjust plot ranges for each axis.
On some machines, when entering values in the table cells, the values are
not saved.
Workaround: After entering a number, click on some other cell in the
table.
While a simulation is running, the current workspace can be edited and saved,
but no other file can be opened and the hydrocode data cannot be viewed.
Workaround: Start another SPECT3D application
On some laptop computers running Windows, the abort button may fail to work.
Workaround: Bring up the Task Manager (Ctl + Alt + Delete) and end the
process.
For a batch run, all file paths must be absolute.
For versions greater than 6.0.0: If a workspace created with a previous version
includes an isotope and is run in batch, it will fail as the isotope numbers
are checked for consistency. Please open the workspace in the GUI application
and save it.
GridConvert: when re-mapping a grid from a single exodus file with multiple time steps, de-selecting and then re-selecting time steps, and then beginning the conversion process, can cause a crash.
GridConvert: when re-mapping a grid with AMR (i.e., Max. # AMR subdivisions > 0), and with the "Specify range" option selected, if the input range values go beyond the original hydro file's spatial ranges, bad values (-1) will be written for connectivity, which may cause SPECT3D to crash when using the output exodus file. Care should be taken to keep new range values within the original range.
GridConvert: when using the "Use evenly-spaced grid" option for re-mapping a grid, the "Fit to input grid" option may not always work. Rather, it may get the grid boundary values (e.g., "X min" and "X max") from the input fields below, even though they are grayed out for this option.
Workaround: Determine the grid boundary values of your original grid and use those with the "Specify range" option.
GridConvert: specifying Grid Type (static vs. moving) in the mapping variables interface may not affect the type of grid data
written (whether it is static (variable named "coord") or dynamic (variable named "vals_nod_var" which is per time step)).
Workaround: When running SPECT3D on GridConvert's output, if it complains about "coord" or "vals_nod_var" not being written, you can swap the Grid Type (from Static to Non-static, or vice-versa) in the Plasma page.
