jist:FAQ-QAO
From NITRC Wiki
FAQ-QAO for Users FAQ-QAO for Developers
Frequently Asked Questions and Questions Asked Once
| Q: | When I run jist outside mipav (either in eclipse or from command line) I get this error:
MipavViewUserInterface: Starting MIPAV with forceQuiet=true MIPAV STARTED with forceQuite set as true Error: Heap size settings in the environment startup file do not match those in the Preferences file. Memory Allocation will display so you can ensure this is correct. But it does not show me the display for changing memory settings and quit. Have you encountered this before? I even changed the preference file of both mipav and jist manually to make sure the memory settings are the same, but still get the same error. |
| A: | If you see “forceQuite” or "forceQuiet", then JIST is starting outside of MIPAV and should just exit if there are any errors what-so-ever. This ensures that JIST never hangs when MIPAV starts. If you want to allow MIPAV to ask you a question without treating every question as a critical failure, then you need to start mipav by itself and allow it to find the preferences file, THEN you can run JIST. In eclipse, you can run MipavMain. From the command line, see the post on how to run MipavMain with the mipavjava alias. jist:CommandLineInterface
|
| Q: | If I use unzip to extract the contents of the JIST jar file, the permissions appear corrupt (some directories are not readable). What's up? |
| A: | It looks like there is a "bug/feature" in jar and/or unzip on linux systems. If I use "jar -xvf" to unzip the JIST jar file, then all permission are set correctly. However, if I use the "unzip" command, then the permissions on some directories are corrupted (000). I suspect that this is due to differing implementations of the INFO-ZIP for unix permissions in zip files. We must maintain compatibility with "jar -xvf" since these are jar files, so I strongly suggest using "jar -xvf" instead of unzip to decompress the jar files. |
| Q: | I followed the instructions, but when I run the process manager, all modules are "NOT READY" |
| A: | The term NOT READY can be caused by a variety of settings. The most common is that the inputs for a module are not yet available. If this module depends on other modules, then its prerequisites have not finished. If this is a top-level module, then the source files may not be able to be found. Alternatively, one or more inputs to a module could have been omitted in the layout manager. |
| Q: | How should I report a problem? |
| A: | Please post a question on the forum with a description of the problem, a copy of your layout file, and the debug.err&debug.out from the module directories which are having problems. |
| Q: | Question |
| A: | Answer |
