Menu
▾
▴
Known_Issues
There is a newer version of this page. You can find it here.
This page contains lists all of the issues that we know about in NiCE and are currently investigating.
These issues are not necessarily bugs. They may represent missing capabilities altogether. Normally, though, they are bugs that we know about and are actively trying to fix. If you see an issue on this page that is affecting you, please do not file a bug report. Instead, send an email to billingsjj <at> ornl <dot> gov and let us know that the issue matters to you.
Persistence
ReactorAnalyzers are not persisted in NiCE 2.1.1. We're hoping to re-deploy this capability in an upcoming release. All of your reactor data is still fine in the HDF5 files.
Job Launchers
Only some of our JobLaunchers allow users to tailor the number of MPI processes and OpenMP threads, even though jobs created with the editor allow default values for these to be specified. Jobs created by the Job Profile Editor should still work, but the choice of whether or not parallel launch is enabled for other apps is fixed.
MultiLauncher
Most of the issues in our MultiLauncher come from the fact that it is heavily threaded. We are currently working the following issues:
- The multilauncher sometimes fails on jobs where multiple remote jobs are executed.
Geometry Editor
Our geometry editor is a can of worms. Eclipse and JME3 don't play so well together, but we have been very successful so far. We are currently aware of the following issues for this piece of code:
- The geometry editor doesn't always load on Windows and Mac.
- The geometry editor throws an exception when re-opening a previously created Geometry with the ItemViewer.
Reactor Analyzer
Reactor Analyzers are not currently persisted because writing an LWR to a database or XML file would be a huge amount of duplicated work since it is already stored in an HDF5 file.
The ReactorAnalyzer may take some time to load large NiCE-IO .h5 files, particularly when there are multiple assemblies. On this desktop (Intel Xeon 3 GHz, 6 GB RAM), it takes approximately 12 seconds to read in each assembly for CASL problem 5 (quarter-core symmetry with 56 assemblies, each 17x17, with 6 data features, 1 axial level). We are looking into optimizing our file structure and access methods to reduce the loading time for such files.
